- Level
- confirmed
- Worst impact
- Degraded
- Regions
- us
What to do
Check whether you use Opsgenie in us. 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 0m it lasted.
Anything that failed between 2024-12-16 17:18 UTC and 2024-12-16 15:30 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 1
- resolved
Our team has identified the issue in Schedule API between 15:30 UTC and 17:00 UTC. We saw performance degradation and 5XX errors in response. Faulty deployment has been reverted quickly in the USA region and rapid recovery is seen. We are monitoring the system for a full recovery right now. The Schedule API is up and running again without any data loss.
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-907943280a
Is Opsgenie still down?
No, this incident was resolved 2024-12-16 15:30 UTC. For Opsgenie's live state, see https://down.guide/opsgenie.
How long did it last?
0m, from 2024-12-16 17:18 UTC to 2024-12-16 15:30 UTC, by the times Opsgenie posted.
What was affected?
Opsgenie named in us.
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.