Jira Software Outage History

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.

Automation events experienced significant delays across Jira Software, Jira Service Management, Jira Work Management, Jira Product Discovery, and Confluence for customers in the APAC region on March 9th UTC. The performance degradation affected multiple components including content viewing, editing, authentication, search, notifications, and administration functions. The issue was resolved after 56 minutes when the team identified the root cause and deployed a hotfix to restore automation performance and process the backlog of delayed events.