Jira Software Outage History

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.

An outage began at 2:14 PM UTC affecting Jira Software and Jira Service Management for users in the us-east-1 region. Some users could not access Jira or JSM as a result, with 12 components listed as impacted, including Automation for Jira, Mobile, Purchasing & Licensing, Signup, Create and edit, Search, Notifications, Authentication and User Management, Viewing content, Administration, and Marketplace. The outage was resolved by 9:14 PM UTC after roughly 7 hours of degraded access.

During the incident, the Jira status page published 3 updates as engineers investigated the disruption and worked to restore service. The issue was regional to us-east-1, with access returning to normal as services were restored.

Jira Software experienced a brief authentication issue affecting Jira Mobile, Confluence, and Forge users relying on OAuth. The outage began at 10:24 AM UTC and was resolved by 10:55 AM UTC, lasting about 31 minutes. Users may have encountered sign-in problems and disruptions to OAuth flows, with Forge installations and invocations potentially disrupted.

The Jira status page issued two updates during the incident, describing an active investigation and the subsequent restoration of normal authentication flow as the issue resolved.

The Jira suite, including Jira, Jira Product Discovery (JPD), and Jira Service Management (JSM), experienced degraded performance in the eu-west-1 region starting at Jan 28, 2026 6:14 PM UTC. Users faced delays in issue data across various views, including the issue view. The incident affected two components: Search and Viewing content, and was localized to eu-west-1. The Jira status page issued two updates during the incident.

Jira Software's Assets product experienced intermittent accessibility issues, resulting in gateway timeouts and internal server errors. Users attempting to run queries, load asset-related pages, or interact with assets-dependent features (such as specific custom fields and automation processes) could see slow performance or failures. The issue also impacted the Automation for Jira component as part of the Assets-related disruptions.

The incident began at Jan 20, 2026 7:14 PM UTC when the status page reported an investigation and transitioned to a degraded state, and was resolved by Jan 20, 2026 9:14 PM UTC when the status returned to normal. The outage lasted approximately 2 hours. The provider issued 2 status updates during the incident, affecting 2 components: Assets and Automation for Jira.

Jira Software experienced a partial outage affecting some customers, disrupting creating and editing issues, viewing issues, and viewing boards. Users could have encountered failures when creating or updating issues and loading boards during the incident. The outage began on 6:24 PM UTC and was resolved by 7:34 PM UTC, lasting about 1 hour and 10 minutes. Jira Software posted 2 status updates during the incident, and user reports indicated disruption.

Automation for Jira triggers were not executing for a subset of Jira Software users, causing automation rules to fail to fire across Jira and Jira Service Management. The incident began at 5:19 AM UTC and affected automation tasks until 2:09 PM UTC. This outage was limited to the automation components, with users potentially experiencing missing or delayed automation actions.

During the incident, the Automation for Jira component moved from a healthy state to a degraded warning and back to normal as engineers investigated and resolved the issue. Jira noted the disruption and posted two official status updates: the initial warning at Jan 6, 2026 5:19 AM UTC and recovery at Jan 6, 2026 2:09 PM UTC. The outage lasted approximately 8 hours and 50 minutes.

Jira Software experienced an outage affecting outbound email, mobile push notifications, and support ticket delivery across all Jira Cloud products. The incident began at Dec 27, 2025 4:44 AM UTC and was resolved by Dec 27, 2025 5:25 AM UTC, lasting about 41 minutes. The issue was associated with the Notifications component, indicating a broad impact on communication-related services.

Two official status updates were published during the incident as teams worked to mitigate the problem. By the second update, recovery was observed and Jira Cloud services were returning to normal for affected components.