Skip to main content
Logz.io

Some Customers Experiencing Lag for Rolled Up Metrics: eu-central-1

Degraded Lasted 1h 9m · started · Logz.io's page

Level
confirmed
Worst impact
Degraded
Components
Metrics Ingestion
Regions
eu, eu-central-1
Down Index
26of 100

What to do

  • Check whether you use Logz.io Metrics Ingestion in eu, eu-central-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 1h 9m it lasted.

    Anything that failed between 2026-03-30 13:21 UTC and 2026-03-30 14:30 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 2

  1. investigating

    We are currently investigating this issue.

    provider

  2. 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-d65af8b0f6

Is Logz.io still down?

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

How long did it last?

1h 9m, from 2026-03-30 13:21 UTC to 2026-03-30 14:30 UTC, by the times Logz.io posted.

What was affected?

Logz.io named Metrics Ingestion in eu, eu-central-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.