Jira Software outage history

Jira Software users experienced missing fields across Work Items, which disrupted searching and automations that rely on those fields. The incident affected Automation for Jira, Search, and Viewing content, causing a partial outage for some users and a degraded experience as workflows could not access or process key fields. Impact began at 12:14 AM UTC and lasted for about twenty-five minutes.

Users of Jira Software on Jira Cloud experienced degraded project navigation as the project sidebar loaded slowly or failed to render. Accessing project views could yield timeouts or missing menus, hindering the ability to navigate between projects.

The issue began at 2:31 PM UTC and was resolved by 3:04 PM UTC. Jira's status page indicated engineers were actively analyzing telemetry to identify a mitigation and would provide the next update in about an hour, with the degradation affecting the Viewing content component until a fix was applied.

Users across Jira Software and connected Atlassian products experienced degraded job processing and scheduling, causing delays in asynchronous tasks, email-to-ticket processing, and scheduled jobs across Jira, Confluence, and Bitbucket Cloud. The outage began at 3:00 AM UTC and impacted core back-end workflows, with affected automation and notification delivery impacting daily operations.

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.