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

**Summary:** A critical outage prevented some users in us-east-1 from accessing Jira and JSM, starting 2026-02-05 14:13 UTC and resolving 2026-02-05 21:38 UTC, lasting 7 h 25 min. Jira placed affected sites in maintenance mode to expedite resolution; services returned to normal for all affected customers. _(machine-written, sol)_
- Kind: Major incident · Label: outage (model (Jev))
- Changed: 2026-02-05 14:13 UTC · Detected: 2026-10-17 18:22 UTC
- [Source: https://stspg.io/k304xzjryrpj](https://stspg.io/k304xzjryrpj)
- [Company: Jira](https://rewindex.com/company/jira.md)
- Versions: before (none: first archived) → after incident\_version:103/zgn6gvq0mdpj@fc6f99a5fff7
- Change 1 of 1 for this incident

## What changed

**1. Added: Title**

```diff
+ Some users in us-east-1 region unable to access Jira and JSM.
```

**2. Added: Impact**

```diff
+ critical
```

**3. Added: Status**

```diff
+ resolved
```

**4. Added: Start time**

```diff
+ 2026-02-05 14:13 UTC
```

**5. Added: Resolved time**

```diff
+ 2026-02-05 21:38 UTC
```

**6. Added: Affected components**

```diff
+ Administration, Authentication and User Management, Automation for Jira, Create and edit, Marketplace, Mobile, Notifications, Purchasing & Licensing, Search, Signup, Viewing content
```

**7. Added: Update** (investigating) · 2026-02-05 14:13 UTC

```diff
+ 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.
```

**8. Added: Update** (identified) · 2026-02-05 14:40 UTC

```diff
+ 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.
```

**9. Added: Update** (identified) · 2026-02-05 15:39 UTC

```diff
+ 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.
```

**10. Added: Update** (identified) · 2026-02-05 17:35 UTC

```diff
+ 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.
```

**11. Added: Update** (identified) · 2026-02-05 19:22 UTC

```diff
+ 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.
```

**12. Added: Update** (monitoring) · 2026-02-05 21:09 UTC

```diff
+ The issue has now been resolved, and services are operating normally for all affected customers. We will continue to monitor closely to confirm stability.
```

**13. Added: Update** (resolved) · 2026-02-05 21:38 UTC

```diff
+ 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.
```

## History of this incident

| When (UTC) | Change | Label |
| --- | --- | --- |
| 2026-02-05 14:13 UTC | Critical incident: Some users in us-east-1 region unable to access Jira and JSM. (this change) | outage |

All Jira changes: [timeline](https://rewindex.com/company/jira/changes.md)
_Diff excerpts are shown on normalized text: dates, counters and tokens appear as ‹date›, ‹count›, ‹tok›; noise-only edits are hidden. Rewindex shows the changed passages, not a copy of the page._


---
Canonical: https://rewindex.com/change/ibd29aa088de43e · Markdown: https://rewindex.com/change/ibd29aa088de43e.md · JSON: https://rewindex.com/api/v1/changes/ibd29aa088de43e · Generated 2026-10-18T02:54:40.574Z