- Level
- confirmed
- Worst impact
- Operational
What to do
Check whether your product depends on Opsgenie. Check your stack
Drop a package.json, lockfile, Terraform or a list of domains at down.guide to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 1h 16m it lasted.
Anything that failed between 2025-06-19 15:21 UTC and 2025-06-19 16:37 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 3
- investigating
We are investigating degraded performance issues in Jira Service Management, Opsgenie, and Compass Cloud customers. We will provide more details within the next hour.
provider
- monitoring
A fix has been implemented and we are monitoring the results.
provider
- resolved
This incident has been resolved.
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-9fdc5129d2
Is Opsgenie still down?
No, this incident was resolved 2025-06-19 16:37 UTC. For Opsgenie's live state, see https://down.guide/providers/opsgenie.
How long did it last?
1h 16m, from 2025-06-19 15:21 UTC to 2025-06-19 16:37 UTC, by the times Opsgenie posted.
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.