- Level
- confirmed
- Worst impact
- Degraded
- Components
- Metrics Ingestion
- Regions
- eu, eu-central-1
- Down Index
- 24of 100
What to do
Check whether you use Logz.io Metrics Ingestion in eu, eu-central-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 31m it lasted.
Anything that failed between 2025-10-10 00:04 UTC and 2025-10-10 00:35 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 have detected an issue that may affect some of our customers in our eu-central-1 service, and we are working to identify the cause and take the appropriate steps to remediate it.
provider
- identified
We found out what was causing the problem, and have started working on a solution
provider
- resolved
The issue that affected some customers in our eu-central-1 service is resolved. All systems are operational.
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-ff4b947d01
Is Logz.io still down?
No, this incident was resolved 2025-10-10 00:35 UTC. For Logz.io's live state, see https://down.guide/logzio.
How long did it last?
31m, from 2025-10-10 00:04 UTC to 2025-10-10 00:35 UTC, by the times Logz.io posted.
What was affected?
Logz.io named Metrics Ingestion in eu, eu-central-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.