outages.live
Live

Opsgenie

Opsgenie is operational

Checked 32 s ago Operational

History

90 days agoToday

Incidents in 90 days

2

Days with an incident

9

Median duration

3 days

Longest incident

7 days

Components

45

US

Incident Flow Operational
90 days agoNo incidentsToday
Alert Flow Operational
90 days agoNo incidentsToday
Email Notification Delivery Operational
90 days agoNo incidentsToday
SMS Notification Delivery Operational
90 days agoNo incidentsToday
Voice Notification Delivery Operational
90 days agoNo incidentsToday
Mobile Notification Delivery Operational
90 days agoNo incidentsToday
Heartbeat Monitoring Operational
90 days agoNo incidentsToday
Incident REST API Operational
90 days agoNo incidentsToday
Alert REST API Operational
90 days agoNo incidentsToday
Heartbeat REST API Operational
90 days agoNo incidentsToday
Incoming Email Service Operational
90 days agoNo incidentsToday
Incoming Integration Flow Operational
90 days agoNo incidentsToday
Outgoing Integration Flow Operational
90 days ago8 days with an incidentToday
Signup, Login & Authorization Operational
90 days agoNo incidentsToday
Opsgenie Actions Operational
90 days agoNo incidentsToday
Web Application Operational
90 days ago1 day with an incidentToday
Mobile Application Operational
90 days ago1 day with an incidentToday
Configuration REST APIs Operational
90 days agoNo incidentsToday
Reporting & Analytics Operational
90 days agoNo incidentsToday
Pricing & Billing Operational
90 days agoNo incidentsToday
Logs Operational
90 days agoNo incidentsToday
Incoming Call Routing Operational
90 days agoNo incidentsToday

EU

Incident Flow Operational
90 days agoNo incidentsToday
Alert Flow Operational
90 days agoNo incidentsToday

Past incidents

Provider status pageTimes in UTC

Sep 14, 2026

Duration57 min16:46 to 17:43Disrupted Opsgenie/JSM availabilityMajor outage

### Summary On September 14, 2026, between 15:30 and 17:10 UTC, Atlassian customers using Opsgenie, Jira Service Management, and Compass experienced delays in receiving alert notifications and intermittent failures when using Ops features. The issue was triggered by long-running transactions in a core service, which led to thread pool exhaustion and caused subsequent requests to become unresponsive. The long-running transactions were caused by a configuration change released between September 9, 2026 and September 11, 2026 UTC. The team actively monitored the impact of the change on the system until early September 14, 2026 UTC, and observed no anomalies. However, increasing traffic during US working hours on September 14, 2026, caused these unexpectedly long-running transactions. The incident was detected within one minute by our automated monitoring systems, and full service stabilization occurred after isolating and rolling back the change on September 14, 2026 at 17:10 UTC. ### IMP

Aug 27, 2026

Duration7 days10:26 to 06:06Issues with Microsoft Teams notifications for Opsgenie customersPartial outage

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.

Follow Opsgenie

Your coding agent knows when Opsgenie is down, and tells you when a failure is theirs, not yours. You can also get Opsgenie incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "opsgenie" and tell me if Opsgenie has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.cc/feed.xml?providers=opsgenie
Slack
/feed subscribe https://outages.cc/feed.xml?providers=opsgenie

Go from tracking outages to fixing production issues with Polylane.

Try Polylane