What the postmortem adds
Atlassian reports September 3, 2026, 14:52–17:02 UTC impact in US East. A new authorization-cache path overloaded the cache layer, disrupting some Jira and Jira Service Management experiences.
Read Atlassian's postmortem, published September 10 at 18:15 UTC.
Timeline (UTC)
| September 3 time | Provider-reported milestone |
|---|---|
| 14:52 | Impact began, established retrospectively |
| 15:57 | Public investigation update |
| 16:15 | Recovery began, reported in the 16:35 update |
| 17:02 | Incident resolved |
The stated impact interval is 2 hours, 10 minutes. It does not measure every customer's downtime.
Postmortem update
This revision incorporates the later postmortem. The earlier report used the first investigation post as its start field and said the cause was unavailable. The publication date of this article remains September 5.
Check your services
See current Jira status for present conditions and Jira incident history for other events. Follow Jira to save it, then configure alert delivery in Settings.