Skip to main content
Logz.io

Some Customers Experiencing Metrics Latency on us-east-1

Degraded Lasted 4h 19m · started · Logz.io's page

Level
confirmed
Worst impact
Degraded
Components
Metrics Ingestion, Metrics Visualizations and Dashboards
Regions
us, us-east-1
Down Index
29of 100

What to do

  • Check whether you use Logz.io Metrics Ingestion, Metrics Visualizations and Dashboards 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 4h 19m it lasted.

    Anything that failed between 2026-03-03 16:16 UTC and 2026-03-03 20:35 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 3

  1. investigating

    We are currently investigating this issue.

    provider

  2. identified

    The issue has been identified and a fix is being implemented.

    provider

  3. 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-0319827042

Is Logz.io still down?

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

How long did it last?

4h 19m, from 2026-03-03 16:16 UTC to 2026-03-03 20:35 UTC, by the times Logz.io posted.

What was affected?

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