- Level
- confirmed
- Worst impact
- Degraded
- Components
- Logs Ingestion
- Regions
- us
What to do
Check whether you use Logz.io Logs Ingestion in us. 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 1h 17m it lasted.
Anything that failed between 2025-12-02 20:58 UTC and 2025-12-02 22:15 UTC may need a replay.Subscribe to Logz.io's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=logzio works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Logz.io 2
- 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-0705672fc3
Is Logz.io still down?
No, this incident was resolved 2025-12-02 22:15 UTC. For Logz.io's live state, see https://down.guide/logzio.
How long did it last?
1h 17m, from 2025-12-02 20:58 UTC to 2025-12-02 22:15 UTC, by the times Logz.io posted.
What was affected?
Logz.io named Logs Ingestion in us.
What caused it?
Logz.io hasn't published a root cause. If it does, it shows here.
Where does this come from?
Logz.io's official status page, https://status.logz.io, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.