Is Jira Software down?

We are investigating an issue impacting the project sidebar and navigation in Jira Cloud. Users may encounter timeouts or missing menus when attempting to access project views. Teams are actively analyzing telemetry to identify a mitigation. We will provide our next update in 60 minutes, or sooner.

Mitigations are in place and we are seeing recovery across Jira Cloud navigation services. Project sidebars are now loading as expected. Our teams continue to monitor the situation, and we expect to confirm full resolution in our next update in 1 hour or sooner.

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.

Job processing and job scheduling is degraded, which is affecting scheduled and asynchronous work across several products, including Jira, Confluence and Bitbucket Cloud. Affected users may see delayed or missing job execution, including delayed email-to-ticket processing and schedules that do not run as expected.

Our teams have identified the root cause of this incident and is now actively working on mitigating the issue. We will provide further updates within an hour or sooner if we have any significant progress to share.

Our teams have taken corrective steps to mitigate the issue and are observing some improvements. We continue to monitor the situation and will take necessary actions until the incident is fully recovered.

Our teams continue to work on recovery until the incident is fully resolved. We will provide further updates if we have significant progress to share. Along with impact to scheduled and asynchronous work across several products, we also identified SLA component in Jira Service Management is not appearing as expected.

Our teams continue to work on recovery until the incident is fully resolved. We will provide further updates if we have significant progress to share. There is also an impact to the new support tickets created in terms of missing SLA component, notifications which may be affecting the response times and backlog management of some tickets.

On 01st Oct 2026, between 01:00 UTC and 07:25 UTC, users may have seen missing job execution, including delayed email-to-ticket processing and schedules that do not run as expected. We have now implemented a fix and and services have been restored to normal operation for affected customers. The impact to support tickets with missing SLA component and delayed notifications have also confirmed recovery. Note: For Bitbucket customers, if there was any scheduled pipelines that did not run during the incident window, you may wait for the next scheduled execution or trigger them manually.

### 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: - Recurring scheduled tasks skipped or delayed runs due during the incident; skipped runs were not automatically re-run, and tasks resumed at their next scheduled time. - Most one-time scheduled tasks ran late; a small number may not have run. - Automation rules, including scheduled rules, ran normally, except as noted below. Bitbucket Cloud Scheduled pipelines due between 01:00 and about 03:50 UTC did not run. If a scheduled pipeline did not run during the incident, you can wait for the next scheduled execution or trigger it manually. Other pipeline runs were not affected. Confluence Some calendar event reminders due between 01:00 and about 03:45 UTC were not sent. Forge apps Scheduled triggers stopped at 01:00 UTC and resumed from about 04:00 UTC; missed invocations were not replayed. Goals Start of the month email reminders to update goals could be delayed. Jira and Jira Service Management Incoming emails stayed in their mailboxes and were processed automatically after recovery. Scheduled notifications, such as filter subscriptions, were delayed. In some service projects, automation rules and notifications triggered by SLAs or time in status ran late. SLA timer data remained intact. Atlassian Support Until 07:25 UTC, issues with our support tools may have slowed some of our responses. Based on our investigation to date, we have not identified any loss of work items, pages, repositories, or incoming emails. ### ROOT CAUSE Our shared job scheduling platform operates at high scale under normal conditions. One of the platform consumers scheduled an abnormally high volume of tasks to be executed at the same time on October 1st at 01:00 UTC. This order-of-magnitude surge exceeded our architectural and scaling limits, creating a processing backlog across dependent services. Engineering manually increased capacity to handle the abnormal load, enabling the service to process the backlog and return to normal operations. ### REMEDIAL ACTIONS PLAN & NEXT STEPS We know that delayed and missed work affects your productivity. We are prioritizing these actions to help reduce the likelihood and impact of similar incidents: - **Enhance workload isolation:** Implement fair scheduling guardrails so volume surges from a single source do not starve or delay tasks across other products. - **Strengthen surge controls:** Add operational capabilities to quickly throttle or pause scheduled workloads from specific sources during unexpected traffic spikes. - **Improve system scaling and recovery:** Enhance platform capacity and optimize scaling processes to handle extreme demand spikes and recover more rapidly. We apologize to customers whose services were impacted during this incident. Thanks, Atlassian

We continue to investigate the issue impacting Jira issue creation, issue viewing, and board loading. Our teams remain engaged on identifying a resolution. We will provide the next update in 1 hour, or sooner if there is material progress.

Mitigations have been deployed and we are seeing positive signs of recovery across Jira. Issues viewing work items, loading boards, and creating tickets are subsiding. We are continuing to monitor system health to ensure full stability and will share our next update within 60 minutes.

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.

We have been tracking an issue impacting Jira where users may have encountered errors or degraded performance accessing Jira and viewing issues. Mitigations are in place and we are seeing positive signs of recovery. Our teams are continuing to monitor the situation, and we expect to confirm resolution within the next 60 minutes.

We are continuing to closely monitor the situation to ensure full stability across Jira. Recovery signs remain steady. Our next update will be shared in 60 minutes, or sooner.

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.

We are investigating reports of an issue affecting Jira Software and Jira Service Management. Affected users may experience errors or delays when loading issue views and viewing boards. We are working to identify the root cause and will provide an update as more information becomes available.

A mitigation has been deployed, and we are observing recovery across Jira Software and Jira Service Management issue views and boards. Our engineering teams are closely monitoring the environment to ensure sustained stability. We will provide another update once full resolution is confirmed or within 60 minutes.

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.

### 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 Service Management users experienced timeout errors and failed or delayed page loads when attempting to access the work item view, issue navigator, and board view. ### ROOT CAUSE The incident was caused by the deployment of a change to the graph store service, which serves links to third-party entities such as pull requests. The change caused startup checks to fail, preventing new nodes from joining the cluster. During peak traffic, the service could not scale sufficiently, causing requests from Jira and Jira Service Management to the graph store service to fail. ### REMEDIAL ACTIONS PLAN & NEXT STEPS We know that outages impact your productivity. We are prioritizing the following improvement actions to avoid repeating this type of incident: - Implement Code-Based Configuration: We are moving configuration definition files to be part of the core codebase to ensure they are versioned and deployed synchronously with the application logic. - Graceful Degradation in Jira: We are implementing changes to the affected Jira views to segregate core queries from noncritical dependency queries, allowing the page to remain functional even if a downstream service fails. - Optimize Deployment Pipeline: Deployment pipelines are being optimized to enable accelerated, parallel updates during operational response scenarios. We apologize to customers whose services were impacted during this incident; we are taking immediate steps to improve the platform’s performance and availability. Thanks, Atlassian Customer Support