Logz.io: US-East - Data Ingestions Delays Due to AWS outage for Some Customers - Degraded Performance

What to do

Check whether you use Logz.io Logs Visualizations and Dashboards, Logs Ingestion 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 7h 10m it lasted.
Anything that failed between 2026-05-08 00:53 UTC and 2026-05-08 08:03 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.

investigatingMay 8, 2026, 12:53 AM UTC
We are currently investigating this issue.
provider
identifiedMay 8, 2026, 2:40 AM UTC
The issue has been identified and a fix is being implemented.
provider
identifiedMay 8, 2026, 4:58 AM UTC
Mitigation efforts are currently underway. Customers should begin to see gradual improvement shortly while we continue monitoring and working toward full resolution.
provider
resolvedMay 8, 2026, 8:03 AM 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-05-08 08:03 UTC. For Logz.io's live state, see https://down.guide/logzio.

How long did it last?

7h 10m, from 2026-05-08 00:53 UTC to 2026-05-08 08:03 UTC, by the times Logz.io posted.

What was affected?

Logz.io named Logs Visualizations and Dashboards, Logs Ingestion 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.