Disrupted JIRA availability in US East
### 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 custo
The latest update from Jira.
State
Resolved
Started
59 d ago
2026-09-03 15:57 UTC
Lasted
1 h 5 min
until 2026-09-03 17:02 UTC
Worst impact
Major outage
Timeline
4 updatesInvestigating
38 min 60%
Monitoring
26 min 40%
Updates
Times in UTCAs posted by Jira
### 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 custo
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.
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.
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.
Affected components
11Jira in the last 90 days
Full historyIncidents in 90 days
14
Days with an incident
11
Median duration
2 h 15 min
This incident
52% shorter than the median
Other Jira incidents
All incidentsJira·Jira - Project Sidebar Loading Degradation
On October 21, 2026, JIRA, JSM, JPD, and JWM users may have experienced performance degradation impacting the project sidebar and navigation. The issue has now been resolved, and the service is operating normally for all affected customers.
Jira·Job processing and scheduling is degraded affecting multiple Atlassian products
### Summary On October 1, 2026, between 01:00 and 07:25 UTC, degraded job processing and scheduling impacted Atlassian products including Bitbucket Cloud, Confluence, Forge apps, Jira, and Jira Service Management in all commercial cloud regions. This caused delayed or missed background tasks, such as email-to-ticket processing and scheduled pipelines; interactive product use was not affected. The event was triggered when an unexpected volume of scheduled tasks became due simultaneously, overwhelming our shared job scheduling platform. Automated monitoring detected the incident within three minutes. Recovery began around 03:45 UTC as engineering scaled capacity and the platform worked through the backlog, with full resolution reached in 6 hours and 25 minutes. ### IMPACT Most scheduled tasks stopped running at 01:00 UTC and resumed from about 03:45 UTC. Most delayed work had caught up by about 06:00 UTC, and the remaining delays had cleared by 07:25 UTC. Across affected products: - Recu
Jira·Degraded Performance Viewing Issues and Boards
On September 24th 2026, some Jira and JSM users in the US region may have experienced a performance degradation impacting Jira issue creation, issue viewing, and board loading. The issue has now been resolved, and the service is operating normally for all affected customers.
Jira·Degraded Performance Accessing Jira
On Sept 24th, 2026, between 07:28 to 08:08 UTC, some Jira users may have experienced errors or degraded performance when accessing Jira and viewing issues. The issue has now been resolved and the service is operating normally for all customers.
Jira·Degraded performance affecting Jira Software and Jira Service Management
### Summary On September 11, 2026, between 07:02 and 07:56 UTC, Atlassian customers primarily from the EU region and some from APAC region using Jira and Jira Service Management products were unable to view work items or access boards consistently. The event was triggered by a backward-incompatible internal configuration rollout in the underlying graph data platform. The incident was detected within 3 minutes by our automated monitoring system and mitigated by rolling forward the stable deployment to all regions. The total time to resolution was about 54 minutes. ### IMPACT The overall impact occurred between September 11, 2026, 07:02 UTC and September 11, 2026, 07:56 UTC on two products. During this period, some customers in the EU region using Jira and Jira Service Management experienced intermittent failures or degraded performance. We noted that a configuration failure prevented critical dependency services from scaling, which resulted in an outage for affected users. Jira and Jira
Follow Jira
Your coding agent knows when Jira is down, and tells you when a failure is theirs, not yours. You can also get Jira incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "jira" and tell me if Jira has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.cc/feed.xml?providers=jira/feed subscribe https://outages.cc/feed.xml?providers=jiraFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane