- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Account Usage
- Down Index
- 35of 100
What to do
Check whether you use Loggly Account Usage. 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 20h 36m it lasted.
Anything that failed between 2024-07-24 16:56 UTC and 2024-07-25 13:32 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 6
- investigating
We experienced an issue with our volume data reporting service and are working on restoring it.
provider
- identified
The issue has been identified and a fix is being implemented.
provider
- identified
A fix is still being implemented and the next update will be 06:00 UTC
provider
- monitoring
A fix has been implemented and we are monitoring the results.
provider
- monitoring
We are continuing to monitor.
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-9a88fe7245
Is Loggly still down?
No, this incident was resolved 2024-07-25 13:32 UTC. For Loggly's live state, see https://down.guide/providers/loggly.
How long did it last?
20h 36m, from 2024-07-24 16:56 UTC to 2024-07-25 13:32 UTC, by the times Loggly posted.
What was affected?
Loggly named Account Usage.
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.