Issues accessing multiple Atlassian products in some regions

Timeline

1. 04:22 UTC Jira status page · Reported Issues accessing multiple Atlassian products in some regions
2. 04:22 UTC Jira status page · Investigating Our teams have identified this issue is also impacting Jira Service Management. We will update further as soon as possible.
3. 04:25 UTC Jira status page · Investigating We are investigating an issue with accessing products that is impacting Confluence, Jira Cloud and Jira Serivce Management customers. Our team is urgently investigating this issue and we will provide further details within one hour or sooner if information is available.
4. 04:33 UTC Jira status page · Identified Our teams have identified a possible fix for the issues impacting Jira Cloud, Jira Service Management and Confluence. This is now being rolled out to impacted regions and we will update within one hour, or sooner if further information is available.
5. 04:51 UTC Jira status page · Monitoring The issues relating to loading Jira Cloud, Jira Service Management and Confluence are now in recovery. We'll continue to monitor closely to confirm stability and provide an update within one hour, or sooner as more information becomes available.
6. 05:16 UTC Jira status page · Resolved On 27 August 2026 UTC, Atlassian products including Jira Cloud, Jira Service Management and Confluence experienced a disruption, and services were unavailable to affected users. The issue has now been resolved, and the service is operating normally for all affected customers. A public postmortem for this incident will be made available on this page when our full investigation of the incident has been completed.
7. 02:53 UTC Jira status page · Postmortem **SUMMARY** On August 27, 2026, between 03:51 and 04:35 UTC, Atlassian customers in the Western Europe and Southeast APAC regions were unable to reach Atlassian Cloud products, including Atlassian Analytics, Compass, Confluence, Focus, Guard, Jira, JPD, JSM, Opsgenie, Rovo Search, and Talent. The event was triggered by a defective code change to the routing layer of one of our proxy fleets. This led to HTTP 404 errors being served to all customer traffic through these proxy fleets in Western Europe and Southeast APAC regions. The incident was detected within 1 minute by our automated…