Delays observed at JSM, Opsgenie and Compass alert search functionality in US Region
Incident
Report for Compass
Resolved
Between September 10, 2025, 3:19 PM UTC and September 11, 2025, 2:44 PM UTC, there was degraded performance in web experiences and the REST APIs for some Jira Service Management, Opsgenie, and Compass Cloud customers in the US region. We have deployed a fix to mitigate the issue and have verified that the services have recovered. The issue has been resolved and the service is operating normally.
Monitoring
We have deployed the fix and all operations are back to normal. We will continue to monitor the operations.
We will continue providing specific updates when available.
We will continue providing specific updates when available.
Update
We have progressed further in preparing our system with a probable fix. Initial testing has been successful. We are in the process of completing further testing and finalising the fix. We expect the fix to be completed in next few hours.
Alerts continue to successfully notify users, in some cases the responder name may be missing. Our goal continues to restore full functionality to users from Jira Service Management, Opsgenie and Compass.
We will continue providing specific updates when available and will ensure we have further update within the hour.
Alerts continue to successfully notify users, in some cases the responder name may be missing. Our goal continues to restore full functionality to users from Jira Service Management, Opsgenie and Compass.
We will continue providing specific updates when available and will ensure we have further update within the hour.
Update
We are progressing well with the testing of identified potential mitigation steps for this issue; and we are seeing positive early results. We will update with an ETA and further information in the next update.
Alerts continue to successfully notify users, in some cases the responder name may be missing. Our goal continues to restore full functionality to users from Jira Service Management, Opsgenie and Compass.
We will continue providing specific updates when available and will ensure we have further update within the hour.
Alerts continue to successfully notify users, in some cases the responder name may be missing. Our goal continues to restore full functionality to users from Jira Service Management, Opsgenie and Compass.
We will continue providing specific updates when available and will ensure we have further update within the hour.
Update
Atlassian teams continue to test the identified potential resolution steps for this issue. Our goal is to restore full functionality to users from Jira Service Management, Opsgenie and Compass.
Currently, the alerts continue to successfully notify users, except that the responder name may be missing.
We will continue providing specific updates when available and will ensure we have further update within the hour.
Currently, the alerts continue to successfully notify users, except that the responder name may be missing.
We will continue providing specific updates when available and will ensure we have further update within the hour.
Update
Our teams have are identified some potential resolution steps for this issue and continue to test the same on priority to be able to restore full functionality to users from Jira Service Management, Opsgenie and Compass.
Currently, the alerts continue to successfully notify users, except that the responder name may be missing.
We will continue providing specific updates when available and will ensure we have further update within the hour.
Currently, the alerts continue to successfully notify users, except that the responder name may be missing.
We will continue providing specific updates when available and will ensure we have further update within the hour.
Update
Atlassian teams continue to remain engaged with priority to restore full functionality to new alerts to users from Jira Service Management, Opsgenie and Compass.
Escalation teams also continue to remain engaged on this incident to ensure our focus is not diluted from a resolution as soon as possible.
Currently, the alerts continue to successfully notify users, except that the responder name may be missing.
We will continue providing specific updates when available and will ensure we have further update within the hour.
Escalation teams also continue to remain engaged on this incident to ensure our focus is not diluted from a resolution as soon as possible.
Currently, the alerts continue to successfully notify users, except that the responder name may be missing.
We will continue providing specific updates when available and will ensure we have further update within the hour.
Identified
Atlassian teams remain engaged with priority to restore full functionality to new alerts to users from Jira Service Management, Opsgenie and Compass.
Escalation teams are also engaged on this incident to ensure we can get to a resolution as soon as possible.
At this point, the alerts continue to successfully notify users, except that the responder name may be missing.
We will continue providing specific updates when available and will ensure we have further update within the hour.
Escalation teams are also engaged on this incident to ensure we can get to a resolution as soon as possible.
At this point, the alerts continue to successfully notify users, except that the responder name may be missing.
We will continue providing specific updates when available and will ensure we have further update within the hour.
This incident affected: API (GraphQL, REST), Integrations (Bitbucket, Gitlab, CircleCI, JSM, JSW, NewRelic, Opsgenie, PagerDuty, Slack, SwaggerUI, Statuspage, Github), Notifications (Webhooks, Email), Catalog (Component Templates, Components, Search, Activity Timeline), Health (Scorecards, Metrics, CheckOps), 3rd Party Services (GitHub API Requests, GitHub Webhooks, CircleCI CircleCI Webhooks), Operations (On-call flows, Alert flows), and Authentication and User Management, Purchasing & Licensing, Signup.