Jira Service Management Outage History

Jira Service Management experienced a major incident that degraded the Work Item view experience, affecting core Jira Software functions including viewBoard, viewIssue, and createIssue capabilities. The disruption also impacted the Service Portal, Opsgenie Incident Flow, and accessibility of support tickets. The service was restored to normal operation after 1.9 hours, with teams continuing to investigate the root cause.

Jira Service Management experienced a 4-hour service disruption where automation rules that invoke Rovo agents were not completing as expected, affecting both Jira and Confluence automation workflows. The incident impacted multiple components including Automation for Jira, Service Portal, Opsgenie flows, and other core services. The issue was identified and resolved, with services returning to normal operation and continued monitoring to ensure stability.

Some users experienced login failures across Atlassian products due to authentication service issues that lasted approximately 36 minutes (05:49-06:25 UTC on April 13, 2026). The underlying authentication problem was identified and resolved, with services returning to normal operation and remaining stable thereafter.

A major search failure affected multiple Atlassian products including Jira, Confluence, Jira Service Management, Opsgenie, Customer Service Management, Asset Reports, and Focus dashboards, preventing users from performing searches and causing downstream impacts to authentication, user management, and other services. The incident lasted 5.4 hours, with core search functionality restored partway through but some customers experiencing delays searching recently changed data during the recovery period. The issue was fully resolved after the team identified the root cause and completed reindexing of affected data.

Jira Service Management experienced a major incident where automations failed to trigger automatically for actions like work item creation, field updates, and comment additions, though manual triggers continued to work normally. The issue affected multiple components including the web interface, service portal, Opsgenie flows, email requests, and authentication systems for some Jira Cloud customers over a 16.6-hour period. The root cause was identified and fixed, with automation processing restored, followed by a replay of historical events to rerun failed automation rules from the affected timeframe.

Customers in the APAC region experienced delayed automation events across Jira, Jira Service Management, Jira Work Management, Jira Product Discovery, and Confluence for 57 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. The service was fully restored and returned to normal operation for all affected customers.

Atlassian Assist in Jira Service Management experienced a complete service disruption lasting 5.6 hours on February 26, 2026, making the AI-powered assistance feature unavailable to all affected users. The engineering team identified the root cause and implemented a fix, restoring normal service operations. The service is now fully operational with continued monitoring to ensure stability.