Jira Software Outage History

A major incident affected multiple Atlassian products including Jira and Confluence Cloud, impacting users' ability to access and use core functionality such as viewing content, authentication, search, notifications, and administration features. The outage lasted 1.9 hours, with Atlassian identifying the root cause and implementing a mitigation that restored service across all affected products. All services were fully recovered and the incident was resolved after a monitoring period to ensure stability.

Jira Software experienced an 8.4-hour incident where automation events in Jira, Jira Service Management, and JSM Assist were delayed by multiple hours for some users. The incident response team identified the root cause and implemented a fix, first restoring normal processing for new automation events, then working through the backlog of delayed historical events. All services were fully restored and all delayed automation events were successfully processed.

Multiple Atlassian services experienced elevated error rates and degraded performance for 18.3 hours due to a public cloud provider infrastructure outage. The incident affected core functionality including content viewing, editing, authentication, search, notifications, administration, marketplace, mobile access, purchasing, and automation features across Atlassian products. The underlying infrastructure issue was mitigated and services were restored, with teams subsequently clearing backlogs of queued events for notifications, automation triggers, and data syncs.

Jira Software experienced a major incident where users were unable to log 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 issue. The incident lasted 3.4 hours and service was restored to normal operation for all affected customers.

Jira Software experienced a major incident affecting core functionality including viewing boards, viewing issues, and creating issues in some regions for 12 minutes. Users encountered connection errors when trying to access work items, receiving messages that the system couldn't connect to existing items. The service team investigated and restored normal functionality.

Jira Software experienced intermittent delays in webhook delivery for 6 hours, affecting multiple components including content viewing, editing, authentication, search, notifications, administration, marketplace, mobile, automation, purchasing, and signup functionality. The issue was caused by a resource constraint in the system, which was resolved by deploying a fix to address the underlying capacity problem. Webhook delivery returned to normal operation after the fix was implemented and monitored for stability.

Jira Software experienced a 4-hour service disruption where automation rules that invoke Rovo agents were not completing as expected, affecting both Jira and Confluence automation functionality. The incident impacted multiple components including Automation for Jira, content viewing, editing, authentication, search, notifications, administration, marketplace, mobile access, and licensing systems. The issue was identified and resolved, with services returning to normal operation and continued monitoring to ensure stability.

Some users were unable to log in to Atlassian products with their Atlassian accounts on April 13, 2026, between 05:49 a.m. and 06:25 a.m. UTC. The incident affected the signup, authentication and user management components across Atlassian products. The underlying issue was addressed and authentication services returned to stable operation with no further impact observed.

Jira Software and Confluence experienced a major 6.1-hour outage affecting search functionality, which caused cascading failures across multiple components including authentication, user management, administration, mobile access, content viewing/editing, notifications, and several downstream services like Customer Service Management and Asset Reports. The team identified the root cause and gradually restored core search functionality, though some customers experienced delays searching recently changed data during the recovery period while reindexing completed. The incident was fully resolved with all services returning to normal operation.

Jira Software experienced a major outage where automations failed to trigger on work item creation, field updates, and comment additions for some customers, though manual triggers continued to work normally. The incident affected multiple components including viewing content, authentication, search, notifications, and administration across Jira and Jira Service Management. After identifying and fixing the root cause, Atlassian restored automation processing and replayed historical events to rerun failed automation rules, with the full resolution taking 16.7 hours.