# Some users in us-east-1 region unable to access Jira and JSM.

- Provider: [Jira](https://down.guide/jira)
- Level: confirmed
- Impact: Major outage
- lasted 7h 25m
- started 2026-02-05 14:13 UTC
- Viewing content, Create and edit, Authentication and User Management +8
- us, us-east-1
- id: DWN-2b51957a88
- Official page: https://stspg.io/k304xzjryrpj

## Updates from Jira
### 2026-02-05 14:13 UTC: investigating
Some users in us-east-1 region might not be able to access Jira and JSM.
We are aware of this issue and are actively investigating the same.
We will provide update on the progress in next 60 minutes or sooner.

### 2026-02-05 14:40 UTC: identified
Some users in the us-east-1 region cannot access Jira and JSM.
We have identified the cause and placed Jira and JSM in maintenance mode for the affected sites to expedite resolution.
We will provide update on the progress in next 60 minutes or sooner.

### 2026-02-05 15:39 UTC: identified
We have identified the 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-05 17:35 UTC: identified
Our team is diligently working on a mitigation, with access being restored for some users in us-east-1 region.
We will continue to share additional updates here as more information is available.

### 2026-02-05 19:22 UTC: identified
Our teams have restored access for most users in us-east-1 region, and continue to work diligently towards full mitigation.
We will continue to share additional updates here as more information is available.

### 2026-02-05 21:09 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-05 21:38 UTC: resolved
On February 5, 2026, JIRA and JIRA Service Management 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-2b51957a88), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.