- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Indexing Data
- Down Index
- 35of 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 3d 13h it lasted.
Anything that failed between 2021-04-22 17:38 UTC and 2021-04-26 07:02 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 3
- investigating
We have identified an issue with processing some data predominantly sent via Snap Agent to Loggly. All incoming data continues to be received and stored. Our engineers are implementing a fix, in the meantime processing of problematic logs is delayed and they won't be searchable until the issue is resolved.
provider
- identified
The issue has been identified and a fix is being implemented.
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-d185a25eec
Is Loggly still down?
No, this incident was resolved 2021-04-26 07:02 UTC. For Loggly's live state, see https://down.guide/loggly.
How long did it last?
3d 13h, from 2021-04-22 17:38 UTC to 2021-04-26 07:02 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.