- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 8of 100
What to do
Check whether your product depends on Vanta. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.
Anything that failed between 2026-08-03 21:12 UTC and 2026-08-03 18:12 UTC may need a replay.Subscribe to Vanta's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=vanta works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Vanta 1
- resolved
We have resolved an issue where customers were unable to programmatically install the Vanta agent using our installation scripts (such as deployments via MDM). This was caused by an unexpected permissions change that made the scripts repository private starting on July 31, 2026, at 3:07 PM UTC. Full access has been restored, and scripted installations are now functioning normally. Direct agent installations were unaffected during this time. We apologize for any disruption this may have caused to your deployment processes.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-aa4db392ca
Is Vanta still down?
No, this incident was resolved 2026-08-03 18:12 UTC. For Vanta's live state, see https://down.guide/vanta.
How long did it last?
0m, from 2026-08-03 21:12 UTC to 2026-08-03 18:12 UTC, by the times Vanta posted.
What caused it?
Vanta hasn't published a root cause. If it does, it shows here.
Where does this come from?
Vanta's official status page, https://status.vanta.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.