Vanta: Subset of AWS related tests showing inaccurate test results
AWS outage, Sep 18, 2023 · 29 vendors, 29 incidents
Vanta’s incident names AWS (location or integration). (hop 1, posted +9 min vs the first vendor naming AWS)
“…Subset of AWS related tests showing inaccurate test results This issue has been resolved and you should no longer see incorrect test results moving forward. If you have any questions or concerns, plea…”
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/>Dagster, Snowflake, Vanta"]:::blames
root --> h1
h4["1 to 4 hours later<br/>7 vendors, 5 blamed AWS<br/>Amplitude, Temporal Cloud, Coralogix, Confluent +3"]:::blames
root --> h4
me["Vanta (this incident)<br/>posted +9 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.
Timeline of updates
- resolved
This issue has been resolved and you should no longer see incorrect test results moving forward. If you have any questions or concerns, please don’t hesitate to contact our Support Team at support@vanta.com.
From Vanta’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.vanta.com (opens in new tab).