Opsgenie Status

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.

Identified: 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.

Identified: 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.

Identified: 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.

Identified: 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.

Identified: 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.

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.

Identified: All concerned teams are engaged and are working to restore full functionality to new alerts to users from Jira Service Management and Opsgenie.

Escalation teams are also engaged on this incident to try and ensure we can get to a resolution as soon as possible.

Currently, the alerts continue to successfully notify users, but without the intended content within the alerts.

We will continue providing specific updates when available and will ensure we have further update within the hour.

Identified: Our teams priority remains to restore full functionality to new alerts to users from Jira Service Management and Opsgenie.

Escalation teams are fully engaged on this incident to try and ensure we can get to a resolution as soon as possible.

At this time these alerts are still successfully notifying users, but without the intended content within the alerts.

We will continue providing specific updates when available and will ensure we have further update within the hour.

Identified: Our infrastructure teams are working diligently to try and ensure all services are restored to Jira Service Management and Opsgenie as soon as possible.

New alerts are continuing to notify users, however we are still prioritising infrastructure to restore the content inside these alerts for Web and Mobile UIs.

We will continue providing updates when available and will ensure we have further update within the hour.

Identified: Our team is continuing to investigate with the highest level of urgency in order to restore Jira Service Management and Opsgenie services.

At this time we are prioritising infrastructure to try and restore new and active alerts to be populated with their alert content as soon as possible, while continuing to deliver existing messages as they are ready.

We will continue to provide updates as we progress, and will ensure we have an update posted within the hour.

Identified: We have received reports that some customers are experiencing further issues relating to loading pages within Opsgenie and Jira Service Management which may be related to the infrastructure efforts underway to restore services to these products.

Please be aware we also have teams actively investigating these issues to ensure as fast a resolution as possible.

We want to reiterate that your alerts are still sending notifications correctly, and there is no data loss occurring. However, the underlying issue is affecting the propagation of alert details to notifications, and to the Web and Mobile UI.

Viewing schedules may also be impacted at this time while we continue to process the tasks required for recovery.

We will provide further updates as soon as possible.

Identified: New alerts should still continue to notify users as they are generated, however the alert content will still be missing.

Our teams are still actively engaging with infrastructure teams to try and expedite historical processing of messages to fully restore services.

We will provide further updates within the hour.

Identified: While new alerts should now correctly notify users, the content of those alerts for impacted customers will remain empty until missed alerts are fully processed. Our team is continuing to investigate with urgency potential infrastructure options to expedite this process. We will provide further updates within the hour.

Identified: We are continuing to see recovery of Jira Service Management operations and Opsgenie services. There are a large number of missed alerts to be processed due to the prior service issue and our team is actively investigating methods to help expedite this processing. Alerts should trigger in the meantime but the content of these alerts may not be visible at this time. Our teams are continuing to investigate with urgency. We will provide further updates within the hour.

Identified: Our team has been able to identify the root cause of these performance issues and have put a mitigation into place. We are now continuing to see recovery of Jira Service Management operations and Opsgenie services. Existing alerts are continuing to be processed at this time. We will provide further update as soon as possible.

Identified: Our team is still actively working to resolve the issue and making progress toward a resolution. Thank you for your patience.

Identified: We are continuing to work on a fix for this issue.

Identified: We continue to work on resolving the incident for Jira Service Management and Opsgenie. We have identified the root cause and taken actions to mitigate the issue and minimize the impact on search functionality.

Investigating: We identified degraded performance in web experiences and Alert Rest API for some Jira Service Management and Opsgenie Cloud customers in the US Region. The team has taken actions to mitigate the issue and minimize the impact on search functionality.

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.

Identified: 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.

Identified: 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.

Identified: 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.

Identified: 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.

Identified: 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.

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.

Identified: All concerned teams are engaged and are working to restore full functionality to new alerts to users from Jira Service Management and Opsgenie.

Escalation teams are also engaged on this incident to try and ensure we can get to a resolution as soon as possible.

Currently, the alerts continue to successfully notify users, but without the intended content within the alerts.

We will continue providing specific updates when available and will ensure we have further update within the hour.

Identified: Our teams priority remains to restore full functionality to new alerts to users from Jira Service Management and Opsgenie.

Escalation teams are fully engaged on this incident to try and ensure we can get to a resolution as soon as possible.

At this time these alerts are still successfully notifying users, but without the intended content within the alerts.

We will continue providing specific updates when available and will ensure we have further update within the hour.

Identified: Our infrastructure teams are working diligently to try and ensure all services are restored to Jira Service Management and Opsgenie as soon as possible.

New alerts are continuing to notify users, however we are still prioritising infrastructure to restore the content inside these alerts for Web and Mobile UIs.

We will continue providing updates when available and will ensure we have further update within the hour.

Identified: Our team is continuing to investigate with the highest level of urgency in order to restore Jira Service Management and Opsgenie services.

At this time we are prioritising infrastructure to try and restore new and active alerts to be populated with their alert content as soon as possible, while continuing to deliver existing messages as they are ready.

We will continue to provide updates as we progress, and will ensure we have an update posted within the hour.

Identified: We have received reports that some customers are experiencing further issues relating to loading pages within Opsgenie and Jira Service Management which may be related to the infrastructure efforts underway to restore services to these products.

Please be aware we also have teams actively investigating these issues to ensure as fast a resolution as possible.

We want to reiterate that your alerts are still sending notifications correctly, and there is no data loss occurring. However, the underlying issue is affecting the propagation of alert details to notifications, and to the Web and Mobile UI.

Viewing schedules may also be impacted at this time while we continue to process the tasks required for recovery.

We will provide further updates as soon as possible.

Identified: New alerts should still continue to notify users as they are generated, however the alert content will still be missing.

Our teams are still actively engaging with infrastructure teams to try and expedite historical processing of messages to fully restore services.

We will provide further updates within the hour.

Identified: While new alerts should now correctly notify users, the content of those alerts for impacted customers will remain empty until missed alerts are fully processed. Our team is continuing to investigate with urgency potential infrastructure options to expedite this process. We will provide further updates within the hour.

Identified: We are continuing to see recovery of Jira Service Management operations and Opsgenie services. There are a large number of missed alerts to be processed due to the prior service issue and our team is actively investigating methods to help expedite this processing. Alerts should trigger in the meantime but the content of these alerts may not be visible at this time. Our teams are continuing to investigate with urgency. We will provide further updates within the hour.

Identified: Our team has been able to identify the root cause of these performance issues and have put a mitigation into place. We are now continuing to see recovery of Jira Service Management operations and Opsgenie services. Existing alerts are continuing to be processed at this time. We will provide further update as soon as possible.

Identified: Our team is still actively working to resolve the issue and making progress toward a resolution. Thank you for your patience.

Identified: We are continuing to work on a fix for this issue.

Identified: We continue to work on resolving the incident for Jira Service Management and Opsgenie. We have identified the root cause and taken actions to mitigate the issue and minimize the impact on search functionality.

Investigating: We identified degraded performance in web experiences and Alert Rest API for some Jira Service Management and Opsgenie Cloud customers in the US Region. The team has taken actions to mitigate the issue and minimize the impact on search functionality.

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.

Identified: 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.

Identified: 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.

Identified: 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.

Identified: 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.

Identified: 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.

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.

Identified: All concerned teams are engaged and are working to restore full functionality to new alerts to users from Jira Service Management and Opsgenie.

Escalation teams are also engaged on this incident to try and ensure we can get to a resolution as soon as possible.

Currently, the alerts continue to successfully notify users, but without the intended content within the alerts.

We will continue providing specific updates when available and will ensure we have further update within the hour.

Identified: Our teams priority remains to restore full functionality to new alerts to users from Jira Service Management and Opsgenie.

Escalation teams are fully engaged on this incident to try and ensure we can get to a resolution as soon as possible.

At this time these alerts are still successfully notifying users, but without the intended content within the alerts.

We will continue providing specific updates when available and will ensure we have further update within the hour.

Identified: Our infrastructure teams are working diligently to try and ensure all services are restored to Jira Service Management and Opsgenie as soon as possible.

New alerts are continuing to notify users, however we are still prioritising infrastructure to restore the content inside these alerts for Web and Mobile UIs.

We will continue providing updates when available and will ensure we have further update within the hour.

Identified: Our team is continuing to investigate with the highest level of urgency in order to restore Jira Service Management and Opsgenie services.

At this time we are prioritising infrastructure to try and restore new and active alerts to be populated with their alert content as soon as possible, while continuing to deliver existing messages as they are ready.

We will continue to provide updates as we progress, and will ensure we have an update posted within the hour.

Identified: We have received reports that some customers are experiencing further issues relating to loading pages within Opsgenie and Jira Service Management which may be related to the infrastructure efforts underway to restore services to these products.

Please be aware we also have teams actively investigating these issues to ensure as fast a resolution as possible.

We want to reiterate that your alerts are still sending notifications correctly, and there is no data loss occurring. However, the underlying issue is affecting the propagation of alert details to notifications, and to the Web and Mobile UI.

Viewing schedules may also be impacted at this time while we continue to process the tasks required for recovery.

We will provide further updates as soon as possible.

Identified: New alerts should still continue to notify users as they are generated, however the alert content will still be missing.

Our teams are still actively engaging with infrastructure teams to try and expedite historical processing of messages to fully restore services.

We will provide further updates within the hour.

Identified: While new alerts should now correctly notify users, the content of those alerts for impacted customers will remain empty until missed alerts are fully processed. Our team is continuing to investigate with urgency potential infrastructure options to expedite this process. We will provide further updates within the hour.

Identified: We are continuing to see recovery of Jira Service Management operations and Opsgenie services. There are a large number of missed alerts to be processed due to the prior service issue and our team is actively investigating methods to help expedite this processing. Alerts should trigger in the meantime but the content of these alerts may not be visible at this time. Our teams are continuing to investigate with urgency. We will provide further updates within the hour.

Identified: Our team has been able to identify the root cause of these performance issues and have put a mitigation into place. We are now continuing to see recovery of Jira Service Management operations and Opsgenie services. Existing alerts are continuing to be processed at this time. We will provide further update as soon as possible.

Identified: Our team is still actively working to resolve the issue and making progress toward a resolution. Thank you for your patience.

Identified: We are continuing to work on a fix for this issue.

Identified: We continue to work on resolving the incident for Jira Service Management and Opsgenie. We have identified the root cause and taken actions to mitigate the issue and minimize the impact on search functionality.

Investigating: We identified degraded performance in web experiences and Alert Rest API for some Jira Service Management and Opsgenie Cloud customers in the US Region. The team has taken actions to mitigate the issue and minimize the impact on search functionality.

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.

Identified: 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.

Identified: 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.

Identified: 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.

Identified: 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.

Identified: 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.

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.

Identified: All concerned teams are engaged and are working to restore full functionality to new alerts to users from Jira Service Management and Opsgenie.

Escalation teams are also engaged on this incident to try and ensure we can get to a resolution as soon as possible.

Currently, the alerts continue to successfully notify users, but without the intended content within the alerts.

We will continue providing specific updates when available and will ensure we have further update within the hour.

Identified: Our teams priority remains to restore full functionality to new alerts to users from Jira Service Management and Opsgenie.

Escalation teams are fully engaged on this incident to try and ensure we can get to a resolution as soon as possible.

At this time these alerts are still successfully notifying users, but without the intended content within the alerts.

We will continue providing specific updates when available and will ensure we have further update within the hour.

Identified: Our infrastructure teams are working diligently to try and ensure all services are restored to Jira Service Management and Opsgenie as soon as possible.

New alerts are continuing to notify users, however we are still prioritising infrastructure to restore the content inside these alerts for Web and Mobile UIs.

We will continue providing updates when available and will ensure we have further update within the hour.

Identified: Our team is continuing to investigate with the highest level of urgency in order to restore Jira Service Management and Opsgenie services.

At this time we are prioritising infrastructure to try and restore new and active alerts to be populated with their alert content as soon as possible, while continuing to deliver existing messages as they are ready.

We will continue to provide updates as we progress, and will ensure we have an update posted within the hour.

Identified: We have received reports that some customers are experiencing further issues relating to loading pages within Opsgenie and Jira Service Management which may be related to the infrastructure efforts underway to restore services to these products.

Please be aware we also have teams actively investigating these issues to ensure as fast a resolution as possible.

We want to reiterate that your alerts are still sending notifications correctly, and there is no data loss occurring. However, the underlying issue is affecting the propagation of alert details to notifications, and to the Web and Mobile UI.

Viewing schedules may also be impacted at this time while we continue to process the tasks required for recovery.

We will provide further updates as soon as possible.

Identified: New alerts should still continue to notify users as they are generated, however the alert content will still be missing.

Our teams are still actively engaging with infrastructure teams to try and expedite historical processing of messages to fully restore services.

