Logz.io: Some Accounts in AWS US-East Region are Experiencing Log Ingestion Lag

What to do

Check whether you use Logz.io in us. 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-07-15 20:58 UTC and 2025-07-15 18: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.

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-07-15 18:00 UTC. For Logz.io's live state, see https://down.guide/logzio.

How long did it last?

0m, from 2025-07-15 20:58 UTC to 2025-07-15 18:00 UTC, by the times Logz.io posted.

What was affected?

Logz.io named in us.

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.