- 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, us-east-1
- Down Index
- 62of 100
What to do
Check whether you use Jira Viewing content, Create and edit, Authentication and User Management, Search and 7 more in us, us-east-1. 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 9h 13m it lasted.
Anything that failed between 2026-02-06 20:24 UTC and 2026-02-07 05:38 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 8
- identified
We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Some users in us-east-1 region may not be able to access Jira and JSM. We will continue to share additional updates here as more information is available.
provider
- identified
Impact The incident is affecting users of the Jira product, resulting in connection failures in specific impacted areas. Customers might be experiencing difficulties accessing or operating certain features within Jira due to this disruption. Current Status Our teams are actively addressing the situation, with restoration activities underway. Key efforts include initiating a point-in-time recovery to restore service as efficiently as possible. Next Steps The incident response team is focusing on the recovery process to resolve the issue. Further communication will be provided in 30 minutes.
provider
- identified
We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Some users in us-east-1 region might not be able to access Jira and JSM. We will continue to share additional updates here as more information is available.
provider
- identified
Our teams are diligently working on a mitigation. Some users in us-east-1 region may not be able to access JIRA and JSM. We will continue to share additioanl updates here as more information is available.
provider
- identified
Our teams are in final stages of mitigation. During this time, some users in us-east-1 region may not be able to access JIRA and JSM. We will continue to share additional updates here as more information is available.
provider
- identified
Our teams have restored access for most users in us-east-1 region, and continue to work diligently towards full mitigation.
provider
- monitoring
The issue has now been resolved, and services are operating normally for all affected customers. We will continue to monitor closely to confirm stability.
provider
- resolved
On February 6, 2026, JIRA and JSM 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.
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-76c53926a5
Is Jira still down?
No, this incident was resolved 2026-02-07 05:38 UTC. For Jira's live state, see https://down.guide/jira.
How long did it last?
9h 13m, from 2026-02-06 20:24 UTC to 2026-02-07 05:38 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, us-east-1.
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.