We will provide further updates within the hour.

Identified: While new alerts should now correctly notify users, the content of those alerts for impacted customers will remain empty until missed alerts are fully processed. Our team is continuing to investigate with urgency potential infrastructure options to expedite this process. We will provide further updates within the hour.

Identified: We are continuing to see recovery of Jira Service Management operations and Opsgenie services. There are a large number of missed alerts to be processed due to the prior service issue and our team is actively investigating methods to help expedite this processing. Alerts should trigger in the meantime but the content of these alerts may not be visible at this time. Our teams are continuing to investigate with urgency. We will provide further updates within the hour.

Identified: Our team has been able to identify the root cause of these performance issues and have put a mitigation into place. We are now continuing to see recovery of Jira Service Management operations and Opsgenie services. Existing alerts are continuing to be processed at this time. We will provide further update as soon as possible.

Identified: Our team is still actively working to resolve the issue and making progress toward a resolution. Thank you for your patience.

Identified: We are continuing to work on a fix for this issue.

Identified: We continue to work on resolving the incident for Jira Service Management and Opsgenie. We have identified the root cause and taken actions to mitigate the issue and minimize the impact on search functionality.

Investigating: We identified degraded performance in web experiences and Alert Rest API for some Jira Service Management and Opsgenie Cloud customers in the US Region. The team has taken actions to mitigate the issue and minimize the impact on search functionality.

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.

Identified: 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.

Identified: 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.

Identified: 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.

Identified: 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.

Identified: 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.

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.

Identified: All concerned teams are engaged and are working to restore full functionality to new alerts to users from Jira Service Management and Opsgenie.

Escalation teams are also engaged on this incident to try and ensure we can get to a resolution as soon as possible.

Currently, the alerts continue to successfully notify users, but without the intended content within the alerts.

We will continue providing specific updates when available and will ensure we have further update within the hour.

Identified: Our teams priority remains to restore full functionality to new alerts to users from Jira Service Management and Opsgenie.

Escalation teams are fully engaged on this incident to try and ensure we can get to a resolution as soon as possible.

At this time these alerts are still successfully notifying users, but without the intended content within the alerts.

We will continue providing specific updates when available and will ensure we have further update within the hour.

Identified: Our infrastructure teams are working diligently to try and ensure all services are restored to Jira Service Management and Opsgenie as soon as possible.

New alerts are continuing to notify users, however we are still prioritising infrastructure to restore the content inside these alerts for Web and Mobile UIs.

We will continue providing updates when available and will ensure we have further update within the hour.

Identified: Our team is continuing to investigate with the highest level of urgency in order to restore Jira Service Management and Opsgenie services.

At this time we are prioritising infrastructure to try and restore new and active alerts to be populated with their alert content as soon as possible, while continuing to deliver existing messages as they are ready.

We will continue to provide updates as we progress, and will ensure we have an update posted within the hour.

Identified: We have received reports that some customers are experiencing further issues relating to loading pages within Opsgenie and Jira Service Management which may be related to the infrastructure efforts underway to restore services to these products.

Please be aware we also have teams actively investigating these issues to ensure as fast a resolution as possible.

We want to reiterate that your alerts are still sending notifications correctly, and there is no data loss occurring. However, the underlying issue is affecting the propagation of alert details to notifications, and to the Web and Mobile UI.

Viewing schedules may also be impacted at this time while we continue to process the tasks required for recovery.

We will provide further updates as soon as possible.

Identified: New alerts should still continue to notify users as they are generated, however the alert content will still be missing.

Our teams are still actively engaging with infrastructure teams to try and expedite historical processing of messages to fully restore services.

We will provide further updates within the hour.

Identified: While new alerts should now correctly notify users, the content of those alerts for impacted customers will remain empty until missed alerts are fully processed. Our team is continuing to investigate with urgency potential infrastructure options to expedite this process. We will provide further updates within the hour.

Identified: We are continuing to see recovery of Jira Service Management operations and Opsgenie services. There are a large number of missed alerts to be processed due to the prior service issue and our team is actively investigating methods to help expedite this processing. Alerts should trigger in the meantime but the content of these alerts may not be visible at this time. Our teams are continuing to investigate with urgency. We will provide further updates within the hour.

Identified: Our team has been able to identify the root cause of these performance issues and have put a mitigation into place. We are now continuing to see recovery of Jira Service Management operations and Opsgenie services. Existing alerts are continuing to be processed at this time. We will provide further update as soon as possible.

Identified: Our team is still actively working to resolve the issue and making progress toward a resolution. Thank you for your patience.

Identified: We are continuing to work on a fix for this issue.

Identified: We continue to work on resolving the incident for Jira Service Management and Opsgenie. We have identified the root cause and taken actions to mitigate the issue and minimize the impact on search functionality.

Investigating: We identified degraded performance in web experiences and Alert Rest API for some Jira Service Management and Opsgenie Cloud customers in the US Region. The team has taken actions to mitigate the issue and minimize the impact on search functionality.

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.

Identified: 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.

Identified: 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.

Identified: 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.

Identified: 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.

Identified: 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.

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.

Identified: All concerned teams are engaged and are working to restore full functionality to new alerts to users from Jira Service Management and Opsgenie.

Escalation teams are also engaged on this incident to try and ensure we can get to a resolution as soon as possible.

Currently, the alerts continue to successfully notify users, but without the intended content within the alerts.

We will continue providing specific updates when available and will ensure we have further update within the hour.

Identified: Our teams priority remains to restore full functionality to new alerts to users from Jira Service Management and Opsgenie.

Escalation teams are fully engaged on this incident to try and ensure we can get to a resolution as soon as possible.

At this time these alerts are still successfully notifying users, but without the intended content within the alerts.

We will continue providing specific updates when available and will ensure we have further update within the hour.

Identified: Our infrastructure teams are working diligently to try and ensure all services are restored to Jira Service Management and Opsgenie as soon as possible.

New alerts are continuing to notify users, however we are still prioritising infrastructure to restore the content inside these alerts for Web and Mobile UIs.

We will continue providing updates when available and will ensure we have further update within the hour.

Identified: Our team is continuing to investigate with the highest level of urgency in order to restore Jira Service Management and Opsgenie services.

At this time we are prioritising infrastructure to try and restore new and active alerts to be populated with their alert content as soon as possible, while continuing to deliver existing messages as they are ready.

We will continue to provide updates as we progress, and will ensure we have an update posted within the hour.

Identified: We have received reports that some customers are experiencing further issues relating to loading pages within Opsgenie and Jira Service Management which may be related to the infrastructure efforts underway to restore services to these products.

Please be aware we also have teams actively investigating these issues to ensure as fast a resolution as possible.

We want to reiterate that your alerts are still sending notifications correctly, and there is no data loss occurring. However, the underlying issue is affecting the propagation of alert details to notifications, and to the Web and Mobile UI.

Viewing schedules may also be impacted at this time while we continue to process the tasks required for recovery.

We will provide further updates as soon as possible.

Identified: New alerts should still continue to notify users as they are generated, however the alert content will still be missing.

Our teams are still actively engaging with infrastructure teams to try and expedite historical processing of messages to fully restore services.

We will provide further updates within the hour.

Identified: While new alerts should now correctly notify users, the content of those alerts for impacted customers will remain empty until missed alerts are fully processed. Our team is continuing to investigate with urgency potential infrastructure options to expedite this process. We will provide further updates within the hour.

Identified: We are continuing to see recovery of Jira Service Management operations and Opsgenie services. There are a large number of missed alerts to be processed due to the prior service issue and our team is actively investigating methods to help expedite this processing. Alerts should trigger in the meantime but the content of these alerts may not be visible at this time. Our teams are continuing to investigate with urgency. We will provide further updates within the hour.

Identified: Our team has been able to identify the root cause of these performance issues and have put a mitigation into place. We are now continuing to see recovery of Jira Service Management operations and Opsgenie services. Existing alerts are continuing to be processed at this time. We will provide further update as soon as possible.

Identified: Our team is still actively working to resolve the issue and making progress toward a resolution. Thank you for your patience.

Identified: We are continuing to work on a fix for this issue.

Identified: We continue to work on resolving the incident for Jira Service Management and Opsgenie. We have identified the root cause and taken actions to mitigate the issue and minimize the impact on search functionality.

Investigating: We identified degraded performance in web experiences and Alert Rest API for some Jira Service Management and Opsgenie Cloud customers in the US Region. The team has taken actions to mitigate the issue and minimize the impact on search functionality.

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.

Identified: 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.

Identified: 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.

Identified: 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.

Identified: 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.

Identified: 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.

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.

Identified: All concerned teams are engaged and are working to restore full functionality to new alerts to users from Jira Service Management and Opsgenie.

Escalation teams are also engaged on this incident to try and ensure we can get to a resolution as soon as possible.

Currently, the alerts continue to successfully notify users, but without the intended content within the alerts.

We will continue providing specific updates when available and will ensure we have further update within the hour.

Identified: Our teams priority remains to restore full functionality to new alerts to users from Jira Service Management and Opsgenie.

Escalation teams are fully engaged on this incident to try and ensure we can get to a resolution as soon as possible.

At this time these alerts are still successfully notifying users, but without the intended content within the alerts.

We will continue providing specific updates when available and will ensure we have further update within the hour.

Identified: Our infrastructure teams are working diligently to try and ensure all services are restored to Jira Service Management and Opsgenie as soon as possible.

New alerts are continuing to notify users, however we are still prioritising infrastructure to restore the content inside these alerts for Web and Mobile UIs.

We will continue providing updates when available and will ensure we have further update within the hour.

Identified: Our team is continuing to investigate with the highest level of urgency in order to restore Jira Service Management and Opsgenie services.

At this time we are prioritising infrastructure to try and restore new and active alerts to be populated with their alert content as soon as possible, while continuing to deliver existing messages as they are ready.

We will continue to provide updates as we progress, and will ensure we have an update posted within the hour.

Identified: We have received reports that some customers are experiencing further issues relating to loading pages within Opsgenie and Jira Service Management which may be related to the infrastructure efforts underway to restore services to these products.

Please be aware we also have teams actively investigating these issues to ensure as fast a resolution as possible.

We want to reiterate that your alerts are still sending notifications correctly, and there is no data loss occurring. However, the underlying issue is affecting the propagation of alert details to notifications, and to the Web and Mobile UI.

Viewing schedules may also be impacted at this time while we continue to process the tasks required for recovery.

We will provide further updates as soon as possible.

Identified: New alerts should still continue to notify users as they are generated, however the alert content will still be missing.

Our teams are still actively engaging with infrastructure teams to try and expedite historical processing of messages to fully restore services.

We will provide further updates within the hour.

Identified: While new alerts should now correctly notify users, the content of those alerts for impacted customers will remain empty until missed alerts are fully processed. Our team is continuing to investigate with urgency potential infrastructure options to expedite this process. We will provide further updates within the hour.

Identified: We are continuing to see recovery of Jira Service Management operations and Opsgenie services. There are a large number of missed alerts to be processed due to the prior service issue and our team is actively investigating methods to help expedite this processing. Alerts should trigger in the meantime but the content of these alerts may not be visible at this time. Our teams are continuing to investigate with urgency. We will provide further updates within the hour.

Identified: Our team has been able to identify the root cause of these performance issues and have put a mitigation into place. We are now continuing to see recovery of Jira Service Management operations and Opsgenie services. Existing alerts are continuing to be processed at this time. We will provide further update as soon as possible.

Identified: Our team is still actively working to resolve the issue and making progress toward a resolution. Thank you for your patience.

Identified: We are continuing to work on a fix for this issue.

Identified: We continue to work on resolving the incident for Jira Service Management and Opsgenie. We have identified the root cause and taken actions to mitigate the issue and minimize the impact on search functionality.

Investigating: We identified degraded performance in web experiences and Alert Rest API for some Jira Service Management and Opsgenie Cloud customers in the US Region. The team has taken actions to mitigate the issue and minimize the impact on search functionality.

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.

Identified: 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.

Identified: 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.

Identified: 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.

Identified: 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.

Identified: 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.

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.

Identified: All concerned teams are engaged and are working to restore full functionality to new alerts to users from Jira Service Management and Opsgenie.

Escalation teams are also engaged on this incident to try and ensure we can get to a resolution as soon as possible.

Currently, the alerts continue to successfully notify users, but without the intended content within the alerts.

We will continue providing specific updates when available and will ensure we have further update within the hour.

Identified: Our teams priority remains to restore full functionality to new alerts to users from Jira Service Management and Opsgenie.

Escalation teams are fully engaged on this incident to try and ensure we can get to a resolution as soon as possible.

At this time these alerts are still successfully notifying users, but without the intended content within the alerts.

We will continue providing specific updates when available and will ensure we have further update within the hour.

Identified: Our infrastructure teams are working diligently to try and ensure all services are restored to Jira Service Management and Opsgenie as soon as possible.

