Confluence Outage History

Confluence Cloud users experienced errors when attempting to view Calendars between 00:50 UTC and 07:30 UTC on May 27, 2026, affecting the View Content functionality. The engineering team identified the root cause and deployed a fix, fully resolving the incident after 1.8 hours.

Some users experienced issues loading and editing certain macros in the Confluence Cloud page editor for 3.3 hours on May 26, 2026, with affected users seeing "Error loading the extension!" messages or finding macros missing from the editor's selection menu. The incident affected marketplace apps and the create/edit functionality, while viewing published pages remained unaffected. The engineering team identified and resolved the underlying issue, fully restoring macro functionality.

A major incident affected multiple Atlassian products including Confluence and Jira Cloud for 1.9 hours, impacting core functionality such as authentication, content access, editing, search, and mobile apps for a large number of customers. The team identified the root cause and implemented a mitigation, with all services fully recovering and the incident resolved.

Multiple Atlassian services, including Confluence, experienced an 18.3-hour outage affecting core functionality such as content viewing and editing, authentication, search, notifications, mobile apps, and various administrative features. The incident was caused by an infrastructure outage from Atlassian's public cloud provider that disrupted asynchronous event processing. Services were restored after the underlying infrastructure issue was mitigated, with additional time required to clear the backlog of queued events and replay missed notifications and automation triggers.

Confluence experienced a service disruption affecting Rovo agents used in automation rules, causing these automations to fail to complete as expected. The incident impacted multiple Confluence components including automations, content management, search, and mobile apps. The issue was identified and resolved after 3.8 hours, with services returning to normal operation.

Some users were unable to log in to Atlassian products with their Atlassian accounts on April 13, 2026, between 05:49 a.m. and 06:25 a.m. UTC. The authentication and user management systems, along with signup functionality, were affected during this 2.8-hour incident. The underlying issue was addressed and authentication services returned to stable operation with no further impact observed.

Search functionality failed across Confluence and Jira for 6.1 hours, with cascading impacts to Customer Service Management, Asset Reports, Jira Service Management dashboards, Rovo Chat, User Management, Administration, and Guard services. The team identified the root cause and restored core search functionality, though some customers experienced delays searching recently changed data while reindexing completed. The incident was fully resolved with all services returning to normal operation.

Confluence Cloud users experienced errors when accessing certain Marketplace macros, receiving "Error rendering macro 'static-macro': Page loading failed" messages. The issue affected Marketplace Apps functionality and prevented users from properly viewing content with these macros. The problem was identified and resolved after 12.8 hours with a deployed fix, restoring normal service operations.

Automation events experienced significant delays for APAC region customers across Jira, Jira Service Management, Jira Work Management, Jira Product Discovery, and Confluence for 47 minutes on March 9th UTC. The engineering team identified the root cause and deployed a hotfix to restore automation performance and process the backlog of delayed events. All services returned to normal operation with continued monitoring to ensure stability.