- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Outgoing Integration Flow, Outgoing Integration Flow
- Down Index
- 34of 100
What to do
Check whether you use Opsgenie Outgoing Integration Flow, Outgoing Integration Flow. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 6d 19h it lasted.
Anything that failed between 2026-08-27 10:26 UTC and 2026-09-03 06:06 UTC may need a replay.Subscribe to Opsgenie's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=opsgenie works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Opsgenie 6
- identified
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.
provider
- identified
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.
provider
- identified
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.
provider
- identified
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.
provider
- identified
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.
provider
- resolved
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.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-9da660deaa
Is Opsgenie still down?
No, this incident was resolved 2026-09-03 06:06 UTC. For Opsgenie's live state, see https://down.guide/opsgenie.
How long did it last?
6d 19h, from 2026-08-27 10:26 UTC to 2026-09-03 06:06 UTC, by the times Opsgenie posted.
What was affected?
Opsgenie named Outgoing Integration Flow, Outgoing Integration Flow.
What caused it?
Opsgenie hasn't published a root cause. If it does, it shows here.
Where does this come from?
Opsgenie's official status page, https://opsgenie.status.atlassian.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.