- Level
- confirmed
- Worst impact
- Degraded
- Components
- Incident Flow, Incident Flow
- Down Index
- 16of 100
What to do
Check whether you use Opsgenie Incident Flow, Incident Flow. 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 23m it lasted.
Anything that failed between 2023-04-06 14:45 UTC and 2023-04-06 15:07 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 2
- identified
The problem is related to a misconfiguration on our network causing ICC sessions to fail. We are working on a fix and adjusting our network. Incident flow is continue to work without a problem and there is no data loss. We appreciate your patience as our teams continue with our investigations into the service interruption
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-44a28a13ba
Is Opsgenie still down?
No, this incident was resolved 2023-04-06 15:07 UTC. For Opsgenie's live state, see https://down.guide/opsgenie.
How long did it last?
23m, from 2023-04-06 14:45 UTC to 2023-04-06 15:07 UTC, by the times Opsgenie posted.
What was affected?
Opsgenie named Incident Flow, Incident Flow.
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.