# Disrupted JIRA and JSM availability

- Provider: [Jira](https://down.guide/jira)
- Level: confirmed
- Impact: Major outage
- lasted 9h 13m
- started 2026-02-06 20:24 UTC
- Viewing content, Create and edit, Authentication and User Management +8
- us, us-east-1
- id: DWN-76c53926a5
- Official page: https://stspg.io/fgnlwb20d8kp

## Updates from Jira
### 2026-02-06 20:24 UTC: 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.

### 2026-02-06 20:24 UTC: 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.

### 2026-02-06 20:26 UTC: 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.

### 2026-02-06 22:33 UTC: 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.

### 2026-02-07 02:22 UTC: 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.

### 2026-02-07 03:43 UTC: identified
Our teams have restored access for most users in us-east-1 region, and continue to work diligently towards full mitigation.

### 2026-02-07 05:28 UTC: 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.

### 2026-02-07 05:38 UTC: 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.

From the builder: does your app depend on Jira? [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=jira) detects problems in your own logs without hand-written monitors, and you can ask it in plain language which errors mention Jira.

---
down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=DWN-76c53926a5), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