New alerts are continuing to notify users, however we are still prioritising infrastructure to restore the content inside these alerts for Web and Mobile UIs.

We will continue providing updates when available and will ensure we have further update within the hour.

Identified: Our team is continuing to investigate with the highest level of urgency in order to restore Jira Service Management and Opsgenie services.

At this time we are prioritising infrastructure to try and restore new and active alerts to be populated with their alert content as soon as possible, while continuing to deliver existing messages as they are ready.

We will continue to provide updates as we progress, and will ensure we have an update posted within the hour.

Identified: We have received reports that some customers are experiencing further issues relating to loading pages within Opsgenie and Jira Service Management which may be related to the infrastructure efforts underway to restore services to these products.

Please be aware we also have teams actively investigating these issues to ensure as fast a resolution as possible.

We want to reiterate that your alerts are still sending notifications correctly, and there is no data loss occurring. However, the underlying issue is affecting the propagation of alert details to notifications, and to the Web and Mobile UI.

Viewing schedules may also be impacted at this time while we continue to process the tasks required for recovery.

We will provide further updates as soon as possible.

Identified: New alerts should still continue to notify users as they are generated, however the alert content will still be missing.

Our teams are still actively engaging with infrastructure teams to try and expedite historical processing of messages to fully restore services.

We will provide further updates within the hour.

Identified: While new alerts should now correctly notify users, the content of those alerts for impacted customers will remain empty until missed alerts are fully processed. Our team is continuing to investigate with urgency potential infrastructure options to expedite this process. We will provide further updates within the hour.

Identified: We are continuing to see recovery of Jira Service Management operations and Opsgenie services. There are a large number of missed alerts to be processed due to the prior service issue and our team is actively investigating methods to help expedite this processing. Alerts should trigger in the meantime but the content of these alerts may not be visible at this time. Our teams are continuing to investigate with urgency. We will provide further updates within the hour.

Identified: Our team has been able to identify the root cause of these performance issues and have put a mitigation into place. We are now continuing to see recovery of Jira Service Management operations and Opsgenie services. Existing alerts are continuing to be processed at this time. We will provide further update as soon as possible.

Identified: Our team is still actively working to resolve the issue and making progress toward a resolution. Thank you for your patience.

Identified: We are continuing to work on a fix for this issue.

Identified: We continue to work on resolving the incident for Jira Service Management and Opsgenie. We have identified the root cause and taken actions to mitigate the issue and minimize the impact on search functionality.

Investigating: We identified degraded performance in web experiences and Alert Rest API for some Jira Service Management and Opsgenie Cloud customers in the US Region. The team has taken actions to mitigate the issue and minimize the impact on search functionality.

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.

Identified: 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.

Identified: 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.

Identified: 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.

Identified: 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.

Identified: 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.

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.

Identified: All concerned teams are engaged and are working to restore full functionality to new alerts to users from Jira Service Management and Opsgenie.

Escalation teams are also engaged on this incident to try and ensure we can get to a resolution as soon as possible.

Currently, the alerts continue to successfully notify users, but without the intended content within the alerts.

We will continue providing specific updates when available and will ensure we have further update within the hour.

Identified: Our teams priority remains to restore full functionality to new alerts to users from Jira Service Management and Opsgenie.

Escalation teams are fully engaged on this incident to try and ensure we can get to a resolution as soon as possible.

At this time these alerts are still successfully notifying users, but without the intended content within the alerts.

We will continue providing specific updates when available and will ensure we have further update within the hour.

Identified: Our infrastructure teams are working diligently to try and ensure all services are restored to Jira Service Management and Opsgenie as soon as possible.

New alerts are continuing to notify users, however we are still prioritising infrastructure to restore the content inside these alerts for Web and Mobile UIs.

We will continue providing updates when available and will ensure we have further update within the hour.

Identified: Our team is continuing to investigate with the highest level of urgency in order to restore Jira Service Management and Opsgenie services.

At this time we are prioritising infrastructure to try and restore new and active alerts to be populated with their alert content as soon as possible, while continuing to deliver existing messages as they are ready.

We will continue to provide updates as we progress, and will ensure we have an update posted within the hour.

Identified: We have received reports that some customers are experiencing further issues relating to loading pages within Opsgenie and Jira Service Management which may be related to the infrastructure efforts underway to restore services to these products.

Please be aware we also have teams actively investigating these issues to ensure as fast a resolution as possible.

We want to reiterate that your alerts are still sending notifications correctly, and there is no data loss occurring. However, the underlying issue is affecting the propagation of alert details to notifications, and to the Web and Mobile UI.

Viewing schedules may also be impacted at this time while we continue to process the tasks required for recovery.

We will provide further updates as soon as possible.

Identified: New alerts should still continue to notify users as they are generated, however the alert content will still be missing.

Our teams are still actively engaging with infrastructure teams to try and expedite historical processing of messages to fully restore services.

We will provide further updates within the hour.

Identified: While new alerts should now correctly notify users, the content of those alerts for impacted customers will remain empty until missed alerts are fully processed. Our team is continuing to investigate with urgency potential infrastructure options to expedite this process. We will provide further updates within the hour.

Identified: We are continuing to see recovery of Jira Service Management operations and Opsgenie services. There are a large number of missed alerts to be processed due to the prior service issue and our team is actively investigating methods to help expedite this processing. Alerts should trigger in the meantime but the content of these alerts may not be visible at this time. Our teams are continuing to investigate with urgency. We will provide further updates within the hour.

Identified: Our team has been able to identify the root cause of these performance issues and have put a mitigation into place. We are now continuing to see recovery of Jira Service Management operations and Opsgenie services. Existing alerts are continuing to be processed at this time. We will provide further update as soon as possible.

Identified: Our team is still actively working to resolve the issue and making progress toward a resolution. Thank you for your patience.

Identified: We are continuing to work on a fix for this issue.

Identified: We continue to work on resolving the incident for Jira Service Management and Opsgenie. We have identified the root cause and taken actions to mitigate the issue and minimize the impact on search functionality.

Investigating: We identified degraded performance in web experiences and Alert Rest API for some Jira Service Management and Opsgenie Cloud customers in the US Region. The team has taken actions to mitigate the issue and minimize the impact on search functionality.

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.

Identified: 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.

Identified: 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.

Identified: 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.

Identified: 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.

Identified: 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.

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.

Identified: All concerned teams are engaged and are working to restore full functionality to new alerts to users from Jira Service Management and Opsgenie.

Escalation teams are also engaged on this incident to try and ensure we can get to a resolution as soon as possible.

Currently, the alerts continue to successfully notify users, but without the intended content within the alerts.

We will continue providing specific updates when available and will ensure we have further update within the hour.

Identified: Our teams priority remains to restore full functionality to new alerts to users from Jira Service Management and Opsgenie.

Escalation teams are fully engaged on this incident to try and ensure we can get to a resolution as soon as possible.

At this time these alerts are still successfully notifying users, but without the intended content within the alerts.

We will continue providing specific updates when available and will ensure we have further update within the hour.

Identified: Our infrastructure teams are working diligently to try and ensure all services are restored to Jira Service Management and Opsgenie as soon as possible.

New alerts are continuing to notify users, however we are still prioritising infrastructure to restore the content inside these alerts for Web and Mobile UIs.

We will continue providing updates when available and will ensure we have further update within the hour.

Identified: Our team is continuing to investigate with the highest level of urgency in order to restore Jira Service Management and Opsgenie services.

At this time we are prioritising infrastructure to try and restore new and active alerts to be populated with their alert content as soon as possible, while continuing to deliver existing messages as they are ready.

We will continue to provide updates as we progress, and will ensure we have an update posted within the hour.

Identified: We have received reports that some customers are experiencing further issues relating to loading pages within Opsgenie and Jira Service Management which may be related to the infrastructure efforts underway to restore services to these products.

Please be aware we also have teams actively investigating these issues to ensure as fast a resolution as possible.

We want to reiterate that your alerts are still sending notifications correctly, and there is no data loss occurring. However, the underlying issue is affecting the propagation of alert details to notifications, and to the Web and Mobile UI.

Viewing schedules may also be impacted at this time while we continue to process the tasks required for recovery.

We will provide further updates as soon as possible.

Identified: New alerts should still continue to notify users as they are generated, however the alert content will still be missing.

Our teams are still actively engaging with infrastructure teams to try and expedite historical processing of messages to fully restore services.

We will provide further updates within the hour.

Identified: While new alerts should now correctly notify users, the content of those alerts for impacted customers will remain empty until missed alerts are fully processed. Our team is continuing to investigate with urgency potential infrastructure options to expedite this process. We will provide further updates within the hour.

Identified: We are continuing to see recovery of Jira Service Management operations and Opsgenie services. There are a large number of missed alerts to be processed due to the prior service issue and our team is actively investigating methods to help expedite this processing. Alerts should trigger in the meantime but the content of these alerts may not be visible at this time. Our teams are continuing to investigate with urgency. We will provide further updates within the hour.

Identified: Our team has been able to identify the root cause of these performance issues and have put a mitigation into place. We are now continuing to see recovery of Jira Service Management operations and Opsgenie services. Existing alerts are continuing to be processed at this time. We will provide further update as soon as possible.

Identified: Our team is still actively working to resolve the issue and making progress toward a resolution. Thank you for your patience.

Identified: We are continuing to work on a fix for this issue.

Identified: We continue to work on resolving the incident for Jira Service Management and Opsgenie. We have identified the root cause and taken actions to mitigate the issue and minimize the impact on search functionality.

Investigating: We identified degraded performance in web experiences and Alert Rest API for some Jira Service Management and Opsgenie Cloud customers in the US Region. The team has taken actions to mitigate the issue and minimize the impact on search functionality.

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.

Identified: 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.

Identified: 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.

Identified: 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.

Identified: 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.

Identified: 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.

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.

Identified: All concerned teams are engaged and are working to restore full functionality to new alerts to users from Jira Service Management and Opsgenie.

Escalation teams are also engaged on this incident to try and ensure we can get to a resolution as soon as possible.

Currently, the alerts continue to successfully notify users, but without the intended content within the alerts.

We will continue providing specific updates when available and will ensure we have further update within the hour.

Identified: Our teams priority remains to restore full functionality to new alerts to users from Jira Service Management and Opsgenie.

Escalation teams are fully engaged on this incident to try and ensure we can get to a resolution as soon as possible.

At this time these alerts are still successfully notifying users, but without the intended content within the alerts.

We will continue providing specific updates when available and will ensure we have further update within the hour.

Identified: Our infrastructure teams are working diligently to try and ensure all services are restored to Jira Service Management and Opsgenie as soon as possible.

New alerts are continuing to notify users, however we are still prioritising infrastructure to restore the content inside these alerts for Web and Mobile UIs.

We will continue providing updates when available and will ensure we have further update within the hour.

Identified: Our team is continuing to investigate with the highest level of urgency in order to restore Jira Service Management and Opsgenie services.

At this time we are prioritising infrastructure to try and restore new and active alerts to be populated with their alert content as soon as possible, while continuing to deliver existing messages as they are ready.

We will continue to provide updates as we progress, and will ensure we have an update posted within the hour.

Identified: We have received reports that some customers are experiencing further issues relating to loading pages within Opsgenie and Jira Service Management which may be related to the infrastructure efforts underway to restore services to these products.

Please be aware we also have teams actively investigating these issues to ensure as fast a resolution as possible.

We want to reiterate that your alerts are still sending notifications correctly, and there is no data loss occurring. However, the underlying issue is affecting the propagation of alert details to notifications, and to the Web and Mobile UI.

Viewing schedules may also be impacted at this time while we continue to process the tasks required for recovery.

We will provide further updates as soon as possible.

Identified: New alerts should still continue to notify users as they are generated, however the alert content will still be missing.

Our teams are still actively engaging with infrastructure teams to try and expedite historical processing of messages to fully restore services.

We will provide further updates within the hour.

Identified: While new alerts should now correctly notify users, the content of those alerts for impacted customers will remain empty until missed alerts are fully processed. Our team is continuing to investigate with urgency potential infrastructure options to expedite this process. We will provide further updates within the hour.

Identified: We are continuing to see recovery of Jira Service Management operations and Opsgenie services. There are a large number of missed alerts to be processed due to the prior service issue and our team is actively investigating methods to help expedite this processing. Alerts should trigger in the meantime but the content of these alerts may not be visible at this time. Our teams are continuing to investigate with urgency. We will provide further updates within the hour.

Identified: Our team has been able to identify the root cause of these performance issues and have put a mitigation into place. We are now continuing to see recovery of Jira Service Management operations and Opsgenie services. Existing alerts are continuing to be processed at this time. We will provide further update as soon as possible.

Identified: Our team is still actively working to resolve the issue and making progress toward a resolution. Thank you for your patience.

