- Level
- confirmed
- Worst impact
- Degraded
- Components
- S3 Ingestion
- Down Index
- 25of 100
What to do
Check whether you use Loggly S3 Ingestion. 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 10h 8m it lasted.
Anything that failed between 2022-05-25 08:20 UTC and 2022-05-25 18:28 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
Our data processing infrastructure is running behind which is causing search delays from S3 sources.
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-922ad3b5f1
Is Loggly still down?
No, this incident was resolved 2022-05-25 18:28 UTC. For Loggly's live state, see https://down.guide/providers/loggly.
How long did it last?
10h 8m, from 2022-05-25 08:20 UTC to 2022-05-25 18:28 UTC, by the times Loggly posted.
What was affected?
Loggly named S3 Ingestion.
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.