- Level
- confirmed
- Worst impact
- Degraded
- Regions
- us
- Down Index
- 27of 100
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 1d it lasted.
Anything that failed between 2022-10-20 09:00 UTC and 2022-10-21 09:00 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
Between 2022-10-21 09:01 UTC and 2022-10-21 09:12 UTC, in the US region, we started to see elevated error rate in our infrastructure due to faulty deployment. We have deployed a fix to mitigate the issue and have verified that all services have recovered without data loss. Thanks to quick reaction of our engineering team, issue has been resolved and the service is operating normally.
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-bd27e79956
Is Opsgenie still down?
No, this incident was resolved 2022-10-21 09:00 UTC. For Opsgenie's live state, see https://down.guide/opsgenie.
How long did it last?
1d, from 2022-10-20 09:00 UTC to 2022-10-21 09:00 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.