- Level
- confirmed
- Worst impact
- Degraded
- Components
- Logs, Logs
- Down Index
- 24of 100
What to do
Check whether you use Opsgenie Logs, Logs. 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 3d 18h it lasted.
Anything that failed between 2023-01-13 11:52 UTC and 2023-01-17 06:18 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 4
- investigating
We have identified that "_incomingData" and "_actionSource" fields are missing in Opsgenie Debug Logs due to internal issues.
provider
- identified
We have identified the problem and worked on the solution to fix debug logs now.
provider
- monitoring
"_incomingData" and "_actionSource" fields are visible in debug logs generated after January 13, 2023 1:55:39 PM UTC
provider
- resolved
This incident has been resolved.
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-6e2565f21c
Is Opsgenie still down?
No, this incident was resolved 2023-01-17 06:18 UTC. For Opsgenie's live state, see https://down.guide/opsgenie.
How long did it last?
3d 18h, from 2023-01-13 11:52 UTC to 2023-01-17 06:18 UTC, by the times Opsgenie posted.
What was affected?
Opsgenie named Logs, Logs.
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.