Skip to main content
Logz.io

Ongoing AWS us-east Outage Impacting Metrics and Logs Ingestion

Degraded Lasted 13h 8m · started · Logz.io's page

Level
confirmed
Worst impact
Degraded
Components
Alerts & Security rules, Logs Ingestion
Regions
us
Down Index
27of 100

What to do

  • Check whether you use Logz.io Alerts & Security rules, 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 13h 8m it lasted.

    Anything that failed between 2025-10-20 07:30 UTC and 2025-10-20 20:38 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 4

  1. monitoring

    We're currently experiencing delays in metrics and logs ingestion due to an AWS outage in the us-east region. Our team is monitoring AWS Health status and will provide updates once the issue is resolved. We're still working to recover from the AWS outage, and our development team is actively addressing the remaining impact. Please note that some backfilled metrics and logs may be missing after the outage is resolved, and you may also experience some latency during the recovery process.

    provider

  2. monitoring

    We are continuing to monitor for any further issues.

    provider

  3. monitoring

    We are continuing to monitor for any further issues.

    provider

  4. resolved

    This incident has been resolved.

    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-56c8b62eb8

Is Logz.io still down?

No, this incident was resolved 2025-10-20 20:38 UTC. For Logz.io's live state, see https://down.guide/logzio.

How long did it last?

13h 8m, from 2025-10-20 07:30 UTC to 2025-10-20 20:38 UTC, by the times Logz.io posted.

What was affected?

Logz.io named Alerts & Security rules, 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.