Guard Atlassian Outage History

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 services including SAML-based SSO, user provisioning, account management, audit logs, API tokens, and data security policies. The underlying infrastructure issue was mitigated and services were restored, with teams subsequently clearing the backlog of queued events for notifications, automation triggers, and data syncs.

Some users were unable to log in to Atlassian products with their Atlassian accounts on April 13, 2026, between 05:49 and 06:25 UTC. The incident affected signup, SAML-based SSO, and user provisioning components across Atlassian services. The underlying authentication issue was resolved and services returned to normal operation with continued monitoring to ensure stability.

Guard Atlassian experienced a major search functionality failure lasting 5.8 hours that prevented users from searching in Confluence and Jira, with cascading impacts to Customer Service Management, Asset Reports, Jira Service Management, Focus dashboards, Rovo Chat, User Management, Administration, and multiple Guard components including Account Management, SAML-based SSO, and Audit Logs. The team identified the root cause and restored core search functionality, though some customers experienced delays searching recently changed data during the reindexing process. The incident was fully resolved with all services operating normally.