Identified: We are continuing to work on a fix for this issue.

Identified: We continue to work on resolving the incident for Jira Service Management and Opsgenie. We have identified the root cause and taken actions to mitigate the issue and minimize the impact on search functionality.

Investigating: We identified degraded performance in web experiences and Alert Rest API for some Jira Service Management and Opsgenie Cloud customers in the US Region. The team has taken actions to mitigate the issue and minimize the impact on search functionality.

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.

Identified: 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.

Identified: 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.

Identified: 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.

Identified: 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.

Identified: 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.

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.

Identified: All concerned teams are engaged and are working to restore full functionality to new alerts to users from Jira Service Management and Opsgenie.

Escalation teams are also engaged on this incident to try and ensure we can get to a resolution as soon as possible.

Currently, the alerts continue to successfully notify users, but without the intended content within the alerts.

We will continue providing specific updates when available and will ensure we have further update within the hour.

Identified: Our teams priority remains to restore full functionality to new alerts to users from Jira Service Management and Opsgenie.

Escalation teams are fully engaged on this incident to try and ensure we can get to a resolution as soon as possible.

At this time these alerts are still successfully notifying users, but without the intended content within the alerts.

We will continue providing specific updates when available and will ensure we have further update within the hour.

Identified: Our infrastructure teams are working diligently to try and ensure all services are restored to Jira Service Management and Opsgenie as soon as possible.

New alerts are continuing to notify users, however we are still prioritising infrastructure to restore the content inside these alerts for Web and Mobile UIs.

We will continue providing updates when available and will ensure we have further update within the hour.

Identified: Our team is continuing to investigate with the highest level of urgency in order to restore Jira Service Management and Opsgenie services.

At this time we are prioritising infrastructure to try and restore new and active alerts to be populated with their alert content as soon as possible, while continuing to deliver existing messages as they are ready.

We will continue to provide updates as we progress, and will ensure we have an update posted within the hour.

Identified: We have received reports that some customers are experiencing further issues relating to loading pages within Opsgenie and Jira Service Management which may be related to the infrastructure efforts underway to restore services to these products.

Please be aware we also have teams actively investigating these issues to ensure as fast a resolution as possible.

We want to reiterate that your alerts are still sending notifications correctly, and there is no data loss occurring. However, the underlying issue is affecting the propagation of alert details to notifications, and to the Web and Mobile UI.

Viewing schedules may also be impacted at this time while we continue to process the tasks required for recovery.

We will provide further updates as soon as possible.

Identified: New alerts should still continue to notify users as they are generated, however the alert content will still be missing.

Our teams are still actively engaging with infrastructure teams to try and expedite historical processing of messages to fully restore services.

We will provide further updates within the hour.

Identified: While new alerts should now correctly notify users, the content of those alerts for impacted customers will remain empty until missed alerts are fully processed. Our team is continuing to investigate with urgency potential infrastructure options to expedite this process. We will provide further updates within the hour.

Identified: We are continuing to see recovery of Jira Service Management operations and Opsgenie services. There are a large number of missed alerts to be processed due to the prior service issue and our team is actively investigating methods to help expedite this processing. Alerts should trigger in the meantime but the content of these alerts may not be visible at this time. Our teams are continuing to investigate with urgency. We will provide further updates within the hour.

Identified: Our team has been able to identify the root cause of these performance issues and have put a mitigation into place. We are now continuing to see recovery of Jira Service Management operations and Opsgenie services. Existing alerts are continuing to be processed at this time. We will provide further update as soon as possible.

Identified: Our team is still actively working to resolve the issue and making progress toward a resolution. Thank you for your patience.

Identified: We are continuing to work on a fix for this issue.

Identified: We continue to work on resolving the incident for Jira Service Management and Opsgenie. We have identified the root cause and taken actions to mitigate the issue and minimize the impact on search functionality.

Investigating: We identified degraded performance in web experiences and Alert Rest API for some Jira Service Management and Opsgenie Cloud customers in the US Region. The team has taken actions to mitigate the issue and minimize the impact on search functionality.

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.

Identified: 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.

Identified: 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.

Identified: 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.

Identified: 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.

Identified: 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.

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.

Identified: All concerned teams are engaged and are working to restore full functionality to new alerts to users from Jira Service Management and Opsgenie.

Escalation teams are also engaged on this incident to try and ensure we can get to a resolution as soon as possible.

Currently, the alerts continue to successfully notify users, but without the intended content within the alerts.

We will continue providing specific updates when available and will ensure we have further update within the hour.

Identified: Our teams priority remains to restore full functionality to new alerts to users from Jira Service Management and Opsgenie.

Escalation teams are fully engaged on this incident to try and ensure we can get to a resolution as soon as possible.

At this time these alerts are still successfully notifying users, but without the intended content within the alerts.

We will continue providing specific updates when available and will ensure we have further update within the hour.

Identified: Our infrastructure teams are working diligently to try and ensure all services are restored to Jira Service Management and Opsgenie as soon as possible.

New alerts are continuing to notify users, however we are still prioritising infrastructure to restore the content inside these alerts for Web and Mobile UIs.

We will continue providing updates when available and will ensure we have further update within the hour.

Identified: Our team is continuing to investigate with the highest level of urgency in order to restore Jira Service Management and Opsgenie services.

At this time we are prioritising infrastructure to try and restore new and active alerts to be populated with their alert content as soon as possible, while continuing to deliver existing messages as they are ready.

We will continue to provide updates as we progress, and will ensure we have an update posted within the hour.

Identified: We have received reports that some customers are experiencing further issues relating to loading pages within Opsgenie and Jira Service Management which may be related to the infrastructure efforts underway to restore services to these products.

Please be aware we also have teams actively investigating these issues to ensure as fast a resolution as possible.

We want to reiterate that your alerts are still sending notifications correctly, and there is no data loss occurring. However, the underlying issue is affecting the propagation of alert details to notifications, and to the Web and Mobile UI.

Viewing schedules may also be impacted at this time while we continue to process the tasks required for recovery.

We will provide further updates as soon as possible.

Identified: New alerts should still continue to notify users as they are generated, however the alert content will still be missing.

Our teams are still actively engaging with infrastructure teams to try and expedite historical processing of messages to fully restore services.

We will provide further updates within the hour.

Identified: While new alerts should now correctly notify users, the content of those alerts for impacted customers will remain empty until missed alerts are fully processed. Our team is continuing to investigate with urgency potential infrastructure options to expedite this process. We will provide further updates within the hour.

Identified: We are continuing to see recovery of Jira Service Management operations and Opsgenie services. There are a large number of missed alerts to be processed due to the prior service issue and our team is actively investigating methods to help expedite this processing. Alerts should trigger in the meantime but the content of these alerts may not be visible at this time. Our teams are continuing to investigate with urgency. We will provide further updates within the hour.

Identified: Our team has been able to identify the root cause of these performance issues and have put a mitigation into place. We are now continuing to see recovery of Jira Service Management operations and Opsgenie services. Existing alerts are continuing to be processed at this time. We will provide further update as soon as possible.

Identified: Our team is still actively working to resolve the issue and making progress toward a resolution. Thank you for your patience.

Identified: We are continuing to work on a fix for this issue.

Identified: We continue to work on resolving the incident for Jira Service Management and Opsgenie. We have identified the root cause and taken actions to mitigate the issue and minimize the impact on search functionality.

Investigating: We identified degraded performance in web experiences and Alert Rest API for some Jira Service Management and Opsgenie Cloud customers in the US Region. The team has taken actions to mitigate the issue and minimize the impact on search functionality.

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.

Identified: 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.

Identified: 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.

Identified: 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.

Identified: 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.

Identified: 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.

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.

Identified: All concerned teams are engaged and are working to restore full functionality to new alerts to users from Jira Service Management and Opsgenie.

Escalation teams are also engaged on this incident to try and ensure we can get to a resolution as soon as possible.

Currently, the alerts continue to successfully notify users, but without the intended content within the alerts.

We will continue providing specific updates when available and will ensure we have further update within the hour.

Identified: Our teams priority remains to restore full functionality to new alerts to users from Jira Service Management and Opsgenie.

Escalation teams are fully engaged on this incident to try and ensure we can get to a resolution as soon as possible.

At this time these alerts are still successfully notifying users, but without the intended content within the alerts.

We will continue providing specific updates when available and will ensure we have further update within the hour.

Identified: Our infrastructure teams are working diligently to try and ensure all services are restored to Jira Service Management and Opsgenie as soon as possible.

New alerts are continuing to notify users, however we are still prioritising infrastructure to restore the content inside these alerts for Web and Mobile UIs.

We will continue providing updates when available and will ensure we have further update within the hour.

Identified: Our team is continuing to investigate with the highest level of urgency in order to restore Jira Service Management and Opsgenie services.

At this time we are prioritising infrastructure to try and restore new and active alerts to be populated with their alert content as soon as possible, while continuing to deliver existing messages as they are ready.

We will continue to provide updates as we progress, and will ensure we have an update posted within the hour.

Identified: We have received reports that some customers are experiencing further issues relating to loading pages within Opsgenie and Jira Service Management which may be related to the infrastructure efforts underway to restore services to these products.

Please be aware we also have teams actively investigating these issues to ensure as fast a resolution as possible.

We want to reiterate that your alerts are still sending notifications correctly, and there is no data loss occurring. However, the underlying issue is affecting the propagation of alert details to notifications, and to the Web and Mobile UI.

Viewing schedules may also be impacted at this time while we continue to process the tasks required for recovery.

We will provide further updates as soon as possible.

Identified: New alerts should still continue to notify users as they are generated, however the alert content will still be missing.

Our teams are still actively engaging with infrastructure teams to try and expedite historical processing of messages to fully restore services.

We will provide further updates within the hour.

Identified: While new alerts should now correctly notify users, the content of those alerts for impacted customers will remain empty until missed alerts are fully processed. Our team is continuing to investigate with urgency potential infrastructure options to expedite this process. We will provide further updates within the hour.

Identified: We are continuing to see recovery of Jira Service Management operations and Opsgenie services. There are a large number of missed alerts to be processed due to the prior service issue and our team is actively investigating methods to help expedite this processing. Alerts should trigger in the meantime but the content of these alerts may not be visible at this time. Our teams are continuing to investigate with urgency. We will provide further updates within the hour.

Identified: Our team has been able to identify the root cause of these performance issues and have put a mitigation into place. We are now continuing to see recovery of Jira Service Management operations and Opsgenie services. Existing alerts are continuing to be processed at this time. We will provide further update as soon as possible.

Identified: Our team is still actively working to resolve the issue and making progress toward a resolution. Thank you for your patience.

Identified: We are continuing to work on a fix for this issue.

Identified: We continue to work on resolving the incident for Jira Service Management and Opsgenie. We have identified the root cause and taken actions to mitigate the issue and minimize the impact on search functionality.

Investigating: We identified degraded performance in web experiences and Alert Rest API for some Jira Service Management and Opsgenie Cloud customers in the US Region. The team has taken actions to mitigate the issue and minimize the impact on search functionality.

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.

Identified: 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.

Identified: 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.

Identified: 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.

Identified: 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.

Identified: 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.

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.

Identified: All concerned teams are engaged and are working to restore full functionality to new alerts to users from Jira Service Management and Opsgenie.

Escalation teams are also engaged on this incident to try and ensure we can get to a resolution as soon as possible.

Currently, the alerts continue to successfully notify users, but without the intended content within the alerts.

We will continue providing specific updates when available and will ensure we have further update within the hour.

Identified: Our teams priority remains to restore full functionality to new alerts to users from Jira Service Management and Opsgenie.

Escalation teams are fully engaged on this incident to try and ensure we can get to a resolution as soon as possible.

At this time these alerts are still successfully notifying users, but without the intended content within the alerts.

We will continue providing specific updates when available and will ensure we have further update within the hour.

Identified: Our infrastructure teams are working diligently to try and ensure all services are restored to Jira Service Management and Opsgenie as soon as possible.

New alerts are continuing to notify users, however we are still prioritising infrastructure to restore the content inside these alerts for Web and Mobile UIs.

We will continue providing updates when available and will ensure we have further update within the hour.

Identified: Our team is continuing to investigate with the highest level of urgency in order to restore Jira Service Management and Opsgenie services.

At this time we are prioritising infrastructure to try and restore new and active alerts to be populated with their alert content as soon as possible, while continuing to deliver existing messages as they are ready.

We will continue to provide updates as we progress, and will ensure we have an update posted within the hour.

Identified: We have received reports that some customers are experiencing further issues relating to loading pages within Opsgenie and Jira Service Management which may be related to the infrastructure efforts underway to restore services to these products.

Please be aware we also have teams actively investigating these issues to ensure as fast a resolution as possible.

