Skip to main content
Logz.io

Logs Utilization Metrics Showing Inconsistent Values for Some Accounts

Degraded Lasted 15m · started · Logz.io's page

Level
confirmed
Worst impact
Degraded
Components
Logs Visualizations and Dashboards
Down Index
14of 100

What to do

  • Check whether you use Logz.io Logs Visualizations and Dashboards. 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 15m it lasted.

    Anything that failed between 2025-07-07 15:34 UTC and 2025-07-07 15:49 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. identified

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

    provider

  2. monitoring

    The issue has been mitigated. Accounts that were suspended due to inconsistent values in the utilization metrics are unsuspended now and any lost data will be restored

    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-552d2ab7e3

Is Logz.io still down?

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

How long did it last?

15m, from 2025-07-07 15:34 UTC to 2025-07-07 15:49 UTC, by the times Logz.io posted.

What was affected?

Logz.io named Logs Visualizations and Dashboards.

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.