Logz.io: Some Customers In us-east-1 Are Experiencing Data Ingestions Delays - Degraded Performance - Identified

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 40m it lasted.
Anything that failed between 2025-12-04 12:45 UTC and 2025-12-04 13:24 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.

identifiedDec 4, 2025, 12:45 PM UTC
We are currently experiencing a data ingestion outage in us-east-1. This is resulting in delays and potential data lag for some affected customers. Our engineering team is working on getting this resolved as soon as possible.
provider
monitoringDec 4, 2025, 12:58 PM UTC
A fix has been implemented and we are monitoring the results.
provider
resolvedDec 4, 2025, 1:24 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 2025-12-04 13:24 UTC. For Logz.io's live state, see https://down.guide/logzio.

How long did it last?

40m, from 2025-12-04 12:45 UTC to 2025-12-04 13:24 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.