- 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 2h 30m it lasted.
Anything that failed between 2024-06-21 00:17 UTC and 2024-06-21 02: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 an intermittent issue with accessing Atlassian Cloud services that is impacting some Atlassian Cloud customers. We will provide more details once we identify the root cause.
provider
- monitoring
We have identified the root cause of the intermittent errors and have mitigated the problem. We are now monitoring closely.
provider
- resolved
Between 2024-06-20 22:04 UTC to 2024-06-20 22:28 UTC, we experienced intermittent issue for users to access the services for some Atlassian Cloud customers. The 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-c49667922f
Is Opsgenie still down?
No, this incident was resolved 2024-06-21 02:47 UTC. For Opsgenie's live state, see https://down.guide/providers/opsgenie.
How long did it last?
2h 30m, from 2024-06-21 00:17 UTC to 2024-06-21 02: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.