Jira Core Outage History

Multiple Atlassian products experienced elevated error rates and degraded performance for 18.2 hours due to an infrastructure outage from their public cloud provider. The incident affected core functionality including content viewing, authentication, search, notifications, administration, and automation across all Atlassian services. The underlying infrastructure issue was mitigated and services were restored, with teams subsequently clearing the backlog of queued events that accumulated during the outage.

Jira Core users experienced a major issue preventing them from logging time while on business boards, affecting the create and edit functionality. The engineering team identified the root cause and deployed a fix to resolve the problem. The incident lasted 3.4 hours and service has been restored to normal operation for all affected customers.

Jira Core experienced a major service disruption affecting the Work Item view experience, including viewing boards, viewing issues, and creating issues, as well as impacting access to support tickets. The incident affected core functionality for viewing content and creating/editing items for approximately 1.9 hours. Service was restored to normal levels, though the root cause investigation was ongoing at the time of resolution.

Jira Core experienced a service disruption affecting Rovo functionality for customers using automation rules that invoke Rovo agents. The issue caused automation rules to fail to complete as expected, impacting the Automation for Jira component. The incident lasted 6 minutes and was actively investigated by the team.

Some users were unable to log in to Atlassian products with their accounts between 05:49 and 06:25 UTC on April 13, 2026, affecting authentication and user management services as well as signup functionality. The underlying issue was addressed and authentication services were restored to normal operation. The team continued monitoring to ensure system stability with no further impact observed.

Customers in the APAC region experienced delayed automation events across Jira, Jira Service Management, Jira Work Management, Jira Product Discovery, and Confluence for 53 minutes on March 9th UTC. The engineering team identified the root cause and deployed a hotfix to restore automation performance and process the backlog of delayed events. All services returned to normal operation with continued monitoring to ensure stability.