Confluence Outage History

The Confluence Cloud Search component experienced intermittent errors affecting Atlassian Intelligence customers, notably impacting Smart Answers in Search and AI Definitions. The incident began around 1:15 AM UTC as users reported search-related problems. By 1:11 AM UTC Atlassian had identified the root cause and was preparing a hotfix.

Confluence Automations experienced delayed automation rule execution, causing automation workflows to run slowly or not trigger as expected. The issue affected Confluence Automations and related Jira Cloud services, including Jira Work Management, Jira Service Management, Jira, and Jira Product Discovery Cloud customers needing automated actions to fire.

An outage impacted the Administration page, causing blank screens when loading administration across Atlassian products. The issue began at Apr 14, 2025 12:40 AM UTC and lasted about one hour, with the Administration component returning to service by Apr 14, 2025 1:40 AM UTC. Atlassian's status page indicated an investigation at the start and later confirmed the admin interface was restored.

Confluence experienced a brief regional impact beginning at Apr 4, 2025 5:55 AM UTC, with some users unable to access Jira and Confluence sites. Affected components included View Content, Create and Edit, Comments, Administration, Notifications, Marketplace Apps, Purchasing & Licensing, Confluence Automations, Cloud to Cloud Migrations - Copy Product Data, Server to Cloud Migrations - Copy Product Data, Authentication and User Management, Signup, and Search. The incident lasted roughly 45 minutes and the service was restored by Apr 4, 2025 6:40 AM UTC. The issue was reported in several regions, indicating a partial regional outage rather than a global disruption.

Confluence experienced a partial outage affecting the Marketplace Apps component, with the Find new apps menu missing from the user interface. This prevented users from opening or browsing the Atlassian Marketplace within Confluence, impacting app discovery and installation workflows for affected users.

The incident began on 5:10 AM UTC and was resolved by 7:45 AM UTC, lasting about 2 hours and 35 minutes. Atlassian posted two status updates during the outage as engineers investigated and restored the Marketplace access. The issue was limited to the Marketplace Apps component for the duration of the incident.

Confluence, along with Jira Cloud services, experienced degraded performance beginning at 3:11 PM UTC. The issue appeared to affect the View Content component, leading to slower page loads and content rendering for some users. Atlassian stated they were investigating and noted that Confluence, Jira Work Management, Jira Service Management, and Jira Cloud customers were impacted. The incident lasted until 7:15 PM UTC, during which two status updates were posted as the team worked to diagnose and restore normal service.

Confluence in the APAC region experienced a partial access issue where some users were shown a site maintenance banner instead of their Confluence site. The disruption affected a wide range of Confluence components, including Comments, View Content, Create and Edit, Authentication and User Management, Search, Notifications, and mobile apps, resulting in degraded access for users across APAC.

An incident began at 8:45 AM UTC when Forge app installations started failing at an increased rate, affecting Confluence and related Atlassian Cloud services. The Marketplace Apps component was listed as degraded as users encountered intermittent errors installing Forge apps.

Later, at 3:05 PM UTC, Atlassian flagged degraded performance for automation, reporting delayed automation rule execution across Confluence Automations and related products including Jira Service Management and Jira Cloud. The incident was resolved by 5:30 PM UTC, with Marketplace Apps and Confluence Automations returning to normal. In total, 3 official status updates were published, and the outage lasted approximately 8 hours and 45 minutes.

Confluence Automations experienced service slowness, causing delays in automation processing across Jira, Jira Service Management, and Confluence. Although automation rules fired, their execution was slowed and queued events could take longer to process. The incident began at Mar 17, 2025 12:50 PM UTC when Confluence Automations moved to a degraded state, and it was resolved by Mar 17, 2025 4:40 PM UTC when status returned to normal. Atlassian noted that rules triggered in the last 2.5 hours would be processed, and adjustments were made at Mar 17, 2025 12:13 PM UTC to prioritize new events. The provider issued 2 status updates during the incident.

Some users experienced errors while creating new Jira and Confluence sites, disrupting the signup flow. The incident began at 6:55 PM UTC and Atlassian issued updates as the signup component showed degraded behavior. The problem was resolved by 8:50 PM UTC, with the signup component returning to normal and status restored to up. Atlassian issued 2 status updates during the incident. The impact was limited to site-creation workflows, with no broader service outages reported.