- 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 59m it lasted.
Anything that failed between 2025-01-14 15:48 UTC and 2025-01-14 16: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
Our engineering team is actively investigating this incident and working to bring the Opsgenie service back up as quickly as possible. Users affected by this incident may notice that Services functionality is slow or completely unavailable for the web page We will update this page as we have additional information.
provider
- identified
Our team has identified the issue with the Services page in Opsgenie and is working to fix it.
provider
- resolved
Our engineers have been closely monitoring the platform and are declaring this incident resolved. Thank you for your patience.
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-fd1342776e
Is Opsgenie still down?
No, this incident was resolved 2025-01-14 16:47 UTC. For Opsgenie's live state, see https://down.guide/providers/opsgenie.
How long did it last?
59m, from 2025-01-14 15:48 UTC to 2025-01-14 16: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.