- Level
- confirmed
- Worst impact
- Degraded
- Regions
- eu
- Down Index
- 12of 100
What to do
Check whether you use Logz.io in eu. 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 0m it lasted.
Anything that failed between 2025-12-18 09:30 UTC and 2025-12-18 08:00 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 1
- resolved
We have detected an issue that may affect some of our customers, and we are working to identify the cause and take the appropriate steps to remediate it.
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-6235b81970
Is Logz.io still down?
No, this incident was resolved 2025-12-18 08:00 UTC. For Logz.io's live state, see https://down.guide/logzio.
How long did it last?
0m, from 2025-12-18 09:30 UTC to 2025-12-18 08:00 UTC, by the times Logz.io posted.
What was affected?
Logz.io named in eu.
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.