Jira Software outage history

Jira Software and Jira Service Management experienced degraded performance, with errors and delays when loading issue views and while viewing boards. Users reported trouble rendering tickets and navigating boards across several regions. StatusGator detected the issue at Sep 11, 2026 7:33 AM UTC, about 13 minutes before Jira acknowledged the problem at 7:47 AM UTC, and the service indicated ongoing investigation with a degraded content component. The problem began to recover and the viewing-content component returned to normal by 8:10 AM UTC, after roughly 37 minutes of degraded performance.

A disruption affected Jira Software in the US East region, taking down access to core features across multiple components, including Administration, Automation for Jira, Mobile, Purchasing & Licensing, Signup, Create and edit, Search, Notifications, Authentication and User Management, Viewing content, and Marketplace.

The outage began at Sep 3, 2026 4:05 PM UTC and lasted about 35 minutes until Sep 3, 2026 4:40 PM UTC. Atlassian's status page indicated active investigation and that updates would be provided as more information became available, with services restored across the affected components by the end of the incident.

Jira Software experienced degraded performance impacting forms functionality, notably the Create and edit component. Beginning at 5:09 PM UTC, users attempting to create or edit issues via forms may have faced slower responses or unexpected behavior. By 6:34 PM UTC, Atlassian teams had identified a likely cause and began mitigations, with further updates through 8:34 PM UTC as work continued.

By 9:24 PM UTC, Jira Software returned to normal operation and the Create and edit component was back online.

Users attempting to transition issues in Jira Software began encountering errors at 9:14 AM UTC. The incident affected the Create and edit component, causing a partial outage where issue transitions could fail and workflows stall. Jira Software's status page stated that the team was actively investigating and would provide the next update within 60 minutes.

The problem was resolved by 10:14 AM UTC, as the Create and edit component returned to normal and issue transitions could be completed again. The service's communications framed this as a brief degradation of the transition experience for Jira users.

Users of Jira Software were temporarily unable to create or update Jira work items via email due to an outage affecting Jira Incoming Emails. The issue began with the Create and Edit component degraded to a warning state, and Microsoft mail fetches returning errors for emails from Microsoft accounts, causing 500 internal server errors during fetch attempts. The incident started at 6:29 PM UTC and progressed until the service was restored by 5:19 AM UTC as the affected component returned to normal. Updates reference ongoing investigations from Microsoft and indicate that email-based workflows were impacted during the window of the outage.

Users across APAC regions experienced outages accessing Jira Cloud, Confluence, and Jira Service Management as core components failed to load or respond. The user experience included page timeouts, unavailable pages, and inability to access Jira boards and Confluence content. The disruption affected a broad set of features including Administration, Automation for Jira, Mobile, Purchasing & Licensing, Signup, Create and edit, Search, Notifications, Authentication and User Management, Viewing content, and Marketplace.

Status updates began with the initial outage at 4:23 AM UTC and an official acknowledgment shortly after. StatusGator detected the issue earlier at 3:58 AM UTC, ending the Early Warning Signal at 4:40 AM UTC. A fix was rolled out to impacted regions around 4:34 AM UTC, with recovery progress noted by 4:54 AM UTC and full restoration across components by 5:19 AM UTC.

Users experienced delayed notifications across Jira, Jira Service Management (JSM), and Confluence, with email, mobile, and Slack alerts arriving late or not at all. The issue began at 8:49 AM UTC and degraded notification delivery for several hours, affecting workflows that rely on timely updates. The disruption appeared regional, with some regions more affected than others.

Starting at 7:24 PM UTC, Jira Software users experienced degraded notifications with increased latency across email, mobile, and Slack for Jira, Jira Service Management (JSM), and Confluence. The issue centered on the Notifications component and prompted ongoing investigation.

By 8:30 PM UTC, three regions were identified as affected, with teams continuing to investigate the latency across notification channels. At 9:34 PM UTC, the likely cause was identified and a mitigation was under way; affected users could still experience delays. The incident was resolved at 11:20 PM UTC when the Notifications component returned to normal, marking nearly four hours of degraded performance.

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