Logz.io: Degraded Log Ingestion
Affected components: AWS N. Virginia (us-east-1) - Logs IngestionLogs Ingestion
Timeline of updates
- investigating
We are currently experiencing reduced log ingestion rates in Us-east
Our team is actively investigating and working to restore full performance - investigating
We are continuing to investigate this issue.
- resolved
This incident has been resolved.
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. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-10-17 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
25b07afe9cbe4f31…
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by Logz.io, started 2026-03-27 07:58 UTC, resolved after 59 min, 3 update(s).
- Title
- Degraded Log Ingestion
- Vendor
- Logz.io
- Date
- URL
- https://rewindex.com/company/logz-io/incidents/06x5c0yvzsyv
Logz.io profileRecent Logz.io incidentsAll outages on March 27, 2026Logz.io in March 2026MarkdownJSON