Jira outage on September 11, 2026: Degraded performance affecting Jira Software and Jira Service Management
Jira reported an incident affecting Jira for 51 minutes on 11 September 2026, from 07:46 to 08:37 UTC.
Resolved
Official incident reported by Jira
- Started
- 07:46
- 11 Sep 2026 UTC
- Resolved
- 08:37
- 11 Sep 2026 UTC
- Duration
- 51m
- 51 minutes
- Impact
- Minor
- as rated by Jira
- Updates
- 4
- posted by Jira
Timeline
All times UTC.
Official incident from Jira
Degraded performance affecting Jira Software and Jira Service Management
-
Official
Investigating
We are investigating reports of an issue affecting Jira Software and Jira Service Management. Affected users may experience errors or delays when loading issue views and viewing boards. We are working to identify the root cause and will provide an update as more information becomes available.
-
Official
Monitoring
A mitigation has been deployed, and we are observing recovery across Jira Software and Jira Service Management issue views and boards. Our engineering teams are closely monitoring the environment to ensure sustained stability. We will provide another update once full resolution is confirmed or within 60 minutes.
-
Official
Resolved
On 11 September 2026, Between 07:02 UTC and 07:56 UTC, some Jira Software and Jira Service Management users may have experienced degraded performance and errors when accessing Work Items and Boards. The issue has now been resolved, and all services are operating normally.
-
Official
Postmortem
### Summary On September 11, 2026, between 07:02 and 07:56 UTC, Atlassian customers primarily from the EU region and some from APAC region using Jira and Jira Service Management products were unable to view work items or access boards consistently. The event was triggered by a backward-incompatible internal configuration rollout in the underlying graph data platform. The incident was detected within 3 minutes by our automated monitoring system and mitigated by rolling forward the stable deployment to all regions. The total time to resolution was about 54 minutes. ### IMPACT The overall impact occurred between September 11, 2026, 07:02 UTC and September 11, 2026, 07:56 UTC on two products. During this period, some customers in the EU region using Jira and Jira Service Management experienced intermittent failures or degraded performance. We noted that a configuration failure prevented critical dependency services from scaling, which resulted in an outage for affected users. Jira and Jira Service Management users experienced timeout errors and failed or delayed page loads when attempting to access the work item view, issue navigator, and board view. ### ROOT CAUSE The incident was...
"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.