Confluence outage history

An outage affected job processing and scheduling across Atlassian products, with users experiencing delays in scheduled tasks and asynchronous work. In Confluence, Jira, and Bitbucket Cloud, scheduled jobs and email-to-ticket processing did not run as expected, and SLA visibility in Jira Service Management was affected by a missing SLA component. The incident began at 3:00 AM UTC and persisted through the afternoon, during which Confluence Automations showed degraded status (warn).

Status updates from Atlassian indicated that teams identified the root cause and began mitigation, with improvements observed as recovery progressed. The service moved toward full restoration by 7:55 AM UTC, and ongoing monitoring was used to ensure full recovery. The impact was felt across multiple products, driven by the central job processing and scheduling issue, with delays affecting users relying on automated workflows and scheduled tasks.

An Atlassian Cloud outage affected Confluence, Jira Cloud, and Jira Service Management in multiple regions, making sites inaccessible and hindering core collaboration and content workflows. Users reported pages failing to load, redirects to outage notices, and authentication issues, with impacts observed across regions including Australia, New Zealand, India, and parts of Europe. The disruption touched a broad set of components, including Confluence Automations, Authentication and User Management, Search, View Content, Create and Edit, Comments, and related data migrations and mobile apps, signaling a wide-reaching outage across the Atlassian Cloud suite.

Confluence experienced a notification delivery issue beginning at 8:45 AM UTC, with the Notifications component showing degraded performance and increased latency for email, mobile, and Slack alerts for Jira, Jira Service Management (JSM), and Confluence. This impacted how users received notifications, potentially delaying important updates. The engineering team identified the impacted regions and began mitigation, with further updates promised as work progressed. The incident persisted through the afternoon as regional mitigations were implemented.

Confluence users relying on notifications experienced degraded delivery due to increased latency across email, mobile, and Slack channels for JIRA, JSM, and Confluence. Impact began at 7:25 PM UTC and three regions were identified as affected as teams continued investigating. By 9:35 PM UTC, the team had a likely cause and was working on mitigation, with updates continuing as more information became available. The issue was resolved by 11:15 PM UTC, at which point the Notifications component returned to normal.

Users on Confluence experienced rendering failures for Marketplace App macros, with macros not rendering or displaying errors on pages that rely on these extensions. The issue surfaced at 7:20 AM UTC as Confluence flagged a degraded experience affecting Marketplace Apps and the View Content components, impacting pages that rely on these macros.

A fix was identified and deployment began at 8:20 AM UTC, and by 10:15 AM UTC the affected components were restored to normal operation. The degraded experience persisted for nearly three hours before full recovery.

Confluence Cloud experienced intermittent errors affecting anonymous access to public links, with some related areas showing a Something went wrong page. The issue began at 8:15 PM UTC and the team identified a problematic recent change, preparing a revert to restore the affected experience while verifying normal service. The View Content component was among the areas impacted. By 10:15 PM UTC the service had returned to normal as the revert path was used to restore access to public links.

An EU-region outage briefly disrupted Confluence, with user-search, user-picker, and assets impacted. The incident began at 11:50 AM UTC and was resolved by 12:30 PM UTC, lasting around 40 minutes for affected users. Atlassian’s status updates indicated reliability issues across Jira and Confluence and that the team was actively investigating, with additional updates promised within the hour.

A brief disruption affected Confluence Automations amid broader reliability issues reported for Jira and Confluence. The outage began for Confluence Automations at 9:26 AM UTC as Atlassian indicated they were investigating the cause and would share updates within an hour. The component recovered at 10:05 AM UTC, roughly 39 minutes after the outage started, with services returning to normal. The service page messages reflect a focused impact on the Confluence Automations component within the wider Jira/Confluence reliability incident and indicate active investigation and resolution efforts.

Confluence and related Atlassian Cloud products experienced degraded performance when selecting users or teams in certain system and custom fields, affecting workflows that rely on user assignments and collaboration. The issue impacted two components, View Content and Create and Edit, across Jira, Jira Service Management, and Confluence. The outage began at 4:15 AM UTC and caused delays during user and team selection until it was resolved. Atlassian published two status updates during the incident to communicate progress, and the service was restored by 12:30 PM UTC, for a total outage duration of about 8 hours and 15 minutes.

Confluence Cloud experienced a partial outage beginning at 3:45 PM UTC, impacting availability for some customers in AP South, APSE, APSE2, East, and Central. Access to Confluence content and collaboration features was affected for those regions, while other regions remained online. By 5:50 PM UTC, the service was restored and Confluence Cloud returned to normal operation. The Atlassian status page logged the incident as a partial disruption and published two updates during the event, documenting the affected regions and restoration timeline. The outage lasted approximately 2 hours and 5 minutes, and user reports during the incident were limited.