Confluence Outage History

Confluence search, including Compass search, experienced errors that prevented search results from being returned. The issue began around 2:18 AM UTC and a degraded search state persisted until 2:50 AM UTC, lasting about 30 minutes and affecting the Search component. The problem was limited to search functionality and did not impact other Confluence features. Two status updates were posted during the incident, with the first noting investigation and degraded search and the second confirming restoration.

Confluence experienced a prolonged delay affecting single-user page edits. Users could see saved changes not appearing promptly or updates taking longer than usual. The issue affected the Create and Edit component, with Atlassian noting a Page Update delay while investigators worked to resolve it. The outage began on 7:45 PM UTC and was resolved by 11:41 AM UTC.

Atlassian's status page posted two updates during the incident, indicating ongoing investigation and degraded performance before the resolution. While user reports came from multiple locations, there was no indication of a global outage; service returned to normal after the final update. Users who attempted edits during the window may have experienced longer save times or missing updates.

Confluence Cloud users experienced intermittent search issues, with the search function failing to return results for some customers. This degraded the ability to locate pages and content via the search bar, impacting teams that rely on quick content discovery. The Confluence status page acknowledged the problem and indicated ongoing investigations into intermittent errors affecting the Search component.

The incident began at 5:55 PM UTC and was resolved by 8:40 PM UTC, lasting about 2 hours and 45 minutes. The Confluence status page issued two updates during the incident, describing the ongoing investigation and eventual restoration of the Search service. The issue was isolated to the Search component; no other Confluence services were noted as affected.

Confluence Cloud began experiencing iOS-specific access issues on 5:05 AM UTC when IP Allowlist and App Trust Mobile Bypass were enabled, causing pages to return 403 errors for iOS users. An Android workaround was recommended while a fix was prepared for the App Store.

A separate issue with Advanced Search intermittently returning results was reported around Feb 27, 2025 8:04 PM UTC and investigated in subsequent updates. The status page documented ongoing investigation and intermittent symptoms in the Search component, with later updates noting continued 403 errors under a Mobile App policy that allowed access from any IP address.

By 1:50 AM UTC the Mobile / iOS App had moved from warn to up, indicating that the iOS access issues were resolved. The impact was limited to iOS users and affected search functionality for some customers, rather than a global outage. The incident lasted from 5:05 AM UTC to 1:50 AM UTC and involved multiple official updates across at least two components.

Confluence Cloud experienced intermittent errors in the search function affecting anonymous access users. Some customers reported that search results were unavailable or queries timed out during the incident.

The outage began at 8:15 PM UTC and was resolved by 10:20 PM UTC, lasting roughly 2 hours and 5 minutes. The issue affected the Search component and was listed as degraded on the Confluence status page. The provider issued 2 status updates during the incident before restoring normal operation.

Confluence and Jira services experienced degraded performance starting around 6:07 PM UTC for Jira Work Management, Jira Service Management, Jira Cloud and Confluence, affecting multiple features including content creation and editing, search, authentication, and notifications. Users likely encountered slower responses and intermittent errors across Jira and Confluence, with 15 components across the suite affected (including Mobile apps, Comments, Notifications, Administration, Create and Edit, View Content, and Authentication and User Management). The outage lasted about 1 hour and 23 minutes. The Atlassian status page acknowledged the degradation at 6:10 PM UTC, with two updates issued during the incident at 6:10 PM UTC and 7:30 PM UTC. Services were restored by 7:30 PM UTC.

Confluence experienced a page load outage affecting Confluence and Knowledge Base in the Customer Portal, and Jira Service Management Cloud customers. The outage began at 12:45 AM UTC and was resolved by 2:20 AM UTC, lasting about 1 hour 35 minutes.

The Atlassian status page issued 2 updates during the incident, including an initial investigation and a final restoration notice confirming the View Content component was back online.

The Confluence service experienced a partial outage starting at 2:50 PM UTC, affecting about 15 components and impacting a broad set of features including content viewing, editing, search, notifications, and user management. Users reported difficulty accessing Confluence and performing common tasks, with degraded performance reported across multiple areas of the platform.

The issue was identified as caused by a third-party plugin, and Atlassian recommended upgrading the Table Filter, Charts & Spreadsheets for Confluence plugin. The outage lasted approximately 5 hours and 5 minutes and was resolved by 7:55 PM UTC. The provider issued 3 status updates during the incident to communicate the investigation, the plugin-related cause, and the final resolution.

Confluence experienced a brief degradation affecting the ability to link Confluence spaces to Jira projects, impacting some Confluence and Jira Cloud customers. Users attempting to connect spaces with Jira projects may have encountered errors or delays during the incident. The incident began at Jan 23, 2025 12:10 AM UTC and was resolved by Jan 23, 2025 1:20 AM UTC, lasting approximately 1 hour 10 minutes. The Atlassian Administration component issued an initial status update indicating an investigation and later signaled recovery as the issue was resolved. The incident involved a single component and was addressed with two status updates.

Confluence experienced a brief degradation of its Search functionality, preventing users from performing in-site searches for about 55 minutes. The Confluence status page showed an investigation into the Search issue starting at 5:45 PM UTC and noted that the Search component was affected; two status updates were posted as the incident progressed. The problem was resolved by 6:40 PM UTC when Search returned to normal and the status page reflected a return to uptime. The impact was limited to the Search component, with no indication of a broader outage across Confluence.