Confluence Outage History

Confluence and Jira Cloud experienced degraded performance for Microsoft Edge users, affecting core actions such as viewing content, creating and editing pages, and leaving comments. The issue began on Sep 9, 2025 10:30 AM UTC with investigation starting around Sep 9, 2025 10:23 AM UTC; the status page later listed three impacted components: View Content, Create and Edit, and Comments. The provider issued two status updates during the incident, and the degradation persisted until Sep 15, 2025 6:45 AM UTC when services returned to normal.

Confluence experienced an issue in the Administration component where product invitation emails were not being sent to users. Invitations within Confluence still succeeded, but email notifications for invites did not reach recipients, impacting onboarding and collaboration workflows that rely on email invites.

Confluence experienced a degraded experience when adding attachments or accessing existing media content, impacting the View Content and Create and Edit components. Users attempting to attach files or view media across pages encountered delays or failures. The issue began on Jul 30, 2025 7:10 AM UTC and was resolved by Jul 30, 2025 9:45 AM UTC, lasting about 2 hours and 35 minutes.

Confluence and several Atlassian cloud products experienced intermittent Forge app invocation failures, impacting scheduled triggers and smart links for a two-hour window. Users may have encountered errors in app functionality and interrupted automation during this period, with multiple Confluence-related components affected. The incident impacted 16 components across the Confluence suite, including mobile apps, authentication, search, content viewing, and create/edit workflows.

Confluence experienced a partial outage in Atlassian Administration, affecting user-related features. Users could not load the Users and Groups pages and user IDP syncing encountered errors, impacting administrator and end-user account management and authentication. The incident was categorized as degraded functionality within the Authentication and User Management component.

Confluence experienced a partial outage due to Forge invocation errors impacting some marketplace apps for a subset of customers in the Singapore region. The incident affected related Atlassian services (Confluence, Jira Service Management, Jira, and Atlassian Developer Cloud users relying on marketplace apps) and could have caused failures or degraded app functionality. The issue began at 9:45 PM UTC and was resolved by 10:35 PM UTC, lasting about 50 minutes.

Confluence experienced degraded search functionality affecting some users in Europe. The outage began at 8:35 AM UTC and was resolved by 10:45 AM UTC, lasting about 2 hours and 10 minutes. The issue impacted the search component of Confluence, limiting users' ability to locate content. The Atlassian status page indicated an investigation into the degradation and later confirmed restoration, with 2 status updates issued during the incident. Regional impact was limited to Europe, with no widespread disruption reported elsewhere.

Confluence experienced degraded outgoing email delivery, impacting emails from Confluence and a broad set of Atlassian products including Jira Work Management, Jira Service Management, Jira, Opsgenie, Trello, Bitbucket, Guard, Jira Align, Jira Product Discovery, Atlas, Compass, and Loom Cloud. Customers may experience delays or failures receiving emails. The issue was isolated to the Notifications component, began at Jun 4, 2025 5:20 PM UTC, and was resolved by Jun 4, 2025 6:00 PM UTC. The status page noted the system was recovering and mail processing was returning to normal as of 4:45 PM UTC. Two status updates were published during the incident.

Confluence experienced an admin access outage when the Administration component returned a 403 error, blocking access to the administration area for a period. The outage began at May 27, 2025 6:55 AM UTC and was resolved by May 27, 2025 7:35 AM UTC, lasting approximately 40 minutes. Administrators were unable to reach the Administration panel and administrative tasks could not be performed during the incident. The Atlassian status page noted the issue and issued two updates during the event.

Confluence experienced an authentication outage starting at May 26, 2025 5:20 AM UTC, affecting the Authentication and User Management component and causing login failures and 503 gateway errors across multiple services.

The incident lasted about 41 minutes and was resolved by May 26, 2025 6:01 AM UTC when the status page indicated the affected component had returned to normal operation. During the outage, users attempting to sign in may have been unable to access authenticated features or perform actions requiring login. Confluence stated that engineers were investigating with urgency to restore authentication.