rewindex

CompaniesLogz.ioIncidents

Logz.io: High error rate on accessing data

No impact listedStatus: resolvedStarted Resolved (12 min)1 updatestatus.logz.io (opens in new tab)

Timeline of updates

  1. resolved

    This turn out to be a false alarm, everything is normal.

From Logz.io’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.

How the archive is checked, and what it cannot prove.

This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.

Impact, status and times are the vendor’s own, as last archived. View on status.logz.io (opens in new tab).

Cite this

Status incident (vendor impact label: none) posted by Logz.io, started 2016-06-19 04:26 UTC, resolved after 12 min, 1 update(s).

Title
High error rate on accessing data
Vendor
Logz.io
Date
URL
https://rewindex.com/company/logz-io/incidents/sb41ynxmz28x

Logz.io profileRecent Logz.io incidentsAll outages on June 19, 2016Logz.io in June 2016MarkdownJSON