outages.live
Live
OpsgenieIncident · 2026-08-27 10:26 UTC

Issues with Microsoft Teams notifications for Opsgenie customers

ResolvedOfficial update

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.

The latest update from Opsgenie.

State

Resolved

Started

66 d ago

2026-08-27 10:26 UTC

Lasted

7 days

until 2026-09-03 06:06 UTC

Worst impact

Partial outage

Timeline

6 updates
Aug 27Aug 29Aug 30Sep 1Sep 3
Partial outageUpdate postedDates in UTC

Identified

7 days 100%

Updates

Times in UTC

As posted by Opsgenie

Resolved2026-09-03 06:06 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.

Identified2026-09-02 10:17 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.

Identified2026-09-01 10:16 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.

Identified2026-08-31 10:29 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.

Identified2026-08-28 10:38 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.

Identified2026-08-27 10:26 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.

Affected components

3
Outgoing Integration FlowUS - Outgoing Integration FlowEU - Outgoing Integration Flow

Opsgenie in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

2

Days with an incident

9

Median duration

3 days

This incident

2.0× the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

7 days
median 3 days
90 days agoToday

Other Opsgenie incidents

All incidents

Opsgenie·Disrupted Opsgenie/JSM availability

### 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

Resolvedresolved 48 d ago

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

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane