- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 13of 100
What to do
Check whether your product depends on Opsgenie. 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 10m it lasted.
Anything that failed between 2025-06-17 12:37 UTC and 2025-06-17 12:47 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 cases of degraded performance for some Jira Service Management and Opsgenie Cloud customers. We will provide more details within the next hour.
provider
- monitoring
We have identified the root cause of the performance degraded service and have mitigated the problem. We are now monitoring closely.
provider
- resolved
This incident has been resolved, and Jira Service Management and Opsgenie are back in operational mode.
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-1f6a0daa70
Is Opsgenie still down?
No, this incident was resolved 2025-06-17 12:47 UTC. For Opsgenie's live state, see https://down.guide/opsgenie.
How long did it last?
10m, from 2025-06-17 12:37 UTC to 2025-06-17 12:47 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.