# Jira: Disrupted JIRA and JSM availability

- Impact (vendor’s label): critical
- Status: resolved
- Started: 2026-02-06 20:24 UTC · Resolved: 2026-02-07 05:38 UTC · Duration: 9.2 h
- Updates: 8 · Affected components: Purchasing & Licensing, Mobile, Marketplace, Automation for Jira, Create and edit, Signup, Viewing content, Administration, Search, Authentication and User Management, Notifications
- [Vendor status page: https://stspg.io/fgnlwb20d8kp](https://stspg.io/fgnlwb20d8kp)
- [Company: Jira](https://rewindex.com/company/jira.md)

## 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, sol)_
## Timeline of updates

- **identified** 2026-02-06 20:24 UTC: 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.
- **identified** 2026-02-06 20:24 UTC: 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.
- **identified** 2026-02-06 20:26 UTC: 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.
- **identified** 2026-02-06 22:33 UTC: 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.
- **identified** 2026-02-07 02:22 UTC: 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.
- **identified** 2026-02-07 03:43 UTC: Our teams have restored access for most users in us-east-1 region, and continue to work diligently towards full mitigation.
- **monitoring** 2026-02-07 05:28 UTC: The issue has now been resolved, and services are operating normally for all affected customers. We will continue to monitor closely to confirm stability.
- **resolved** 2026-02-07 05:38 UTC: 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.

## Rewindex changes for this incident

- 2026-02-06 20:24 UTC: [Critical incident: Disrupted JIRA and JSM availability](https://rewindex.com/change/i99288b4f52e383.md)


---
Canonical: https://rewindex.com/company/jira/incidents/7yg61d3jfpdp · Markdown: https://rewindex.com/company/jira/incidents/7yg61d3jfpdp.md · JSON: https://rewindex.com/api/v1/companies/jira/incidents/7yg61d3jfpdp · Generated 2026-10-18T13:34:38.159Z