Disrupted Opsgenie/JSM availability
Affected: Web ApplicationWeb ApplicationMobile ApplicationMobile Application
OpsGenie Outage History
OpsGenie is up right nowOpsGenie had 13 outages in the last 2 years totaling 296h 59m of downtime — averaging 0.5 incidents per month.
There were 13 OpsGenie outages since November 6, 2024 totaling 296h 59m of downtime. Each is summarised below — incident details, duration, and resolution information.
Issues with Microsoft Teams notifications for Opsgenie customers
Affected: Outgoing Integration FlowOutgoing Integration Flow
Timeline · 6 updates
- identified Aug 27, 2026, 10:26 AM UTC
On August 19, 2026, we identified an issue affecting the delivery of Microsoft Teams notifications for Opsgenie standalone customers. The root cause has been identified and our teams are working with our partners to resolve this issue. This issue does not impact Jira Service Management Operations customers. We will provide the next update in 24 hours.
- identified Aug 28, 2026, 10:38 AM UTC
Our teams continue to work with our partners towards resolving the Microsoft Teams notification delivery issue for Opsgenie standalone customers. We will provide the next update in 72 hours or sooner if we have a material update.
- identified Aug 31, 2026, 10:29 AM UTC
Our teams continue to work with our partners, towards resolving the Microsoft Teams notification delivery issue for Opsgenie standalone customers. We will provide the next update in 24 hours, or sooner if there is a significant update.
- identified Sep 01, 2026, 10:16 AM UTC
Our teams continue to work with our partners towards resolving the Microsoft Teams notification delivery issue for Opsgenie standalone customers. We will provide the next update in 24 hours, or sooner if there is a significant update.
- identified Sep 02, 2026, 10:17 AM UTC
Our teams continue to work with our partners towards resolving the Microsoft Teams notification delivery issue for Opsgenie standalone customers. We will provide the next update in 24 hours, or sooner if there is a significant update.
- resolved Sep 03, 2026, 06:06 AM UTC
On August 19, we identified an issue affecting the delivery of Microsoft Teams notifications for Opsgenie standalone customers. The root cause was attributed to an operational error caused by our external partner, and they have taken corrective measures to restore services. If you are still experiencing issues, please follow these steps to restore your integration: https://support.atlassian.com/opsgenie/docs/restore-the-opsgenie-microsoft-teams-v2-integration/. If you require further assistance, please reach out to Atlassian Support via support.atlassian.com/contact.
Voice call failures for some India based numbers
Affected: Incident FlowIncident FlowAlert FlowAlert FlowEmail Notification DeliveryEmail Notification DeliveryPublic WebsiteSMS Notification DeliverySMS Notification DeliveryVoice Notification DeliveryVoice Notification DeliveryMobile Notification DeliveryMobile Notification DeliveryHeartbeat MonitoringHeartbeat MonitoringIncident REST APIIncident REST APIAlert REST APIAlert REST APIHeartbeat REST APIHeartbeat REST APIIncoming Email ServiceIncoming Email ServiceIncoming Integration FlowIncoming Integration FlowOutgoing Integration FlowOutgoing Integration FlowSignup, Login & AuthorizationSignup, Login & AuthorizationOpsgenie ActionsOpsgenie ActionsWeb ApplicationWeb ApplicationMobile ApplicationMobile ApplicationConfiguration REST APIsConfiguration REST APIsReporting & AnalyticsReporting & AnalyticsPricing & BillingPricing & BillingLogsLogsIncoming Call RoutingIncoming Call Routing
Timeline · 3 updates
- identified Jul 21, 2026, 09:48 AM UTC
We are working with our notification provider to resolve the issue. We will provide another update in 24 hours or as soon as more information becomes available.
- identified Jul 22, 2026, 06:59 AM UTC
A small number of voice notifications for Jira Service Management and Opsgenie customers using India based mobile numbers may fail. Customers may see failed voice call logs and not receive the expected paging call. Our 3rd party notification provider is actively working towards restoring the voice notification delivery and we will provide updates once the issue is resolved. If you need any further support or information, please reach out to our support team.
- resolved Jul 24, 2026, 01:07 PM UTC
Our notification provider has identified the root of the issue that is causing voice call failures to some India-based mobile numbers. We understand the inconvenience this may cause and appreciate your patience while our provider works on restoring the service. If you have experienced any issues with voice notifications, please contact our Support for assistance.
Atlassian Cloud Services impacted
Affected: Incident FlowIncident FlowAlert FlowAlert FlowEmail Notification DeliveryEmail Notification DeliveryPublic WebsiteSMS Notification DeliverySMS Notification DeliveryVoice Notification DeliveryVoice Notification DeliveryMobile Notification DeliveryMobile Notification DeliveryHeartbeat MonitoringHeartbeat MonitoringIncident REST APIIncident REST APIAlert REST APIAlert REST APIHeartbeat REST APIHeartbeat REST APIIncoming Email ServiceIncoming Email ServiceIncoming Integration FlowIncoming Integration FlowOutgoing Integration FlowOutgoing Integration FlowSignup, Login & AuthorizationSignup, Login & AuthorizationOpsgenie ActionsOpsgenie ActionsWeb ApplicationWeb ApplicationMobile ApplicationMobile ApplicationConfiguration REST APIsConfiguration REST APIsReporting & AnalyticsReporting & AnalyticsPricing & BillingPricing & BillingLogsLogsIncoming Call RoutingIncoming Call Routing
Timeline · 25 updates
Delays in Opsgenie, JSM Ops and Compass Ops notifications
Affected: Email Notification DeliverySMS Notification DeliveryVoice Notification DeliveryMobile Notification Delivery
Timeline · 4 updates
- investigating Sep 30, 2025, 02:07 PM UTC
We are observing delays in Opsgenie, JSM ops and Compass ops notification flows. No alert has been lost and our team is actively working on it to mitigate the delays. We'll keep you posted with further updates.
- identified Sep 30, 2025, 02:09 PM UTC
We continue to work on resolving the notification delays for Jira Service Management, Opsgenie, and Compass. We have identified the root cause and expect recovery shortly.
- monitoring Sep 30, 2025, 02:22 PM UTC
We have identified the root cause of the notification delay for Opsgenie, JSM Ops and Compass Ops and have mitigated the problem. We are now monitoring closely.
- resolved Sep 30, 2025, 02:32 PM UTC
Between 13:10 UTC to 14:00 UTC, we experienced notification delay for Jira Service Management, Opsgenie, and Compass in only EU-region. The issue has been resolved and the service is operating normally.
Delays observed at JSM, Opsgenie and Compass alert search functionality in US Region
Affected: Incident FlowIncident FlowAlert FlowAlert FlowEmail Notification DeliveryEmail Notification DeliveryPublic WebsiteSMS Notification DeliverySMS Notification DeliveryVoice Notification DeliveryVoice Notification DeliveryMobile Notification DeliveryMobile Notification DeliveryHeartbeat MonitoringHeartbeat MonitoringIncident REST APIIncident REST APIAlert REST APIAlert REST APIHeartbeat REST APIHeartbeat REST APIIncoming Email ServiceIncoming Email ServiceIncoming Integration FlowIncoming Integration FlowOutgoing Integration FlowOutgoing Integration FlowSignup, Login & AuthorizationSignup, Login & AuthorizationOpsgenie ActionsOpsgenie ActionsWeb ApplicationWeb ApplicationMobile ApplicationMobile ApplicationConfiguration REST APIsConfiguration REST APIsReporting & AnalyticsReporting & AnalyticsPricing & BillingPricing & BillingLogsLogsIncoming Call RoutingIncoming Call Routing
Timeline · 22 updates
Degraded performance in Opsgenie and JSM operations
Timeline · 3 updates
- investigating Jun 19, 2025, 03:21 PM UTC
We are investigating degraded performance issues in Jira Service Management, Opsgenie, and Compass Cloud customers. We will provide more details within the next hour.
- monitoring Jun 19, 2025, 03:42 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jun 19, 2025, 04:37 PM UTC
This incident has been resolved.
Delays observed at JSM and Opsgenie alert search functionality
Affected: Web Application
Timeline · 3 updates
- identified May 10, 2025, 07:08 AM UTC
We identified degraded performance at alert search functionality for some Jira Service Management and Opsgenie Cloud customers due to the infrastructure issue from cloud provider. No impact has been observed at alert critical flows like notification. The team has taken actions to mitigate the issue and minimize the impact to search functionality
- monitoring May 10, 2025, 09:49 AM UTC
The problem is mitigated, and we are now monitoring closely.
- resolved May 10, 2025, 10:51 AM UTC
All search functionality is operational without any latency. Thank you for your patience.
Schedule API are getting timed out
Timeline · 2 updates
- investigating Apr 04, 2025, 10:05 AM UTC
We are investigating cases of degraded performance for Alert Schedules experiencing timeouts and slowness for Opsgenie Cloud customers. Requests have been taking more than 30s and some have been timing out. We will provide more details within the next hour.
- resolved Apr 04, 2025, 10:52 AM UTC
This incident has been resolved.
EU OpsGenie API calls having intermittent routing issues
Affected: Alert Flow
Timeline · 2 updates
- investigating Mar 05, 2025, 06:34 AM UTC
We are aware of an issue where some API calls configured to use api.opsgenie.com/eu are intermittently returning a 404 error with the message 'no Route matched with those values'. API calls to api.eu.opsgenie.com and api.opsgenie.com (without /eu) are not affected. Our team is investigating this issue.
- resolved Mar 05, 2025, 07:24 AM UTC
Issues where some API calls configured to use api.opsgenie.com/eu were intermittently returning a 404 error with the message 'no Route matched with those values' should now be resolved. API calls to api.eu.opsgenie.com and api.opsgenie.com (without /eu) were not affected at this time.
Services menu in Opsgenie is not responding
Timeline · 3 updates
- investigating Jan 14, 2025, 03:48 PM UTC
Our engineering team is actively investigating this incident and working to bring the Opsgenie service back up as quickly as possible. Users affected by this incident may notice that Services functionality is slow or completely unavailable for the web page We will update this page as we have additional information.
- identified Jan 14, 2025, 03:55 PM UTC
Our team has identified the issue with the Services page in Opsgenie and is working to fix it.
- resolved Jan 14, 2025, 04:47 PM UTC
Our engineers have been closely monitoring the platform and are declaring this incident resolved. Thank you for your patience.
Elevated 5XX errors in Schedule API at Opsgenie USA region
Timeline · 1 update
- resolved Dec 16, 2024, 05:18 PM UTC
Our team has identified the issue in Schedule API between 15:30 UTC and 17:00 UTC. We saw performance degradation and 5XX errors in response. Faulty deployment has been reverted quickly in the USA region and rapid recovery is seen. We are monitoring the system for a full recovery right now. The Schedule API is up and running again without any data loss.
Opsgenie Web UI is slow or unavailable in US region
Affected: Web Application
Timeline · 3 updates
- investigating Nov 06, 2024, 07:47 PM UTC
We've noticed that Opsgenie Web UI is responding slowly or unavailable in US region. Our engineering team is actively investigating this incident and working to bring Opsgenie back up to speed as quickly as possible. We'll keep you posted with further updates on this page.
- monitoring Nov 06, 2024, 07:49 PM UTC
Our engineering team has implemented fixes. We will continue to monitor all systems. Thank you for your patience.
- resolved Nov 06, 2024, 07:59 PM UTC
Our engineers have been closely monitoring the platform and are declaring this incident resolved. Thank you for your patience.