Confluence outage history

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.

The Confluence outage affected the Admin Groups page in Atlassian Administration. From 11:00 AM UTC, admins were unable to click on any group from the Groups page and could not add or remove users or modify app access for groups while using admin.atlassian.com. The Administration component was impacted and the issue lasted for about 30 minutes, with service returning to normal by 11:30 AM UTC.

The Atlassian status page documented the incident and noted ongoing investigation, with an update indicating resolution by 11:30 AM UTC. The incident involved the Administration component and included two status updates during its course.

Paragraph 1: Atlassian reported an OAuth authentication disruption affecting Confluence and Jira Mobile. Users attempting to sign in via OAuth experienced interruptions in the mobile sign-in flow. The issue primarily impacted the Mobile / iOS App and Mobile / Android App, and could disrupt Forge installations and invocations.

Paragraph 2: The Atlassian status page issued two updates during the incident. The outage began at 10:20 AM UTC and was resolved by 10:55 AM UTC, lasting about 35 minutes. The final update indicated that affected services were back to normal.

Confluence Cloud experienced a partial outage affecting some users, with the Confluence site reported as unreachable for portions of the user base. The incident impacted two core components: View Content and Create and Edit. The disruption began at 3:30 PM UTC and was resolved by 4:35 PM UTC, lasting about 1 hour and 5 minutes. Atlassian's status page indicated an active investigation and later updates as the issue was addressed, with two official updates issued during the incident.

User reports described login issues, server connectivity problems, and HTTP 500/503 errors, suggesting the outage affected content viewing and editing across multiple regions rather than being localized to a single area.

Confluence Cloud experienced a partial outage starting around 2:57 PM UTC, with some users unable to load pages, access the portal, or perform create/edit actions. Reports described login failures and connectivity issues, including errors such as 500 or 503 responses. The disruption affected two components: View Content and Create and Edit. StatusGator detected the issue at Jan 8, 2026 2:57 PM UTC, about 33 minutes before Atlassian acknowledged it on their status page at Jan 8, 2026 3:30 PM UTC. Some observations persisted until around 3:45 PM UTC. The provider issued two status updates during the incident (at Jan 8, 2026 3:30 PM UTC and Jan 8, 2026 4:35 PM UTC) and later restored service.

An outage affected Confluence across Atlassian Cloud, starting at 2:50 AM UTC and lasting approximately 2 hours and 30 minutes, with recovery by 5:20 AM UTC. The incident disrupted outbound email delivery, mobile push notifications, and the ability to generate support tickets across all Atlassian Cloud products, meaning users could miss notifications and were unable to submit or route support requests during the outage. The disruption impacted the overall user experience across Atlassian Cloud services.