Jira outage on September 3, 2026: Disrupted JIRA availability in US East

Jira reported an incident affecting Jira for 1 hour 5 minutes on 3 September 2026, from 15:57 to 17:02 UTC.

jira.atlassian.com All times UTC

Resolved

Official incident reported by Jira

Started: 15:57; 3 Sep 2026 UTC
Resolved: 17:02; 3 Sep 2026 UTC
Duration: 1h 5m; 1 hour 5 minutes
Impact: Critical; as rated by Jira
Updates: 4; posted by Jira

Timeline

All times UTC.

Official incident from Jira

Disrupted JIRA availability in US East

Postmortem Critical impact 3 Sep 2026 15:57 UTC View on Jira's status page

3 Sep 15:57 Official
Investigating
We are actively investigating reports of a service disruption affecting JIRA customers in US East. We will share updates here as more information is available.
3 Sep 16:35 Official
Monitoring
Our teams have taken mitigation steps to reduce the impact and recovery among affected customers began at 16:15 UTC. We continue to investigate the root cause of the issue, and will share additional updates here as more information is available.
3 Sep 17:02 Official
Resolved
On September 3, 2026, JIRA 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.
10 Sep 18:15 Official
Postmortem
### Summary On September 3, 2026, between 14:52 and 17:02 UTC, Atlassian customers using Jira and Jira Service Management in the US-East region experienced intermittent errors and degraded access to core Jira experiences, including Rovo, viewing issues, boards, navigation, search-backed experiences, workflow-related actions. The event was triggered by a progressive rollout of a caching change in Atlassian's authorization service. The change increased cache traffic and caused saturation in the cache layer used for authorization checks, which then resulted in timeouts and service errors for some customers in the region. The incident was detected by our monitoring within approximately 12 minutes. We mitigated by deploying the affected cache service and disabling the feature flags associated with the new cache path. The total time to resolution was 2 hours and 10 minutes. ### IMPACT The overall impact occurred on September 3, 2026 between 14:52 and 17:02 UTC. During this period, some customers in the US-East region using Jira and Jira Service Management experienced intermittent failures or degraded performance when accessing experiences that depend on authorization checks. These...

"Official" rows are quoted from Jira's public status page, jira-software.status.atlassian.com. Very long posts are shortened.

What our checkpoints saw

HostTracker's checkpoints, which test jira.atlassian.com from several locations, recorded no outage of 5 minutes or longer during this incident. A provider can report a problem that affects only some features, regions or accounts, which a check of the main address does not see. The live Jira status shows what our checks see right now.

All Jira incidents Live Jira status Every service we track

Does your product depend on Jira?

An outage like this one reaches your users through your product, and most teams hear about it from a customer rather than from a dashboard. HostTracker watches any endpoint you name - your own site, an API you call, a vendor you resell - from 300+ locations, confirms a failure from several of them before it says anything, and then tells you by email, SMS, voice call or your chat tool.

You get the same record you are reading here for your own services: every outage timestamped, with the checks that observed it.

Start monitoring free Check another address

Independent measurement by HostTracker. Not affiliated with Jira. Official updates are quoted from Jira's public status page and remain Jira's own words.