We want to reiterate that your alerts are still sending notifications correctly, and there is no data loss occurring. However, the underlying issue is affecting the propagation of alert details to notifications, and to the Web and Mobile UI.

Viewing schedules may also be impacted at this time while we continue to process the tasks required for recovery.

We will provide further updates as soon as possible.

Identified: New alerts should still continue to notify users as they are generated, however the alert content will still be missing.

Our teams are still actively engaging with infrastructure teams to try and expedite historical processing of messages to fully restore services.

We will provide further updates within the hour.

Identified: While new alerts should now correctly notify users, the content of those alerts for impacted customers will remain empty until missed alerts are fully processed. Our team is continuing to investigate with urgency potential infrastructure options to expedite this process. We will provide further updates within the hour.

Identified: We are continuing to see recovery of Jira Service Management operations and Opsgenie services. There are a large number of missed alerts to be processed due to the prior service issue and our team is actively investigating methods to help expedite this processing. Alerts should trigger in the meantime but the content of these alerts may not be visible at this time. Our teams are continuing to investigate with urgency. We will provide further updates within the hour.

Identified: Our team has been able to identify the root cause of these performance issues and have put a mitigation into place. We are now continuing to see recovery of Jira Service Management operations and Opsgenie services. Existing alerts are continuing to be processed at this time. We will provide further update as soon as possible.

Identified: Our team is still actively working to resolve the issue and making progress toward a resolution. Thank you for your patience.

Identified: We are continuing to work on a fix for this issue.

Identified: We continue to work on resolving the incident for Jira Service Management and Opsgenie. We have identified the root cause and taken actions to mitigate the issue and minimize the impact on search functionality.

Investigating: We identified degraded performance in web experiences and Alert Rest API for some Jira Service Management and Opsgenie Cloud customers in the US Region. The team has taken actions to mitigate the issue and minimize the impact on search functionality.

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.

Identified: 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.

Identified: 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.

Identified: 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.

Identified: 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.

Identified: 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.

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.

Identified: All concerned teams are engaged and are working to restore full functionality to new alerts to users from Jira Service Management and Opsgenie.

Escalation teams are also engaged on this incident to try and ensure we can get to a resolution as soon as possible.

Currently, the alerts continue to successfully notify users, but without the intended content within the alerts.

We will continue providing specific updates when available and will ensure we have further update within the hour.

Identified: Our teams priority remains to restore full functionality to new alerts to users from Jira Service Management and Opsgenie.

Escalation teams are fully engaged on this incident to try and ensure we can get to a resolution as soon as possible.

At this time these alerts are still successfully notifying users, but without the intended content within the alerts.

We will continue providing specific updates when available and will ensure we have further update within the hour.

Identified: Our infrastructure teams are working diligently to try and ensure all services are restored to Jira Service Management and Opsgenie as soon as possible.

New alerts are continuing to notify users, however we are still prioritising infrastructure to restore the content inside these alerts for Web and Mobile UIs.

We will continue providing updates when available and will ensure we have further update within the hour.

Identified: Our team is continuing to investigate with the highest level of urgency in order to restore Jira Service Management and Opsgenie services.

At this time we are prioritising infrastructure to try and restore new and active alerts to be populated with their alert content as soon as possible, while continuing to deliver existing messages as they are ready.

We will continue to provide updates as we progress, and will ensure we have an update posted within the hour.

Identified: We have received reports that some customers are experiencing further issues relating to loading pages within Opsgenie and Jira Service Management which may be related to the infrastructure efforts underway to restore services to these products.

Please be aware we also have teams actively investigating these issues to ensure as fast a resolution as possible.

We want to reiterate that your alerts are still sending notifications correctly, and there is no data loss occurring. However, the underlying issue is affecting the propagation of alert details to notifications, and to the Web and Mobile UI.

Viewing schedules may also be impacted at this time while we continue to process the tasks required for recovery.

We will provide further updates as soon as possible.

Identified: New alerts should still continue to notify users as they are generated, however the alert content will still be missing.

Our teams are still actively engaging with infrastructure teams to try and expedite historical processing of messages to fully restore services.

We will provide further updates within the hour.

Identified: While new alerts should now correctly notify users, the content of those alerts for impacted customers will remain empty until missed alerts are fully processed. Our team is continuing to investigate with urgency potential infrastructure options to expedite this process. We will provide further updates within the hour.

Identified: We are continuing to see recovery of Jira Service Management operations and Opsgenie services. There are a large number of missed alerts to be processed due to the prior service issue and our team is actively investigating methods to help expedite this processing. Alerts should trigger in the meantime but the content of these alerts may not be visible at this time. Our teams are continuing to investigate with urgency. We will provide further updates within the hour.

Identified: Our team has been able to identify the root cause of these performance issues and have put a mitigation into place. We are now continuing to see recovery of Jira Service Management operations and Opsgenie services. Existing alerts are continuing to be processed at this time. We will provide further update as soon as possible.

Identified: Our team is still actively working to resolve the issue and making progress toward a resolution. Thank you for your patience.

Identified: We are continuing to work on a fix for this issue.

Identified: We continue to work on resolving the incident for Jira Service Management and Opsgenie. We have identified the root cause and taken actions to mitigate the issue and minimize the impact on search functionality.

Investigating: We identified degraded performance in web experiences and Alert Rest API for some Jira Service Management and Opsgenie Cloud customers in the US Region. The team has taken actions to mitigate the issue and minimize the impact on search functionality.

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.

Identified: 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.

Identified: 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.

Identified: 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.

Identified: 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.

Identified: 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.

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.

Identified: All concerned teams are engaged and are working to restore full functionality to new alerts to users from Jira Service Management and Opsgenie.

Escalation teams are also engaged on this incident to try and ensure we can get to a resolution as soon as possible.

Currently, the alerts continue to successfully notify users, but without the intended content within the alerts.

We will continue providing specific updates when available and will ensure we have further update within the hour.

Identified: Our teams priority remains to restore full functionality to new alerts to users from Jira Service Management and Opsgenie.

Escalation teams are fully engaged on this incident to try and ensure we can get to a resolution as soon as possible.

At this time these alerts are still successfully notifying users, but without the intended content within the alerts.

We will continue providing specific updates when available and will ensure we have further update within the hour.

Identified: Our infrastructure teams are working diligently to try and ensure all services are restored to Jira Service Management and Opsgenie as soon as possible.

New alerts are continuing to notify users, however we are still prioritising infrastructure to restore the content inside these alerts for Web and Mobile UIs.

We will continue providing updates when available and will ensure we have further update within the hour.

Identified: Our team is continuing to investigate with the highest level of urgency in order to restore Jira Service Management and Opsgenie services.

At this time we are prioritising infrastructure to try and restore new and active alerts to be populated with their alert content as soon as possible, while continuing to deliver existing messages as they are ready.

We will continue to provide updates as we progress, and will ensure we have an update posted within the hour.

Identified: We have received reports that some customers are experiencing further issues relating to loading pages within Opsgenie and Jira Service Management which may be related to the infrastructure efforts underway to restore services to these products.

Please be aware we also have teams actively investigating these issues to ensure as fast a resolution as possible.

We want to reiterate that your alerts are still sending notifications correctly, and there is no data loss occurring. However, the underlying issue is affecting the propagation of alert details to notifications, and to the Web and Mobile UI.

Viewing schedules may also be impacted at this time while we continue to process the tasks required for recovery.

We will provide further updates as soon as possible.

Identified: New alerts should still continue to notify users as they are generated, however the alert content will still be missing.

Our teams are still actively engaging with infrastructure teams to try and expedite historical processing of messages to fully restore services.

We will provide further updates within the hour.

Identified: While new alerts should now correctly notify users, the content of those alerts for impacted customers will remain empty until missed alerts are fully processed. Our team is continuing to investigate with urgency potential infrastructure options to expedite this process. We will provide further updates within the hour.

Identified: We are continuing to see recovery of Jira Service Management operations and Opsgenie services. There are a large number of missed alerts to be processed due to the prior service issue and our team is actively investigating methods to help expedite this processing. Alerts should trigger in the meantime but the content of these alerts may not be visible at this time. Our teams are continuing to investigate with urgency. We will provide further updates within the hour.

Identified: Our team has been able to identify the root cause of these performance issues and have put a mitigation into place. We are now continuing to see recovery of Jira Service Management operations and Opsgenie services. Existing alerts are continuing to be processed at this time. We will provide further update as soon as possible.

Identified: Our team is still actively working to resolve the issue and making progress toward a resolution. Thank you for your patience.

Identified: We are continuing to work on a fix for this issue.

Identified: We continue to work on resolving the incident for Jira Service Management and Opsgenie. We have identified the root cause and taken actions to mitigate the issue and minimize the impact on search functionality.

Investigating: We identified degraded performance in web experiences and Alert Rest API for some Jira Service Management and Opsgenie Cloud customers in the US Region. The team has taken actions to mitigate the issue and minimize the impact on search functionality.

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.

Identified: 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.

Identified: 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.

Identified: 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.

Identified: 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.

Identified: 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.

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.

Identified: All concerned teams are engaged and are working to restore full functionality to new alerts to users from Jira Service Management and Opsgenie.

Escalation teams are also engaged on this incident to try and ensure we can get to a resolution as soon as possible.

Currently, the alerts continue to successfully notify users, but without the intended content within the alerts.

We will continue providing specific updates when available and will ensure we have further update within the hour.

Identified: Our teams priority remains to restore full functionality to new alerts to users from Jira Service Management and Opsgenie.

Escalation teams are fully engaged on this incident to try and ensure we can get to a resolution as soon as possible.

At this time these alerts are still successfully notifying users, but without the intended content within the alerts.

We will continue providing specific updates when available and will ensure we have further update within the hour.

Identified: Our infrastructure teams are working diligently to try and ensure all services are restored to Jira Service Management and Opsgenie as soon as possible.

New alerts are continuing to notify users, however we are still prioritising infrastructure to restore the content inside these alerts for Web and Mobile UIs.

We will continue providing updates when available and will ensure we have further update within the hour.

Identified: Our team is continuing to investigate with the highest level of urgency in order to restore Jira Service Management and Opsgenie services.

At this time we are prioritising infrastructure to try and restore new and active alerts to be populated with their alert content as soon as possible, while continuing to deliver existing messages as they are ready.

We will continue to provide updates as we progress, and will ensure we have an update posted within the hour.

Identified: We have received reports that some customers are experiencing further issues relating to loading pages within Opsgenie and Jira Service Management which may be related to the infrastructure efforts underway to restore services to these products.

Please be aware we also have teams actively investigating these issues to ensure as fast a resolution as possible.

We want to reiterate that your alerts are still sending notifications correctly, and there is no data loss occurring. However, the underlying issue is affecting the propagation of alert details to notifications, and to the Web and Mobile UI.

Viewing schedules may also be impacted at this time while we continue to process the tasks required for recovery.

We will provide further updates as soon as possible.

Identified: New alerts should still continue to notify users as they are generated, however the alert content will still be missing.

Our teams are still actively engaging with infrastructure teams to try and expedite historical processing of messages to fully restore services.

We will provide further updates within the hour.

Identified: While new alerts should now correctly notify users, the content of those alerts for impacted customers will remain empty until missed alerts are fully processed. Our team is continuing to investigate with urgency potential infrastructure options to expedite this process. We will provide further updates within the hour.

Identified: We are continuing to see recovery of Jira Service Management operations and Opsgenie services. There are a large number of missed alerts to be processed due to the prior service issue and our team is actively investigating methods to help expedite this processing. Alerts should trigger in the meantime but the content of these alerts may not be visible at this time. Our teams are continuing to investigate with urgency. We will provide further updates within the hour.

Identified: Our team has been able to identify the root cause of these performance issues and have put a mitigation into place. We are now continuing to see recovery of Jira Service Management operations and Opsgenie services. Existing alerts are continuing to be processed at this time. We will provide further update as soon as possible.

Identified: Our team is still actively working to resolve the issue and making progress toward a resolution. Thank you for your patience.

Identified: We are continuing to work on a fix for this issue.

Identified: We continue to work on resolving the incident for Jira Service Management and Opsgenie. We have identified the root cause and taken actions to mitigate the issue and minimize the impact on search functionality.

Investigating: We identified degraded performance in web experiences and Alert Rest API for some Jira Service Management and Opsgenie Cloud customers in the US Region. The team has taken actions to mitigate the issue and minimize the impact on search functionality.

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.

Identified: 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.

Identified: 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.

Identified: 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.

Identified: 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.

Identified: 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.

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.

Identified: All concerned teams are engaged and are working to restore full functionality to new alerts to users from Jira Service Management and Opsgenie.

Escalation teams are also engaged on this incident to try and ensure we can get to a resolution as soon as possible.

Currently, the alerts continue to successfully notify users, but without the intended content within the alerts.

We will continue providing specific updates when available and will ensure we have further update within the hour.

