Logz.io: Indexing and API degradation for some of the customers in the Frankfurt region
Timeline of updates
- resolved
Almost all customers now have recent logs, last few are catching up quickly.
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: minor) posted by Logz.io, started 2019-06-14 22:02 UTC, resolved after 11 h, 1 update(s).
- Title
- Indexing and API degradation for some of the customers in the Frankfurt region
- Vendor
- Logz.io
- Date
- URL
- https://rewindex.com/company/logz-io/incidents/mhvsjnb644jr
Logz.io profileRecent Logz.io incidentsAll outages on June 14, 2019Logz.io in June 2019MarkdownJSON