Confluence Outage History

On Nov 18, 2025 1:35 PM UTC, Confluence began experiencing a broad outage with elevated server errors affecting Whiteboards and Databases. An initial status update cited a partial reduction in service from a third-party provider and widespread issues across many components, including Notifications, Purchasing & Licensing, Mobile Apps, Authentication and User Management, Create and Edit, Search, View Content, and Comments. The incident persisted for several hours with continued updates as teams worked to restore service and affected users experienced outages across Confluence features. At 2:40 PM UTC Confluence posted an update attributing the errors to a global Cloudflare outage, with Cloudflare actively working to restore services. The outage prompted three status updates during the incident.

Confluence experienced a brief issue affecting content editing, with users seeing lost connection messages while attempting to save changes (for example, "We've lost our connection to you. Your changes will be saved when we reconnect. Trying to reconnect..."). The problem impacted the Create and Edit component. The outage began on 2:55 AM UTC and was resolved by 3:20 AM UTC, lasting about 25 minutes. The Confluence status page listed the Create and Edit component as degraded (warn) at 2:55 AM UTC and returned to normal with the final update at 3:20 AM UTC, with two status updates issued during the incident.

The Confluence Automations component experienced degraded performance and intermittent errors affecting some Confluence Automations users, with reports affecting some Confluence, Jira Service Management, and Jira Cloud customers. The incident began at Nov 3, 2025 4:15 PM UTC when Confluence Automations transitioned to a degraded state, and the status page noted an investigation into the root cause. Users observed slower performance and intermittent failures during the event.

The provider issued 2 status updates as the issue unfolded and resolved the incident at Nov 3, 2025 6:10 PM UTC. The outage lasted approximately 1 hour and 55 minutes. No user reports were observed, and there was no clear regional pattern; the impact appeared limited to the affected Confluence Automations component. Affected users experienced degraded functionality and intermittent errors while attempting to use the feature during the window.

The Atlassian Cloud experienced degraded performance for some users in Australia from 6:50 AM UTC to 2:10 AM UTC. This impacted Confluence and a broad set of Atlassian Cloud services, with users reporting slower page loads, intermittent errors, and difficulties with editing, searching, and receiving notifications. Fifteen components were affected, including Authentication and User Management, Search, and Notifications.

Confluence experienced a regional outage in the APSE region, causing access issues for the Confluence application and content. The disruption affected two components, View Content and Create and Edit, leading to pages not loading and edits being unavailable for users in that region. The outage began around 6:31 AM UTC.

Confluence Automations experienced delays in executing automation rules, affecting users relying on automated workflows. Atlassian attributed the issue to a follow-on effect from a recent AWS outage and initiated an investigation with regular updates. The outage began on Oct 22, 2025 6:25 AM UTC and was resolved by Oct 22, 2025 11:40 AM UTC, lasting approximately 5 hours and 15 minutes. Two official status updates were published during the incident, indicating an initial delay and later restoration of automation rule execution.

The outage began at Oct 20, 2025 8:00 AM UTC and was resolved by Oct 21, 2025 5:25 AM UTC, lasting about 21 hours and 25 minutes. Atlassian reported impact across 14 components including Authentication and User Management, View Content, Purchasing & Licensing, Confluence Automations, Cloud to Cloud Migrations - Copy Product Data, Server to Cloud Migrations - Copy Product Data, Mobile / Android App, Create and Edit, Comments, Search, Administration, Notifications, Marketplace Apps, Signup, and Mobile / iOS App. Users experienced login and access issues, difficulties viewing or editing content, and errors such as Something went wrong, with mobile apps and notifications affected. The issues appeared global in scope based on reports from multiple regions.

Confluence experienced degraded UI operations, with UI-based customer interactions not working as expected. The outage began at Oct 15, 2025 1:45 PM UTC and lasted approximately 2 hours and 35 minutes, with restoration confirmed by Oct 15, 2025 4:20 PM UTC. The incident specifically involved the Confluence Automations component, and status updates noted that UI issues were under investigation.

During the event, Atlassian issued 2 status updates describing the investigation and remediation efforts, and users likely encountered slow or unresponsive UI elements and automation tasks within Confluence.

Access to Jira and Confluence cloud products was degraded from 4:39 AM UTC to 4:52 AM UTC due to an erroneous certificate. The certificate was corrected and functionality was restored, with full restoration by Sep 22, 2025 7:00 AM UTC.

The incident prompted two official status updates during the event. The impact was broad, affecting 15 Confluence components including Search, View Content, and Authentication and User Management, across the suite. Users worldwide experienced issues during the outage. The degradation lasted about 13 minutes, followed by full recovery.

Confluence experienced a brief outage in which users could not access the service due to SSL or security errors. Reports from around the world—Australia, the United States, Singapore, the Philippines, Thailand, and New Zealand—described 403 errors and SSL connection failures. The incident began at 4:44 AM UTC and lasted about 20 minutes, with access restored by 5:04 AM UTC. The outage affected multiple regions and appeared to be a global disruption for a short window.