Identified: Our teams priority remains to restore full functionality to new alerts to users from Jira Service Management and Opsgenie.

Escalation teams are fully engaged on this incident to try and ensure we can get to a resolution as soon as possible.

At this time these alerts are still successfully notifying users, but without the intended content within the alerts.

We will continue providing specific updates when available and will ensure we have further update within the hour.

Identified: Our infrastructure teams are working diligently to try and ensure all services are restored to Jira Service Management and Opsgenie as soon as possible.

New alerts are continuing to notify users, however we are still prioritising infrastructure to restore the content inside these alerts for Web and Mobile UIs.

We will continue providing updates when available and will ensure we have further update within the hour.

Identified: Our team is continuing to investigate with the highest level of urgency in order to restore Jira Service Management and Opsgenie services.

At this time we are prioritising infrastructure to try and restore new and active alerts to be populated with their alert content as soon as possible, while continuing to deliver existing messages as they are ready.

We will continue to provide updates as we progress, and will ensure we have an update posted within the hour.

Identified: We have received reports that some customers are experiencing further issues relating to loading pages within Opsgenie and Jira Service Management which may be related to the infrastructure efforts underway to restore services to these products.

Please be aware we also have teams actively investigating these issues to ensure as fast a resolution as possible.

We want to reiterate that your alerts are still sending notifications correctly, and there is no data loss occurring. However, the underlying issue is affecting the propagation of alert details to notifications, and to the Web and Mobile UI.

Viewing schedules may also be impacted at this time while we continue to process the tasks required for recovery.

We will provide further updates as soon as possible.

Identified: New alerts should still continue to notify users as they are generated, however the alert content will still be missing.

Our teams are still actively engaging with infrastructure teams to try and expedite historical processing of messages to fully restore services.

We will provide further updates within the hour.

Identified: While new alerts should now correctly notify users, the content of those alerts for impacted customers will remain empty until missed alerts are fully processed. Our team is continuing to investigate with urgency potential infrastructure options to expedite this process. We will provide further updates within the hour.

Identified: We are continuing to see recovery of Jira Service Management operations and Opsgenie services. There are a large number of missed alerts to be processed due to the prior service issue and our team is actively investigating methods to help expedite this processing. Alerts should trigger in the meantime but the content of these alerts may not be visible at this time. Our teams are continuing to investigate with urgency. We will provide further updates within the hour.

Identified: Our team has been able to identify the root cause of these performance issues and have put a mitigation into place. We are now continuing to see recovery of Jira Service Management operations and Opsgenie services. Existing alerts are continuing to be processed at this time. We will provide further update as soon as possible.

Identified: Our team is still actively working to resolve the issue and making progress toward a resolution. Thank you for your patience.

Identified: We are continuing to work on a fix for this issue.

Identified: We continue to work on resolving the incident for Jira Service Management and Opsgenie. We have identified the root cause and taken actions to mitigate the issue and minimize the impact on search functionality.

Investigating: We identified degraded performance in web experiences and Alert Rest API for some Jira Service Management and Opsgenie Cloud customers in the US Region. The team has taken actions to mitigate the issue and minimize the impact on search functionality.

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.

Identified: 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.

Identified: 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.

Identified: 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.

Identified: 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.

Identified: 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.

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.

Identified: All concerned teams are engaged and are working to restore full functionality to new alerts to users from Jira Service Management and Opsgenie.

Escalation teams are also engaged on this incident to try and ensure we can get to a resolution as soon as possible.

Currently, the alerts continue to successfully notify users, but without the intended content within the alerts.

We will continue providing specific updates when available and will ensure we have further update within the hour.

Identified: Our teams priority remains to restore full functionality to new alerts to users from Jira Service Management and Opsgenie.

Escalation teams are fully engaged on this incident to try and ensure we can get to a resolution as soon as possible.

At this time these alerts are still successfully notifying users, but without the intended content within the alerts.

We will continue providing specific updates when available and will ensure we have further update within the hour.

Identified: Our infrastructure teams are working diligently to try and ensure all services are restored to Jira Service Management and Opsgenie as soon as possible.

New alerts are continuing to notify users, however we are still prioritising infrastructure to restore the content inside these alerts for Web and Mobile UIs.

We will continue providing updates when available and will ensure we have further update within the hour.

Identified: Our team is continuing to investigate with the highest level of urgency in order to restore Jira Service Management and Opsgenie services.

At this time we are prioritising infrastructure to try and restore new and active alerts to be populated with their alert content as soon as possible, while continuing to deliver existing messages as they are ready.

We will continue to provide updates as we progress, and will ensure we have an update posted within the hour.

Identified: We have received reports that some customers are experiencing further issues relating to loading pages within Opsgenie and Jira Service Management which may be related to the infrastructure efforts underway to restore services to these products.

Please be aware we also have teams actively investigating these issues to ensure as fast a resolution as possible.

We want to reiterate that your alerts are still sending notifications correctly, and there is no data loss occurring. However, the underlying issue is affecting the propagation of alert details to notifications, and to the Web and Mobile UI.

Viewing schedules may also be impacted at this time while we continue to process the tasks required for recovery.

We will provide further updates as soon as possible.

Identified: New alerts should still continue to notify users as they are generated, however the alert content will still be missing.

Our teams are still actively engaging with infrastructure teams to try and expedite historical processing of messages to fully restore services.

We will provide further updates within the hour.

Identified: While new alerts should now correctly notify users, the content of those alerts for impacted customers will remain empty until missed alerts are fully processed. Our team is continuing to investigate with urgency potential infrastructure options to expedite this process. We will provide further updates within the hour.

Identified: We are continuing to see recovery of Jira Service Management operations and Opsgenie services. There are a large number of missed alerts to be processed due to the prior service issue and our team is actively investigating methods to help expedite this processing. Alerts should trigger in the meantime but the content of these alerts may not be visible at this time. Our teams are continuing to investigate with urgency. We will provide further updates within the hour.

Identified: Our team has been able to identify the root cause of these performance issues and have put a mitigation into place. We are now continuing to see recovery of Jira Service Management operations and Opsgenie services. Existing alerts are continuing to be processed at this time. We will provide further update as soon as possible.

Identified: Our team is still actively working to resolve the issue and making progress toward a resolution. Thank you for your patience.

Identified: We are continuing to work on a fix for this issue.

Identified: We continue to work on resolving the incident for Jira Service Management and Opsgenie. We have identified the root cause and taken actions to mitigate the issue and minimize the impact on search functionality.

Investigating: We identified degraded performance in web experiences and Alert Rest API for some Jira Service Management and Opsgenie Cloud customers in the US Region. The team has taken actions to mitigate the issue and minimize the impact on search functionality.

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.

Identified: 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.

Identified: 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.

Identified: 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.

Identified: 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.

Identified: 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.

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.

Identified: All concerned teams are engaged and are working to restore full functionality to new alerts to users from Jira Service Management and Opsgenie.

Escalation teams are also engaged on this incident to try and ensure we can get to a resolution as soon as possible.

Currently, the alerts continue to successfully notify users, but without the intended content within the alerts.

We will continue providing specific updates when available and will ensure we have further update within the hour.

Identified: Our teams priority remains to restore full functionality to new alerts to users from Jira Service Management and Opsgenie.

Escalation teams are fully engaged on this incident to try and ensure we can get to a resolution as soon as possible.

At this time these alerts are still successfully notifying users, but without the intended content within the alerts.

We will continue providing specific updates when available and will ensure we have further update within the hour.

Identified: Our infrastructure teams are working diligently to try and ensure all services are restored to Jira Service Management and Opsgenie as soon as possible.

New alerts are continuing to notify users, however we are still prioritising infrastructure to restore the content inside these alerts for Web and Mobile UIs.

We will continue providing updates when available and will ensure we have further update within the hour.

Identified: Our team is continuing to investigate with the highest level of urgency in order to restore Jira Service Management and Opsgenie services.

At this time we are prioritising infrastructure to try and restore new and active alerts to be populated with their alert content as soon as possible, while continuing to deliver existing messages as they are ready.

We will continue to provide updates as we progress, and will ensure we have an update posted within the hour.

Identified: We have received reports that some customers are experiencing further issues relating to loading pages within Opsgenie and Jira Service Management which may be related to the infrastructure efforts underway to restore services to these products.

Please be aware we also have teams actively investigating these issues to ensure as fast a resolution as possible.

We want to reiterate that your alerts are still sending notifications correctly, and there is no data loss occurring. However, the underlying issue is affecting the propagation of alert details to notifications, and to the Web and Mobile UI.

Viewing schedules may also be impacted at this time while we continue to process the tasks required for recovery.

We will provide further updates as soon as possible.

Identified: New alerts should still continue to notify users as they are generated, however the alert content will still be missing.

Our teams are still actively engaging with infrastructure teams to try and expedite historical processing of messages to fully restore services.

We will provide further updates within the hour.

Identified: While new alerts should now correctly notify users, the content of those alerts for impacted customers will remain empty until missed alerts are fully processed. Our team is continuing to investigate with urgency potential infrastructure options to expedite this process. We will provide further updates within the hour.

Identified: We are continuing to see recovery of Jira Service Management operations and Opsgenie services. There are a large number of missed alerts to be processed due to the prior service issue and our team is actively investigating methods to help expedite this processing. Alerts should trigger in the meantime but the content of these alerts may not be visible at this time. Our teams are continuing to investigate with urgency. We will provide further updates within the hour.

Identified: Our team has been able to identify the root cause of these performance issues and have put a mitigation into place. We are now continuing to see recovery of Jira Service Management operations and Opsgenie services. Existing alerts are continuing to be processed at this time. We will provide further update as soon as possible.

Identified: Our team is still actively working to resolve the issue and making progress toward a resolution. Thank you for your patience.

Identified: We are continuing to work on a fix for this issue.

Identified: We continue to work on resolving the incident for Jira Service Management and Opsgenie. We have identified the root cause and taken actions to mitigate the issue and minimize the impact on search functionality.

Investigating: We identified degraded performance in web experiences and Alert Rest API for some Jira Service Management and Opsgenie Cloud customers in the US Region. The team has taken actions to mitigate the issue and minimize the impact on search functionality.

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.

Identified: 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.

Identified: 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.

Identified: 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.

Identified: 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.

Identified: 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.

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.

Identified: All concerned teams are engaged and are working to restore full functionality to new alerts to users from Jira Service Management and Opsgenie.

Escalation teams are also engaged on this incident to try and ensure we can get to a resolution as soon as possible.

Currently, the alerts continue to successfully notify users, but without the intended content within the alerts.

We will continue providing specific updates when available and will ensure we have further update within the hour.

Identified: Our teams priority remains to restore full functionality to new alerts to users from Jira Service Management and Opsgenie.

Escalation teams are fully engaged on this incident to try and ensure we can get to a resolution as soon as possible.

At this time these alerts are still successfully notifying users, but without the intended content within the alerts.

We will continue providing specific updates when available and will ensure we have further update within the hour.

Identified: Our infrastructure teams are working diligently to try and ensure all services are restored to Jira Service Management and Opsgenie as soon as possible.

New alerts are continuing to notify users, however we are still prioritising infrastructure to restore the content inside these alerts for Web and Mobile UIs.

We will continue providing updates when available and will ensure we have further update within the hour.

Identified: Our team is continuing to investigate with the highest level of urgency in order to restore Jira Service Management and Opsgenie services.

At this time we are prioritising infrastructure to try and restore new and active alerts to be populated with their alert content as soon as possible, while continuing to deliver existing messages as they are ready.

We will continue to provide updates as we progress, and will ensure we have an update posted within the hour.

Identified: We have received reports that some customers are experiencing further issues relating to loading pages within Opsgenie and Jira Service Management which may be related to the infrastructure efforts underway to restore services to these products.

Please be aware we also have teams actively investigating these issues to ensure as fast a resolution as possible.

We want to reiterate that your alerts are still sending notifications correctly, and there is no data loss occurring. However, the underlying issue is affecting the propagation of alert details to notifications, and to the Web and Mobile UI.

Viewing schedules may also be impacted at this time while we continue to process the tasks required for recovery.

We will provide further updates as soon as possible.

Identified: New alerts should still continue to notify users as they are generated, however the alert content will still be missing.

Our teams are still actively engaging with infrastructure teams to try and expedite historical processing of messages to fully restore services.

We will provide further updates within the hour.

Identified: While new alerts should now correctly notify users, the content of those alerts for impacted customers will remain empty until missed alerts are fully processed. Our team is continuing to investigate with urgency potential infrastructure options to expedite this process. We will provide further updates within the hour.

Identified: We are continuing to see recovery of Jira Service Management operations and Opsgenie services. There are a large number of missed alerts to be processed due to the prior service issue and our team is actively investigating methods to help expedite this processing. Alerts should trigger in the meantime but the content of these alerts may not be visible at this time. Our teams are continuing to investigate with urgency. We will provide further updates within the hour.

