Jira Software outage history

Jira Software experienced an outage that impacted the Viewing content component, causing pages to fail to load and Jira Console/API access to be unavailable for about an hour. The disruption appeared to be global, with users across multiple regions reporting loading failures, blank pages, or errors while trying to access Jira. Impact began around 11:32 AM UTC and was resolved by 12:24 PM UTC as the Viewing content component came back online. StatusGator detected the issue earlier, with an Early Warning Signal at Aug 7, 2026 10:53 AM UTC, about 38 minutes before the official acknowledgment.

Users attempting to open Jira tickets and boards encountered errors such as 'We couldn't connect to that work item' and were unable to view ticket details. The issue began to surface around 12:45 AM UTC and StatusGator detected the anomaly at Aug 7, 2026 12:47 AM UTC, about 38 minutes before Atlassian acknowledged the problem on the Jira Software status page. The official status updates began at 1:26 AM UTC with a note of degraded performance affecting Viewing content as investigations continued through 1:34 AM UTC; the service returned to normal by 1:44 AM UTC. During the window, users reported issues viewing tickets and boards, consistent with the degraded state. 1:26 AM UTC

Users experienced degraded performance in Jira Software due to delays in automation rule executions, impacting automated workflows across Jira and Jira Service Management. The issue began at 8:19 PM UTC and affected automation-dependent tasks, with ongoing impacts until the team began mitigation efforts. On 4:54 AM UTC the engineering team identified a root cause and started scaling changes to stabilize rule executions, with monitoring planned over the next 24 hours. The service returned to normal by 1:04 AM UTC.

Users experienced degraded performance in Jira Automation rules, affecting automation executions across Jira and Jira Service Management. The incident began at 4:04 PM UTC with automation tasks running slower and some workflows stalling. The affected component was Automation for Jira.

An update at 5:00 PM UTC indicated the likely cause had been identified and mitigation was underway, with signs of improvement. The issue was resolved and Automation for Jira returned to normal by 5:24 PM UTC.

Users relying on Jira Automation experienced degraded performance, particularly for automation tasks in Europe regions. The incident began at 4:19 PM UTC with reports of slower automation workflows, prompting an investigation by the Jira team.

By 6:00 PM UTC, a likely cause had been identified and mitigation work started, with ongoing updates as more details became available. Automation for Jira was restored to normal by 6:44 PM UTC.

StatusGator detected issues at 10:42 AM UTC, roughly 1 hour and 12 minutes before Jira’s official acknowledgment, signaling early visibility into the incident. The outage began at 11:54 AM UTC and affected Jira Software features used for searching and assigning issues, with the EU region specifically impacted. Users reported problems with user-search, user-picker, and assets, leaving teams unable to locate assignees or quickly reference teammates while Create and edit and Search components were degraded.

An outage in Jira Software began around 9:24 AM UTC, as reliability issues affected Jira and Confluence. Automation for Jira went down while Create and edit and Search entered a degraded state, leaving users unable to run automation rules and complete common tasks like assigning issues. The disruption was felt across projects and regions as teams faced blocked automations and unresponsive ticket management workflows.

Status updates tracked the progression; Automation for Jira recovered by 10:10 AM UTC and the remaining functions returned to normal shortly after. StatusGator detected issues earlier, reporting the user database outage at Jul 6, 2026 8:31 AM UTC, roughly 53 minutes before Jira acknowledged the problem. The incident appeared widespread given the diverse regional user reports (Europe, India, and elsewhere) indicating a broad impact on day-to-day Jira usage, with recovery completing by the time service returned to full operation.

Jira Software experienced degraded performance that hindered selecting users and teams in specific fields on certain sites. This impact affected creating and editing issues and viewing content, impacting two components: Create and edit, and Viewing content.

The incident began on Feb 19, 2026 4:49 PM UTC and was resolved by Feb 20, 2026 12:29 PM UTC, lasting roughly 19 hours and 40 minutes. During the event the Jira Software status page posted two updates before the service returned to normal.

Jira and Jira Service Management Ecosystem Apps experienced a significant outage beginning on 7:50 AM UTC with increased error rates impacting API usage and workflows across the Jira/JSM ecosystem. The issue progressed to affect multiple components, including Administration and Marketplace, and later extended to admin-related tools such as the Groups page where administrators could not click or manage group-based access. The service provided updates noting two fix paths (a quick fix and a longer, time-consuming fix) and outlined plans to test and implement changes as they became available. The outage spanned multiple days, with the impact broadening as the incident evolved.

The outage began at 8:29 PM UTC UTC, disrupting Jira Software and Jira Service Management availability for many users. Atlassian reported a disruption affecting Jira and JSM and noted that a likely cause had been identified with teams actively mitigating the issue. Some users in the us-east-1 region experienced access problems during the incident. The disruption impacted 11 components, including Automation for Jira, Mobile, Purchasing & Licensing, Signup, Create and edit, Search, Notifications, Authentication and User Management, Viewing content, Administration, and Marketplace. The incident lasted roughly 9 hours and 5 minutes, with three official updates issued as the status progressed. Services were reported as resolving by 5:34 AM UTC, and full restoration was confirmed by 5:40 AM UTC.