- Level
- confirmed
- Worst impact
- Degraded
- Components
- Indexing Data
- Down Index
- 21of 100
What to do
Check whether you use Loggly Indexing Data. 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 2h 1m it lasted.
Anything that failed between 2021-12-22 12:43 UTC and 2021-12-22 14:43 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 4
- investigating
Our engineers have identified an issue with log ingestion starting at 4:11AM PST. We are investigating.
provider
- identified
The issue has been identified and a fix is being implemented.
provider
- monitoring
A fix has been implemented and we are monitoring the results.
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-d0effdfd24
Is Loggly still down?
No, this incident was resolved 2021-12-22 14:43 UTC. For Loggly's live state, see https://down.guide/loggly.
How long did it last?
2h 1m, from 2021-12-22 12:43 UTC to 2021-12-22 14:43 UTC, by the times Loggly posted.
What was affected?
Loggly named Indexing Data.
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.