Identified: Our team has been able to identify the root cause of these performance issues and have put a mitigation into place. We are now continuing to see recovery of Jira Service Management operations and Opsgenie services. Existing alerts are continuing to be processed at this time. We will provide further update as soon as possible.

Identified: Our team is still actively working to resolve the issue and making progress toward a resolution. Thank you for your patience.

Identified: We are continuing to work on a fix for this issue.

Identified: We continue to work on resolving the incident for Jira Service Management and Opsgenie. We have identified the root cause and taken actions to mitigate the issue and minimize the impact on search functionality.

Investigating: We identified degraded performance in web experiences and Alert Rest API for some Jira Service Management and Opsgenie Cloud customers in the US Region. The team has taken actions to mitigate the issue and minimize the impact on search functionality.

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.

Identified: 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.

Identified: 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.

Identified: 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.

Identified: 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.

Identified: 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.

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.

Identified: All concerned teams are engaged and are working to restore full functionality to new alerts to users from Jira Service Management and Opsgenie.

Escalation teams are also engaged on this incident to try and ensure we can get to a resolution as soon as possible.

Currently, the alerts continue to successfully notify users, but without the intended content within the alerts.

We will continue providing specific updates when available and will ensure we have further update within the hour.

Identified: Our teams priority remains to restore full functionality to new alerts to users from Jira Service Management and Opsgenie.

Escalation teams are fully engaged on this incident to try and ensure we can get to a resolution as soon as possible.

At this time these alerts are still successfully notifying users, but without the intended content within the alerts.

We will continue providing specific updates when available and will ensure we have further update within the hour.

Identified: Our infrastructure teams are working diligently to try and ensure all services are restored to Jira Service Management and Opsgenie as soon as possible.

New alerts are continuing to notify users, however we are still prioritising infrastructure to restore the content inside these alerts for Web and Mobile UIs.

We will continue providing updates when available and will ensure we have further update within the hour.

Identified: Our team is continuing to investigate with the highest level of urgency in order to restore Jira Service Management and Opsgenie services.

At this time we are prioritising infrastructure to try and restore new and active alerts to be populated with their alert content as soon as possible, while continuing to deliver existing messages as they are ready.

We will continue to provide updates as we progress, and will ensure we have an update posted within the hour.

Identified: We have received reports that some customers are experiencing further issues relating to loading pages within Opsgenie and Jira Service Management which may be related to the infrastructure efforts underway to restore services to these products.

Please be aware we also have teams actively investigating these issues to ensure as fast a resolution as possible.

We want to reiterate that your alerts are still sending notifications correctly, and there is no data loss occurring. However, the underlying issue is affecting the propagation of alert details to notifications, and to the Web and Mobile UI.

Viewing schedules may also be impacted at this time while we continue to process the tasks required for recovery.

We will provide further updates as soon as possible.

Identified: New alerts should still continue to notify users as they are generated, however the alert content will still be missing.

Our teams are still actively engaging with infrastructure teams to try and expedite historical processing of messages to fully restore services.

We will provide further updates within the hour.

Identified: While new alerts should now correctly notify users, the content of those alerts for impacted customers will remain empty until missed alerts are fully processed. Our team is continuing to investigate with urgency potential infrastructure options to expedite this process. We will provide further updates within the hour.

Identified: We are continuing to see recovery of Jira Service Management operations and Opsgenie services. There are a large number of missed alerts to be processed due to the prior service issue and our team is actively investigating methods to help expedite this processing. Alerts should trigger in the meantime but the content of these alerts may not be visible at this time. Our teams are continuing to investigate with urgency. We will provide further updates within the hour.

Identified: Our team has been able to identify the root cause of these performance issues and have put a mitigation into place. We are now continuing to see recovery of Jira Service Management operations and Opsgenie services. Existing alerts are continuing to be processed at this time. We will provide further update as soon as possible.

Identified: Our team is still actively working to resolve the issue and making progress toward a resolution. Thank you for your patience.

Identified: We are continuing to work on a fix for this issue.

Identified: We continue to work on resolving the incident for Jira Service Management and Opsgenie. We have identified the root cause and taken actions to mitigate the issue and minimize the impact on search functionality.

Investigating: We identified degraded performance in web experiences and Alert Rest API for some Jira Service Management and Opsgenie Cloud customers in the US Region. The team has taken actions to mitigate the issue and minimize the impact on search functionality.

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.

Identified: 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.

Identified: 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.

Identified: 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.

Identified: 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.

Identified: 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.

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.

Identified: All concerned teams are engaged and are working to restore full functionality to new alerts to users from Jira Service Management and Opsgenie.

Escalation teams are also engaged on this incident to try and ensure we can get to a resolution as soon as possible.

Currently, the alerts continue to successfully notify users, but without the intended content within the alerts.

We will continue providing specific updates when available and will ensure we have further update within the hour.

Identified: Our teams priority remains to restore full functionality to new alerts to users from Jira Service Management and Opsgenie.

Escalation teams are fully engaged on this incident to try and ensure we can get to a resolution as soon as possible.

At this time these alerts are still successfully notifying users, but without the intended content within the alerts.

We will continue providing specific updates when available and will ensure we have further update within the hour.

Identified: Our infrastructure teams are working diligently to try and ensure all services are restored to Jira Service Management and Opsgenie as soon as possible.

New alerts are continuing to notify users, however we are still prioritising infrastructure to restore the content inside these alerts for Web and Mobile UIs.

We will continue providing updates when available and will ensure we have further update within the hour.

Identified: Our team is continuing to investigate with the highest level of urgency in order to restore Jira Service Management and Opsgenie services.

At this time we are prioritising infrastructure to try and restore new and active alerts to be populated with their alert content as soon as possible, while continuing to deliver existing messages as they are ready.

We will continue to provide updates as we progress, and will ensure we have an update posted within the hour.

Identified: We have received reports that some customers are experiencing further issues relating to loading pages within Opsgenie and Jira Service Management which may be related to the infrastructure efforts underway to restore services to these products.

Please be aware we also have teams actively investigating these issues to ensure as fast a resolution as possible.

We want to reiterate that your alerts are still sending notifications correctly, and there is no data loss occurring. However, the underlying issue is affecting the propagation of alert details to notifications, and to the Web and Mobile UI.

Viewing schedules may also be impacted at this time while we continue to process the tasks required for recovery.

We will provide further updates as soon as possible.

Identified: New alerts should still continue to notify users as they are generated, however the alert content will still be missing.

Our teams are still actively engaging with infrastructure teams to try and expedite historical processing of messages to fully restore services.

We will provide further updates within the hour.

Identified: While new alerts should now correctly notify users, the content of those alerts for impacted customers will remain empty until missed alerts are fully processed. Our team is continuing to investigate with urgency potential infrastructure options to expedite this process. We will provide further updates within the hour.

Identified: We are continuing to see recovery of Jira Service Management operations and Opsgenie services. There are a large number of missed alerts to be processed due to the prior service issue and our team is actively investigating methods to help expedite this processing. Alerts should trigger in the meantime but the content of these alerts may not be visible at this time. Our teams are continuing to investigate with urgency. We will provide further updates within the hour.

Identified: Our team has been able to identify the root cause of these performance issues and have put a mitigation into place. We are now continuing to see recovery of Jira Service Management operations and Opsgenie services. Existing alerts are continuing to be processed at this time. We will provide further update as soon as possible.

Identified: Our team is still actively working to resolve the issue and making progress toward a resolution. Thank you for your patience.

Identified: We are continuing to work on a fix for this issue.

Identified: We continue to work on resolving the incident for Jira Service Management and Opsgenie. We have identified the root cause and taken actions to mitigate the issue and minimize the impact on search functionality.

Investigating: We identified degraded performance in web experiences and Alert Rest API for some Jira Service Management and Opsgenie Cloud customers in the US Region. The team has taken actions to mitigate the issue and minimize the impact on search functionality.

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.

Identified: 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.

Identified: 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.

Identified: 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.

Identified: 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.

Identified: 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.

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.

Identified: All concerned teams are engaged and are working to restore full functionality to new alerts to users from Jira Service Management and Opsgenie.

Escalation teams are also engaged on this incident to try and ensure we can get to a resolution as soon as possible.

Currently, the alerts continue to successfully notify users, but without the intended content within the alerts.

We will continue providing specific updates when available and will ensure we have further update within the hour.

Identified: Our teams priority remains to restore full functionality to new alerts to users from Jira Service Management and Opsgenie.

Escalation teams are fully engaged on this incident to try and ensure we can get to a resolution as soon as possible.

At this time these alerts are still successfully notifying users, but without the intended content within the alerts.

We will continue providing specific updates when available and will ensure we have further update within the hour.

Identified: Our infrastructure teams are working diligently to try and ensure all services are restored to Jira Service Management and Opsgenie as soon as possible.

New alerts are continuing to notify users, however we are still prioritising infrastructure to restore the content inside these alerts for Web and Mobile UIs.

We will continue providing updates when available and will ensure we have further update within the hour.

Identified: Our team is continuing to investigate with the highest level of urgency in order to restore Jira Service Management and Opsgenie services.

At this time we are prioritising infrastructure to try and restore new and active alerts to be populated with their alert content as soon as possible, while continuing to deliver existing messages as they are ready.

We will continue to provide updates as we progress, and will ensure we have an update posted within the hour.

Identified: We have received reports that some customers are experiencing further issues relating to loading pages within Opsgenie and Jira Service Management which may be related to the infrastructure efforts underway to restore services to these products.

Please be aware we also have teams actively investigating these issues to ensure as fast a resolution as possible.

We want to reiterate that your alerts are still sending notifications correctly, and there is no data loss occurring. However, the underlying issue is affecting the propagation of alert details to notifications, and to the Web and Mobile UI.

Viewing schedules may also be impacted at this time while we continue to process the tasks required for recovery.

We will provide further updates as soon as possible.

Identified: New alerts should still continue to notify users as they are generated, however the alert content will still be missing.

Our teams are still actively engaging with infrastructure teams to try and expedite historical processing of messages to fully restore services.

We will provide further updates within the hour.

Identified: While new alerts should now correctly notify users, the content of those alerts for impacted customers will remain empty until missed alerts are fully processed. Our team is continuing to investigate with urgency potential infrastructure options to expedite this process. We will provide further updates within the hour.

Identified: We are continuing to see recovery of Jira Service Management operations and Opsgenie services. There are a large number of missed alerts to be processed due to the prior service issue and our team is actively investigating methods to help expedite this processing. Alerts should trigger in the meantime but the content of these alerts may not be visible at this time. Our teams are continuing to investigate with urgency. We will provide further updates within the hour.

Identified: Our team has been able to identify the root cause of these performance issues and have put a mitigation into place. We are now continuing to see recovery of Jira Service Management operations and Opsgenie services. Existing alerts are continuing to be processed at this time. We will provide further update as soon as possible.

Identified: Our team is still actively working to resolve the issue and making progress toward a resolution. Thank you for your patience.

Identified: We are continuing to work on a fix for this issue.

Identified: We continue to work on resolving the incident for Jira Service Management and Opsgenie. We have identified the root cause and taken actions to mitigate the issue and minimize the impact on search functionality.

Investigating: We identified degraded performance in web experiences and Alert Rest API for some Jira Service Management and Opsgenie Cloud customers in the US Region. The team has taken actions to mitigate the issue and minimize the impact on search functionality.

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.

Identified: 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.

Identified: 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.

Identified: 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.

Identified: 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.

Identified: 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.

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.

Identified: All concerned teams are engaged and are working to restore full functionality to new alerts to users from Jira Service Management and Opsgenie.

Escalation teams are also engaged on this incident to try and ensure we can get to a resolution as soon as possible.

Currently, the alerts continue to successfully notify users, but without the intended content within the alerts.

We will continue providing specific updates when available and will ensure we have further update within the hour.

Identified: Our teams priority remains to restore full functionality to new alerts to users from Jira Service Management and Opsgenie.

Escalation teams are fully engaged on this incident to try and ensure we can get to a resolution as soon as possible.

At this time these alerts are still successfully notifying users, but without the intended content within the alerts.

We will continue providing specific updates when available and will ensure we have further update within the hour.

Identified: Our infrastructure teams are working diligently to try and ensure all services are restored to Jira Service Management and Opsgenie as soon as possible.

New alerts are continuing to notify users, however we are still prioritising infrastructure to restore the content inside these alerts for Web and Mobile UIs.

We will continue providing updates when available and will ensure we have further update within the hour.

Identified: Our team is continuing to investigate with the highest level of urgency in order to restore Jira Service Management and Opsgenie services.

At this time we are prioritising infrastructure to try and restore new and active alerts to be populated with their alert content as soon as possible, while continuing to deliver existing messages as they are ready.

