- Level
- confirmed
- Worst impact
- Major outage
- Components
- Viewing content, Create and edit, Authentication and User Management, Search, Notifications, Administration, Marketplace, Mobile, Purchasing & Licensing, Signup, Automation for Jira
- Regions
- us
- Down Index
- 53of 100
What to do
Check whether you use Jira Viewing content, Create and edit, Authentication and User Management, Search and 7 more in us. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 7m it lasted.
Anything that failed between 2026-05-14 06:41 UTC and 2026-05-14 06:48 UTC may need a replay.Subscribe to Jira's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=jira works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Jira 10
- investigating
We are investigating an issue with multiple Atlassian products that is impacting a large number of Confluence and Jira Cloud customers. We are continuing to investigate and will add further details about additional impact as our investigation continues. We will provide more details within the next hour or sooner if further information becomes available
provider
- investigating
We are aware that the current issues with accessing Atlassian products are impacting additional products. We have now expanded the impact of the incident to cover the known impacted products at this time. We will provide further update within one hour or sooner as information is available.
provider
- identified
Further confirmations of impacted products have now been added to the incident. Our team is investigating the issue with urgency and we will provide further update as soon as it becomes available.
provider
- identified
It is likely if you are experiencing any issues relating to logging in or accessing Atlassian products at this time it is likely due to this ongoing incident. We are continuing to receive reports about expanded product impact resulting from this incident. While our team continues to investigate the issue with urgency, we will continue to provide further updates here with additional information. We will provide further update within one hour, or sooner as further information becomes available.
provider
- identified
Our team has identified the root cause of this issue and is now actively working on mitigating the issue with accessing Atlassian products. At this time, Atlassian customers should also be able to once again raise support requests with our team. We will provide further update within an hour as we are able to progress mitigating this issue.
provider
- monitoring
Our team has implemented a mitigation for this issue and we are now seeing recovery across Atlassian products. We will continue to monitor this issue for any ongoing concerns, and provide further updates here within an hour as we are able to confirm a full recovery has taken place.
provider
- monitoring
We are now able to see recovery for all impacted products, and users should be able to access their products as expected. Our team is continuing to monitor all products and services to ensure there is no further impact, and we will provide further update when this has been validated and the incident is closed.
provider
- monitoring
We are approaching full system recovery at this time, and are performing final confirmations that services are restored.
provider
- resolved
All products and services impacted by this incident should now be fully recovered, and this incident is resolved.
provider
- postmortem
### Summary On May 14, 2026, between 04:30 and 05:26 UTC, Atlassian customers experienced widespread service disruption across multiple Atlassian Cloud products. The issue was caused by a race condition in our internal deployment orchestration platform during a routine rollback operation of a core identity service in the us-east region. This race condition resulted in insufficient capacity for the identity service in the affected region which started returning errors to dependent products. The incident was detected within a minute by automated monitoring systems and mitigated in 56 minutes. ### **IMPACT** During the incident, customers attempting to access Atlassian Cloud products in the us-east region experienced authentication and permission failures and were unable to access services. Customers also experienced errors when accessing the support portal until Atlassian fell back to an alternate support method. This was caused by a core identity service in the us-east region becoming unavailable. Affected products included Atlassian Administration, Atlassian Analytics, Bitbucket, Compass, Confluence, Jira, Jira Product Discovery, Jira Service Management and Trello. Some users outside us-east may have been affected in certain scenarios. ### **ROOT CAUSE** The incident was caused by a race condition in our internal deployment orchestration platform during a routine rollback operation of a core identity service in the us-east region. This race condition resulted in insufficient capacity for the identity service in the affected region which started returning errors to dependent products. ### **REMEDIAL ACTIONS PLAN & NEXT STEPS** We know that outages impact your productivity. Atlassian is prioritizing the following actions to help prevent similar incidents in future: * **Refine deployment orchestration safeguards** * Harden our deployment platform to prevent similar race conditions or resulting capacity loss during a rollback operation. * Streamline mitigation steps when a service becomes unavailable in a region. * **Reduce cross-region impact** * Improve regional isolation and fallback handling so an issue affecting a single region is less likely to impact customers or product functionality in other regions. We recognise how critical reliable access to Atlassian products is for our customers' productivity, and we apologize to customers who were impacted by this incident. Thanks, Atlassian
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-ddb9ad3923
Is Jira still down?
No, this incident was resolved 2026-05-14 06:48 UTC. For Jira's live state, see https://down.guide/jira.
How long did it last?
7m, from 2026-05-14 06:41 UTC to 2026-05-14 06:48 UTC, by the times Jira posted.
What was affected?
Jira named Viewing content, Create and edit, Authentication and User Management, Search and 7 more in us.
What caused it?
Jira hasn't published a root cause. If it does, it shows here.
Where does this come from?
Jira's official status page, https://jira-software.status.atlassian.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.