Gusto: Some users are experiencing errors within their Gusto account.
AWS outage, Jun 13, 2023 · 56 vendors, 56 incidents
Gusto’s incident started in the same window without naming AWS (timing only, not evidence of a link). (timing only, posted +1 h 59 min vs the first vendor naming AWS)
Swipe sideways to see the whole diagram.
Mermaid source
flowchart LR
root["AWS<br/>own incident not archived"]:::inferred
h1["Within an hour<br/>13 vendors, 13 blamed AWS<br/>Pipedream, Wiz, Temporal Cloud +10"]:::blames
root --> h1
h4["1 to 4 hours later<br/>7 vendors, 6 blamed AWS<br/>CockroachDB, Vanta, Asana +4"]:::blames
root --> h4
me["Gusto (this incident)<br/>posted +1 h 59 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.
Affected components: AWS apigateway-us-east-1Provider: AWS - AWS apigateway-us-east-1
Timeline of updates
- identified
The issue has been identified and a fix is being implemented.
- 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
dff0c025d99c6429…
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).