- Level
- confirmed
- Worst impact
- Degraded
- Components
- Logs Ingestion
- Regions
- us, us-east-1
- Down Index
- 26of 100
What to do
Check whether you use Logz.io Logs Ingestion in us, us-east-1. 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 11m it lasted.
Anything that failed between 2025-10-22 13:41 UTC and 2025-10-22 14:52 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
We’re currently investigating an issue affecting log ingestion in the US-East-1 region. Some customers may experience delays in incoming log data. Our engineering team is actively working to identify the cause and fix the issue. We’ll provide updates as soon as more information becomes available.
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-4c7ea3c7eb
Is Logz.io still down?
No, this incident was resolved 2025-10-22 14:52 UTC. For Logz.io's live state, see https://down.guide/logzio.
How long did it last?
1h 11m, from 2025-10-22 13:41 UTC to 2025-10-22 14:52 UTC, by the times Logz.io posted.
What was affected?
Logz.io named Logs Ingestion in us, us-east-1.
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.