- Level
- confirmed
- Worst impact
- Degraded
- Components
- Logs Ingestion, Logs Ingestion
- Regions
- ap-northeast-1
- Down Index
- 17of 100
What to do
Check whether you use Logz.io Logs Ingestion, Logs Ingestion in ap-northeast-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 8m it lasted.
Anything that failed between 2026-01-29 13:38 UTC and 2026-01-29 13:46 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 3
- investigating
We are currently investigating this issue.
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-8044623c06
Is Logz.io still down?
No, this incident was resolved 2026-01-29 13:46 UTC. For Logz.io's live state, see https://down.guide/logzio.
How long did it last?
8m, from 2026-01-29 13:38 UTC to 2026-01-29 13:46 UTC, by the times Logz.io posted.
What was affected?
Logz.io named Logs Ingestion, Logs Ingestion in ap-northeast-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.