Lever: Offers stuck in sending
AWS us-east-1 outage, Dec 7, 2021 · 71 vendors, 77 incidents
Lever’s incident started in the same window without naming AWS (timing only, not evidence of a link). (timing only, posted +3 h 17 min vs the first vendor naming AWS)
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["Lever (this incident)<br/>posted +3 h 17 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.
Timeline of updates
- resolved
The issue where there was an intermittent issue of offer being stuck in "sending" has been resolved . The incident occurred from around 10:20AM PST to around 12PM PST. There should be no further impact at this time, but please reach out to us at Support if any additional assistance is needed: https://help.lever.co/hc/en-us/requests/new
From Lever’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.lever.co (opens in new tab).