Jira outage on August 27, 2026: Issues accessing multiple Atlassian products in some regions
Jira reported an incident affecting Jira for 54 minutes on 27 August 2026, from 04:22 to 05:16 UTC.
Resolved
Official incident reported by Jira
- Started
- 04:22
- 27 Aug 2026 UTC
- Resolved
- 05:16
- 27 Aug 2026 UTC
- Duration
- 54m
- 54 minutes
- Impact
- Critical
- as rated by Jira
- Updates
- 6
- posted by Jira
Timeline
All times UTC.
Official incident from Jira
Issues accessing multiple Atlassian products in some regions
-
Official
Investigating
Our teams have identified this issue is also impacting Jira Service Management. We will update further as soon as possible.
-
Official
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.
-
Official
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.
-
Official
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.
-
Official
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.
-
Official
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 monitoring systems, and mitigated by rolling back to the previous configuration release, which put the proxy fleet into a known good state. After the proxy fleet recovered, some Jira and Confluence customers (regardless of location) received HTTP 503 errors between 04:33 and 04:53 UTC as server fleets adjusted to the influx of traffic. **IMPACT** The overall impact was split into two discrete periods: - First, on 27 August 2026, between 03:51 and 04:35 UTC on Atlassian Analytics, Compass, Confluence, Focus, Guard, Jira, JPD, JSM, Opsgenie, Rovo Search, and Talent. The incident caused service disruption...
"Official" rows are quoted from Jira's public status page, jira-software.status.atlassian.com. Very long posts are shortened.
What our checkpoints saw
HostTracker's checkpoints, which test jira.atlassian.com from several locations, recorded no outage of 5 minutes or longer during this incident. A provider can report a problem that affects only some features, regions or accounts, which a check of the main address does not see. The live Jira status shows what our checks see right now.
Does your product depend on Jira?
An outage like this one reaches your users through your product, and most teams hear about it from a customer rather than from a dashboard. HostTracker watches any endpoint you name - your own site, an API you call, a vendor you resell - from 300+ locations, confirms a failure from several of them before it says anything, and then tells you by email, SMS, voice call or your chat tool.
You get the same record you are reading here for your own services: every outage timestamped, with the checks that observed it.
Independent measurement by HostTracker. Not affiliated with Jira. Official updates are quoted from Jira's public status page and remain Jira's own words.