Logz.io: Initial reports of problems
AWS us-east-1 outage, Dec 7, 2021 · 71 vendors, 77 incidents
Logz.io’s incident started in the same window without naming AWS (timing only, not evidence of a link). (hop 1, posted +32 min vs the first vendor naming AWS)
“…As we continue to monitor the situation, we are not seeing any impact on our service, and AWS are reporting progress towards resolution. If our service is impacted again we will reopen the incident. W…”
Swipe sideways to see the whole diagram.
Mermaid source
flowchart LR
root["AWS us-east-1<br/>own incident not archived"]:::inferred
h1["Within an hour<br/>11 vendors, 9 blamed AWS<br/>Aptible, Firebolt, Honeycomb +8"]:::blames
root --> h1
h4["1 to 4 hours later<br/>16 vendors, 12 blamed AWS<br/>Maven Central, Pusher, Confluent +13"]:::blames
root --> h4
later["Later<br/>3 vendors, 2 blamed AWS<br/>Segment, Confluent, Doppler"]:::blames
root --> later
me["Logz.io (this incident)<br/>posted +32 min"]:::me
root -.->|"same window"| meFull event: timeline, evidence and all vendors →
Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.
Timeline of updates
- resolved
As we continue to monitor the situation, we are not seeing any impact on our service, and AWS are reporting progress towards resolution. If our service is impacted again we will reopen the incident. We are still monitoring the progress.
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).