Jira Service Management Outage History

Users experienced widespread access issues across multiple Atlassian products including Jira Service Management, Opsgenie, authentication systems, and other core services for 1.8 hours. The incident affected web interfaces, service portals, email requests, user authentication, purchasing, and automation features across the Atlassian ecosystem. The team identified the root cause, implemented a mitigation, and fully restored all services with continued monitoring to ensure complete recovery.

Some Jira Service Management users experienced excessive notifications for 8.5 hours as Atlassian's engineering team replayed delayed events from a previous incident. The notification flood was a side effect of the recovery process, which took longer than initially expected. The engineering team identified and resolved the issue, restoring normal notification delivery with no data loss.

Jira Service Management experienced a major incident where automation events in Jira, Jira Service Management, and JSM Assist were delayed by multiple hours for some users over an 8.4-hour period. The incident response team identified the root cause and restored normal processing for new automation events after approximately 6 hours, then worked through processing the backlog of delayed historical events. All services were fully restored and all delayed automation events were successfully processed by the end of the incident.

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 Jira Service Management, Opsgenie, authentication, purchasing, and automation services across multiple components. The underlying infrastructure issue was mitigated and services were restored, with teams clearing backlogs of queued events including notifications and automation triggers.

Jira Service Management experienced a major incident where lookup objects in Automation for Jira Service Management stopped functioning as expected, affecting automated workflows and processes. The issue impacted the Automation for Jira component and prevented users from properly utilizing lookup functionality within their service management automations. The engineering team implemented a fix after 1.7 hours of investigation and monitoring, restoring normal service operations for all affected customers.

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.