We will continue to provide updates as we progress, and will ensure we have an update posted within the hour.

Identified: We have received reports that some customers are experiencing further issues relating to loading pages within Opsgenie and Jira Service Management which may be related to the infrastructure efforts underway to restore services to these products.

Please be aware we also have teams actively investigating these issues to ensure as fast a resolution as possible.

We want to reiterate that your alerts are still sending notifications correctly, and there is no data loss occurring. However, the underlying issue is affecting the propagation of alert details to notifications, and to the Web and Mobile UI.

Viewing schedules may also be impacted at this time while we continue to process the tasks required for recovery.

We will provide further updates as soon as possible.

Identified: New alerts should still continue to notify users as they are generated, however the alert content will still be missing.

Our teams are still actively engaging with infrastructure teams to try and expedite historical processing of messages to fully restore services.

We will provide further updates within the hour.

Identified: While new alerts should now correctly notify users, the content of those alerts for impacted customers will remain empty until missed alerts are fully processed. Our team is continuing to investigate with urgency potential infrastructure options to expedite this process. We will provide further updates within the hour.

Identified: We are continuing to see recovery of Jira Service Management operations and Opsgenie services. There are a large number of missed alerts to be processed due to the prior service issue and our team is actively investigating methods to help expedite this processing. Alerts should trigger in the meantime but the content of these alerts may not be visible at this time. Our teams are continuing to investigate with urgency. We will provide further updates within the hour.

Identified: Our team has been able to identify the root cause of these performance issues and have put a mitigation into place. We are now continuing to see recovery of Jira Service Management operations and Opsgenie services. Existing alerts are continuing to be processed at this time. We will provide further update as soon as possible.

Identified: Our team is still actively working to resolve the issue and making progress toward a resolution. Thank you for your patience.

Identified: We are continuing to work on a fix for this issue.

Identified: We continue to work on resolving the incident for Jira Service Management and Opsgenie. We have identified the root cause and taken actions to mitigate the issue and minimize the impact on search functionality.

Investigating: We identified degraded performance in web experiences and Alert Rest API for some Jira Service Management and Opsgenie Cloud customers in the US Region. The team has taken actions to mitigate the issue and minimize the impact on search functionality.

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.

Identified: 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.

Identified: 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.

Identified: 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.

Identified: 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.

Identified: 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.

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.

Identified: All concerned teams are engaged and are working to restore full functionality to new alerts to users from Jira Service Management and Opsgenie.

Escalation teams are also engaged on this incident to try and ensure we can get to a resolution as soon as possible.

Currently, the alerts continue to successfully notify users, but without the intended content within the alerts.

We will continue providing specific updates when available and will ensure we have further update within the hour.

Identified: Our teams priority remains to restore full functionality to new alerts to users from Jira Service Management and Opsgenie.

Escalation teams are fully engaged on this incident to try and ensure we can get to a resolution as soon as possible.

At this time these alerts are still successfully notifying users, but without the intended content within the alerts.

We will continue providing specific updates when available and will ensure we have further update within the hour.

Identified: Our infrastructure teams are working diligently to try and ensure all services are restored to Jira Service Management and Opsgenie as soon as possible.

New alerts are continuing to notify users, however we are still prioritising infrastructure to restore the content inside these alerts for Web and Mobile UIs.

We will continue providing updates when available and will ensure we have further update within the hour.

Identified: Our team is continuing to investigate with the highest level of urgency in order to restore Jira Service Management and Opsgenie services.

At this time we are prioritising infrastructure to try and restore new and active alerts to be populated with their alert content as soon as possible, while continuing to deliver existing messages as they are ready.

We will continue to provide updates as we progress, and will ensure we have an update posted within the hour.

Identified: We have received reports that some customers are experiencing further issues relating to loading pages within Opsgenie and Jira Service Management which may be related to the infrastructure efforts underway to restore services to these products.

Please be aware we also have teams actively investigating these issues to ensure as fast a resolution as possible.

We want to reiterate that your alerts are still sending notifications correctly, and there is no data loss occurring. However, the underlying issue is affecting the propagation of alert details to notifications, and to the Web and Mobile UI.

Viewing schedules may also be impacted at this time while we continue to process the tasks required for recovery.

We will provide further updates as soon as possible.

Identified: New alerts should still continue to notify users as they are generated, however the alert content will still be missing.

Our teams are still actively engaging with infrastructure teams to try and expedite historical processing of messages to fully restore services.

We will provide further updates within the hour.

Identified: While new alerts should now correctly notify users, the content of those alerts for impacted customers will remain empty until missed alerts are fully processed. Our team is continuing to investigate with urgency potential infrastructure options to expedite this process. We will provide further updates within the hour.

Identified: We are continuing to see recovery of Jira Service Management operations and Opsgenie services. There are a large number of missed alerts to be processed due to the prior service issue and our team is actively investigating methods to help expedite this processing. Alerts should trigger in the meantime but the content of these alerts may not be visible at this time. Our teams are continuing to investigate with urgency. We will provide further updates within the hour.

Identified: Our team has been able to identify the root cause of these performance issues and have put a mitigation into place. We are now continuing to see recovery of Jira Service Management operations and Opsgenie services. Existing alerts are continuing to be processed at this time. We will provide further update as soon as possible.

Identified: Our team is still actively working to resolve the issue and making progress toward a resolution. Thank you for your patience.

Identified: We are continuing to work on a fix for this issue.

Identified: We continue to work on resolving the incident for Jira Service Management and Opsgenie. We have identified the root cause and taken actions to mitigate the issue and minimize the impact on search functionality.

Investigating: We identified degraded performance in web experiences and Alert Rest API for some Jira Service Management and Opsgenie Cloud customers in the US Region. The team has taken actions to mitigate the issue and minimize the impact on search functionality.

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.

Identified: 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.

Identified: 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.

Identified: 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.

Identified: 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.

Identified: 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.

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.

Identified: All concerned teams are engaged and are working to restore full functionality to new alerts to users from Jira Service Management and Opsgenie.

Escalation teams are also engaged on this incident to try and ensure we can get to a resolution as soon as possible.

Currently, the alerts continue to successfully notify users, but without the intended content within the alerts.

We will continue providing specific updates when available and will ensure we have further update within the hour.

Identified: Our teams priority remains to restore full functionality to new alerts to users from Jira Service Management and Opsgenie.

Escalation teams are fully engaged on this incident to try and ensure we can get to a resolution as soon as possible.

At this time these alerts are still successfully notifying users, but without the intended content within the alerts.

We will continue providing specific updates when available and will ensure we have further update within the hour.

Identified: Our infrastructure teams are working diligently to try and ensure all services are restored to Jira Service Management and Opsgenie as soon as possible.

New alerts are continuing to notify users, however we are still prioritising infrastructure to restore the content inside these alerts for Web and Mobile UIs.

We will continue providing updates when available and will ensure we have further update within the hour.

Identified: Our team is continuing to investigate with the highest level of urgency in order to restore Jira Service Management and Opsgenie services.

At this time we are prioritising infrastructure to try and restore new and active alerts to be populated with their alert content as soon as possible, while continuing to deliver existing messages as they are ready.

We will continue to provide updates as we progress, and will ensure we have an update posted within the hour.

Identified: We have received reports that some customers are experiencing further issues relating to loading pages within Opsgenie and Jira Service Management which may be related to the infrastructure efforts underway to restore services to these products.

Please be aware we also have teams actively investigating these issues to ensure as fast a resolution as possible.

We want to reiterate that your alerts are still sending notifications correctly, and there is no data loss occurring. However, the underlying issue is affecting the propagation of alert details to notifications, and to the Web and Mobile UI.

Viewing schedules may also be impacted at this time while we continue to process the tasks required for recovery.

We will provide further updates as soon as possible.

Identified: New alerts should still continue to notify users as they are generated, however the alert content will still be missing.

Our teams are still actively engaging with infrastructure teams to try and expedite historical processing of messages to fully restore services.

We will provide further updates within the hour.

Identified: While new alerts should now correctly notify users, the content of those alerts for impacted customers will remain empty until missed alerts are fully processed. Our team is continuing to investigate with urgency potential infrastructure options to expedite this process. We will provide further updates within the hour.

Identified: We are continuing to see recovery of Jira Service Management operations and Opsgenie services. There are a large number of missed alerts to be processed due to the prior service issue and our team is actively investigating methods to help expedite this processing. Alerts should trigger in the meantime but the content of these alerts may not be visible at this time. Our teams are continuing to investigate with urgency. We will provide further updates within the hour.

Identified: Our team has been able to identify the root cause of these performance issues and have put a mitigation into place. We are now continuing to see recovery of Jira Service Management operations and Opsgenie services. Existing alerts are continuing to be processed at this time. We will provide further update as soon as possible.

Identified: Our team is still actively working to resolve the issue and making progress toward a resolution. Thank you for your patience.

Identified: We are continuing to work on a fix for this issue.

Identified: We continue to work on resolving the incident for Jira Service Management and Opsgenie. We have identified the root cause and taken actions to mitigate the issue and minimize the impact on search functionality.

Investigating: We identified degraded performance in web experiences and Alert Rest API for some Jira Service Management and Opsgenie Cloud customers in the US Region. The team has taken actions to mitigate the issue and minimize the impact on search functionality.

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.

Identified: 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.

Identified: 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.

Identified: 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.

Identified: 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.

Identified: 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.

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.

Identified: All concerned teams are engaged and are working to restore full functionality to new alerts to users from Jira Service Management and Opsgenie.

Escalation teams are also engaged on this incident to try and ensure we can get to a resolution as soon as possible.

Currently, the alerts continue to successfully notify users, but without the intended content within the alerts.

We will continue providing specific updates when available and will ensure we have further update within the hour.

Identified: Our teams priority remains to restore full functionality to new alerts to users from Jira Service Management and Opsgenie.

Escalation teams are fully engaged on this incident to try and ensure we can get to a resolution as soon as possible.

At this time these alerts are still successfully notifying users, but without the intended content within the alerts.

We will continue providing specific updates when available and will ensure we have further update within the hour.

Identified: Our infrastructure teams are working diligently to try and ensure all services are restored to Jira Service Management and Opsgenie as soon as possible.

New alerts are continuing to notify users, however we are still prioritising infrastructure to restore the content inside these alerts for Web and Mobile UIs.

We will continue providing updates when available and will ensure we have further update within the hour.

Identified: Our team is continuing to investigate with the highest level of urgency in order to restore Jira Service Management and Opsgenie services.

At this time we are prioritising infrastructure to try and restore new and active alerts to be populated with their alert content as soon as possible, while continuing to deliver existing messages as they are ready.

We will continue to provide updates as we progress, and will ensure we have an update posted within the hour.

Identified: We have received reports that some customers are experiencing further issues relating to loading pages within Opsgenie and Jira Service Management which may be related to the infrastructure efforts underway to restore services to these products.

Please be aware we also have teams actively investigating these issues to ensure as fast a resolution as possible.

We want to reiterate that your alerts are still sending notifications correctly, and there is no data loss occurring. However, the underlying issue is affecting the propagation of alert details to notifications, and to the Web and Mobile UI.

Viewing schedules may also be impacted at this time while we continue to process the tasks required for recovery.

We will provide further updates as soon as possible.

Identified: New alerts should still continue to notify users as they are generated, however the alert content will still be missing.

Our teams are still actively engaging with infrastructure teams to try and expedite historical processing of messages to fully restore services.

We will provide further updates within the hour.

Identified: While new alerts should now correctly notify users, the content of those alerts for impacted customers will remain empty until missed alerts are fully processed. Our team is continuing to investigate with urgency potential infrastructure options to expedite this process. We will provide further updates within the hour.

Identified: We are continuing to see recovery of Jira Service Management operations and Opsgenie services. There are a large number of missed alerts to be processed due to the prior service issue and our team is actively investigating methods to help expedite this processing. Alerts should trigger in the meantime but the content of these alerts may not be visible at this time. Our teams are continuing to investigate with urgency. We will provide further updates within the hour.

Identified: Our team has been able to identify the root cause of these performance issues and have put a mitigation into place. We are now continuing to see recovery of Jira Service Management operations and Opsgenie services. Existing alerts are continuing to be processed at this time. We will provide further update as soon as possible.

Identified: Our team is still actively working to resolve the issue and making progress toward a resolution. Thank you for your patience.

Identified: We are continuing to work on a fix for this issue.

Identified: We continue to work on resolving the incident for Jira Service Management and Opsgenie. We have identified the root cause and taken actions to mitigate the issue and minimize the impact on search functionality.

Investigating: We identified degraded performance in web experiences and Alert Rest API for some Jira Service Management and Opsgenie Cloud customers in the US Region. The team has taken actions to mitigate the issue and minimize the impact on search functionality.

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.

Identified: 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.

Identified: 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.

Identified: 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.