Changes / Jira / Disrupted JIRA and JSM availability
Jira: Critical incident: Disrupted JIRA and JSM availability
Summary
Jira reported a critical outage affecting Jira and JSM access for some users in us-east-1, with connection failures and unavailable services. It started at 2026-02-06 20:24 UTC and was resolved at 2026-02-07 05:38 UTC, lasting 9 h 13 min; mitigation efforts included initiating a point-in-time recovery.
Machine-written from the diff below (Sol; type: incident outage). Check the diff before relying on it.
What changed
Before: not present
After: Disrupted JIRA and JSM availability
Before: not present
After: critical
Before: not present
After: resolved
Before: not present
After: 2026-02-06 20:24 UTC
Before: not present
After: 2026-02-07 05:38 UTC
Before: not present
After: Administration, Authentication and User Management, Automation for Jira, Create and edit, Marketplace, Mobile, Notifications, Purchasing & Licensing, Search, Signup, Viewing content
Before: not present
After: 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.
Before: not present
After: 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.
Before: not present
After: 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.
Before: not present
After: 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.
Before: not present
After: 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.
Before: not present
After: Our teams have restored access for most users in us-east-1 region, and continue to work diligently towards full mitigation.
Before: not present
After: The issue has now been resolved, and services are operating normally for all affected customers. We will continue to monitor closely to confirm stability.
Before: not present
After: 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.
First version of this incident archived by Rewindex. View the live incident (opens in new tab).
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Critical incident: Disrupted JIRA and JSM availability (this change) Jira reported a critical outage affecting Jira and JSM access for some users in us-east-1, with connection failures and unavailable services. It started at 2026-02-06 20:24 UTC and was resolved at 2026-02-07 05:38 UTC, lasting 9 h 13 min; mitigation efforts included initiating a point-in-time recovery. | Major incident |