Courier: Ongoing AWS Outage
AWS us-east-1 outage, Dec 7, 2021 · 71 vendors, 77 incidents
Courier’s incident blames AWS as the cause. (hop 1, posted +1 h 51 min vs the first vendor naming AWS)
“…Ongoing AWS Outage Our API is processing messages again and appears to be healthy. We're continuing to monitor the AWS status page: https://status.aws.amazon.com/…”
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["Courier (this incident)<br/>posted +1 h 51 min"]:::me
h4 --- 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
Our API is processing messages again and appears to be healthy. We're continuing to monitor the AWS status page: https://status.aws.amazon.com/
From Courier’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.courier.com (opens in new tab).