- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Incident Flow, Incident Flow, Alert Flow, Alert Flow, Email Notification Delivery, Email Notification Delivery, Public Website, SMS Notification Delivery, SMS Notification Delivery, Voice Notification Delivery, Voice Notification Delivery, Mobile Notification Delivery, Mobile Notification Delivery
- Down Index
- 36of 100
What to do
Check whether you use Opsgenie Incident Flow, Incident Flow, Alert Flow, Alert Flow and 9 more. 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 3h 45m it lasted.
Anything that failed between 2024-07-03 20:51 UTC and 2024-07-04 00:36 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 issue with that is impacting Atlassian, Atlassian Partners, Atlassian Support, Confluence, Jira Work Management, Jira Service Management, Jira, Opsgenie, Atlassian Developer, Atlassian (deprecated), Trello, Atlassian Bitbucket, Guard, Jira Align, Jira Product Discovery, Atlas, Atlassian Analytics, and Rovo Cloud customers. We will provide more details within the next hour.
provider
- monitoring
We have mitigated the problem and continue looking into the root cause. The outage was between 8:08pm 03/07 UTC - 08:31pm 03/07 UTC We are now monitoring closely.
provider
- resolved
Between 03-07-2024 20:08 UTC to 03-07-2024 20:31 UTC, we experienced downtime for Opsgenie. 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-049102f303
Is Opsgenie still down?
No, this incident was resolved 2024-07-04 00:36 UTC. For Opsgenie's live state, see https://down.guide/opsgenie.
How long did it last?
3h 45m, from 2024-07-03 20:51 UTC to 2024-07-04 00:36 UTC, by the times Opsgenie posted.
What was affected?
Opsgenie named Incident Flow, Incident Flow, Alert Flow, Alert Flow and 9 more.
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.