Front: Degraded performance in us-west-2 [us-west-2]
AWS outage, Aug 29, 2024 · 14 vendors, 14 incidents
Front’s incident names AWS (location or integration). (hop 1, posted +43 min vs the first vendor naming AWS)
“…Degraded performance in us-west-2 [us-west-2] This incident has been resolved. This incident has been resolved. We are experiencing issues launching new deployments in our us-west-2 region, which may…”
Swipe sideways to see the whole diagram.
Mermaid source
flowchart LR
root["AWS<br/>own incident not archived"]:::inferred
h1["Within an hour<br/>3 vendors, 1 blamed AWS<br/>Segment, Ably, Front"]:::blames
root --> h1
h4["1 to 4 hours later<br/>2 vendors, 1 blamed AWS<br/>Confluent, Semgrep"]:::blames
root --> h4
me["Front (this incident)<br/>posted +43 min"]:::me
h1 --- 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.
Affected components: App
Timeline of updates
- investigating
We are experiencing issues launching new deployments in our us-west-2 region, which may degrade the app performance and lead to delays in receiving messages for some customers.
- monitoring
We're beginning to see new deployments coming online. We're continuing to monitor the health of the cluster.
- 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 18:22 UTC
In the 2026-10-17 checkpoint, timestamped by FreeTSA and DigiCert on Oct 19, 23:18 UTC. Record hash
0167a55fe818963b…
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).