- Level
- confirmed
- Worst impact
- Degraded
- Components
- Alerts
- Down Index
- 20of 100
What to do
Check whether you use Loggly Alerts. 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 1h 14m it lasted.
Anything that failed between 2026-05-11 21:06 UTC and 2026-05-11 22:21 UTC may need a replay.Subscribe to Loggly's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=loggly works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Loggly 2
- monitoring
At 5:46 AM PDT we started experiencing delays in our alerting system caused by a network provider issue. The issue is resolved and we are monitoring the recovery.
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-0361ee7b90
Is Loggly still down?
No, this incident was resolved 2026-05-11 22:21 UTC. For Loggly's live state, see https://down.guide/loggly.
How long did it last?
1h 14m, from 2026-05-11 21:06 UTC to 2026-05-11 22:21 UTC, by the times Loggly posted.
What was affected?
Loggly named Alerts.
What caused it?
Loggly hasn't published a root cause. If it does, it shows here.
Where does this come from?
Loggly's official status page, https://status.loggly.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.