Logz.io: Some Customers Experiencing Degraded Performance for Metrics

What to do

Check whether you use Logz.io Metrics Ingestion. 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 4h 53m it lasted.
Anything that failed between 2026-01-05 19:06 UTC and 2026-01-05 23:59 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.

identifiedJan 5, 2026, 7:06 PM UTC
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
monitoringJan 5, 2026, 8:54 PM UTC
A fix has been implemented and we are monitoring the results.
provider
resolvedJan 5, 2026, 11:59 PM UTC
This incident has been resolved.
provider

Reports count in aggregate; nothing about you is shown.

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Is Logz.io still down?

No, this incident was resolved 2026-01-05 23:59 UTC. For Logz.io's live state, see https://down.guide/logzio.

How long did it last?

4h 53m, from 2026-01-05 19:06 UTC to 2026-01-05 23:59 UTC, by the times Logz.io posted.

What was affected?

Logz.io named Metrics Ingestion.

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.