- Level
- confirmed
- Worst impact
- Degraded
- Components
- S3 Ingestion
- Down Index
- 19of 100
What to do
Check whether you use Loggly S3 Ingestion. 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 45m it lasted.
Anything that failed between 2024-10-16 12:35 UTC and 2024-10-16 13:20 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
We are currently investigating this issue.
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-1989434d16
Is Loggly still down?
No, this incident was resolved 2024-10-16 13:20 UTC. For Loggly's live state, see https://down.guide/loggly.
How long did it last?
45m, from 2024-10-16 12:35 UTC to 2024-10-16 13:20 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.