Is Jira Down Today?

Common Jira issues

• →JQL searches timing out
• →Boards showing stale issue states
• →Workflow transitions failing for some users

• Degraded performance affecting Jira Software and Jira Service Management

  resolved

  On 11 September 2026, Between 07:02 UTC and 07:56 UTC, some Jira Software and Jira Service Management users may have experienced degraded performance and errors when accessing Work Items and Boards. The issue has now been resolved, and all services are operating normally.

  Sep 11, 2026Details →

• Disrupted JIRA availability in US East

  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 included issue view, Rovo, board view, navigation, search-backed experiences, API, and workflow-related actions. ### ROOT CAUSE The issue was caused by a progressive rollout of a new cache path in Atlassian’s authorization service. The change was intended to improve scalability for customers with large authorization datasets by changing how some authorization information was cached. During the rollout, both the existing and new cache paths were active for consistency checks, which increased the number of cache entries and cache operations. In the US-East region, where traffic volume was highest, this additional load saturated parts of the shared cache layer. As cache requests timed out, the authorization service made more fallback requests to upstream systems, further increasing load and causing circuit breakers and timeouts. Dependent Jira experiences that require authorization checks then returned intermittent errors or failed to load for affected users. The initial rollout monitoring did not surface the risk early enough because lower-traffic regions did not show the same level of degradation and some alerts were not scoped or routed in a way that highlighted the regional cache saturation before customer impact grew. ### REMEDIAL ACTIONS PLAN & NEXT STEPS We know that outages impact customer productivity, and we apologize to customers who were affected during this incident. We are prioritizing the following improvement actions to help reduce the likelihood and impact of similar incidents: - **Enhance deployment safeguards:** Improve rollout practices for high-risk cache and authorization-service changes by using smaller, region-aware rollout increments and validating behavior in higher-traffic regions before broader enablement. - **Implement graceful degradation:** Evaluate graceful-degradation options for authorization checks so dependent experiences can continue working, if a cache dependency is unavailable. - **Strengthen regional telemetry and capacity monitoring:** Strengthen cache capacity and health monitoring, including regional detectors for cache CPU, memory pressure, hit rate, eviction rate, timeout rate, and connection behavior. - **Expand production-scale load testing:** Review cache design and capacity planning for authorization data so changes that increase key cardinality or cache operations are load-tested against representative production-scale traffic before rollout. - **Harden client resilience:** Review cache client timeout and reconnect behavior to reduce the risk of connection storms when cache nodes become slow or saturated. We will continue to validate these actions through the incident review process and track them to completion with the responsible engineering teams. Thanks, Atlassian Customer Support

  Sep 3, 2026Details →

• Degraded performance of JIRA

  resolved

  On September 1, some JIRA users may have experienced performance degradation affecting forms functionality. The issue has now been resolved, and the service is operating normally for all affected customers.

  Sep 1, 2026Details →

• Jira - Work Item transition failures

  resolved

  On 1st Sept 2026, between 04:22 UTC to 10:59 UTC, some Jira users may have experienced service disruptions. The issue has now been resolved and the service is operating normally for all the customers.

  Sep 1, 2026Details →

• Fetching mails from Microsoft accounts producing errors and preventing email based creation of Jira work items

  resolved

  We're now seeing full recovery across Atlassian services that have been impacted, and this incident is now resolved. For those continuing to experience issues relating to this incident we encourage you to please check https://status.cloud.microsoft/ as they continue to provide further updates about additional services.

  Aug 31, 2026Details →