Confluent: AWS us-east-1 provisioning affected by AWS outage
AWS outage, Nov 25, 2020 · 28 vendors, 29 incidents
Confluent’s incident blames AWS as the cause. (hop 1, posted +7 h 23 min vs the first vendor naming AWS)
“…AWS us-east-1 provisioning affected by AWS outage Even though AWS is still recovering from the incident, the system that were affecting our provisioning have recovered. Pending clusters in AWS in us-e…”
Swipe sideways to see the whole diagram.
Mermaid source
flowchart LR
root["AWS<br/>own incident not archived"]:::inferred
h1["Within an hour<br/>1 vendor, 1 blamed AWS<br/>Pipedream"]:::blames
root --> h1
h4["1 to 4 hours later<br/>4 vendors, 4 blamed AWS<br/>HubSpot, Xero, Lattice, Heap"]:::blames
root --> h4
later["Later<br/>2 vendors, 2 blamed AWS<br/>Confluent, Pipedream"]:::blames
root --> later
me["Confluent (this incident)<br/>posted +7 h 23 min"]:::me
later --- 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
Even though AWS is still recovering from the incident, the system that were affecting our provisioning have recovered. Pending clusters in AWS in us-east-1 region have now been provisioned.
From Confluent’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Impact, status and times are the vendor’s own, as last archived. View on status.confluent.cloud (opens in new tab).