Lever: Incident with AWS
AWS outage, Sep 28, 2022 · 16 vendors, 16 incidents
Lever’s incident blames AWS as the cause. (hop 1, posted +1 h 56 min vs the first vendor naming AWS)
“…Incident with AWS AWS has confirmed that the issue they have experienced has been resolved. More information on the incident can be found here https://health.aws.amazon.com/health/status. We’ll contin…”
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, 3 blamed AWS<br/>Daily, Unbounce, Gusto"]:::blames
root --> h1
h4["1 to 4 hours later<br/>3 vendors, 3 blamed AWS<br/>Lever, Jira, Confluence"]:::blames
root --> h4
me["Lever (this incident)<br/>posted +1 h 56 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
AWS has confirmed that the issue they have experienced has been resolved. More information on the incident can be found here https://health.aws.amazon.com/health/status. We’ll continue monitoring for any residual impact in Lever, and send an update if there are any major issues that we continue to see.
From Lever’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.lever.co (opens in new tab).