Companies / Vanta / changes

Vanta change history

11Major incident
When (UTC)ChangeKind
Major incident: Some Vanta AI features are unavailable
Vanta reported a major outage affecting AI features in Vendor Risk Management, Questionnaire Automation, Policy Search, and Policy Generation from 2026-09-14 14:10 UTC to 2026-09-14 15:40 UTC, lasting 1 h 30 min. Vanta said it understood the root cause but did not disclose it or the fix; the incident was resolved.
Major incident
Major incident: Sync operations failing for GCP Firestore
Vanta reported a major incident with GCP Firestore sync operations: syncs for GCP Firebase projects and databases failed, leaving some resource data stale in the Vanta app. It started at 2026-09-09 19:56 UTC and was resolved at 2026-09-10 21:36 UTC, lasting 25 h 39 min; Vanta worked with the GCP team but stated no cause or specific fix.
Major incident
Major incident: EU Region Degraded Performance
Vanta reported a major EU-region incident causing elevated errors, degraded performance and possible inability to access the platform; US and AUS regions were unaffected. It started at 2026-05-01 10:25 UTC and was resolved at 2026-05-02 12:43 UTC, lasting 26 h 18 min; Vanta said EU infrastructure recovery took longer than expected.
Major incident
Major incident: New Private and Partner Integrations
Vanta reported a major outage affecting connections to new private and partner integrations, starting at 2026-04-28 21:57 UTC and resolved at 2026-04-29 01:01 UTC after 3 h 4 min. Vanta applied a fix and confirmed services were working as expected again.
Major incident
Major incident: Missing GitHub data
Vanta reported a major degradation starting 2026-04-27 18:56 UTC: GitHub Pull Requests, Issues, and Dependabot vulnerabilities could be missing, affecting related test statuses. Vanta attributed it to downstream GitHub incidents; resolution followed their recovery and completion of Vanta’s remediation at 2026-05-01 17:42 UTC, after 3 days 22 h.
Major incident
Major incident: Pages missing in nav for customers
Vanta reported a major incident: the Access tab disappeared, and some MSP customers saw only `/integrations`. It lasted from 2026-01-27 16:45 UTC to 2026-01-28 23:57 UTC (31 h 12 min). Vanta said a system synchronization mistakenly removed features for a small number of MSP accounts; access was restored and the incident resolved.
Major incident
Critical incident: Vanta intermittently inaccessible
Vanta reported a critical outage disrupting access to its web app and all Trust Centers starting 2025-11-18 12:00 UTC, lasting 5 h 38 min. Vanta attributed the disruption to a core networking infrastructure provider; the provider deployed a fix, and access was restored by 2025-11-18 17:39 UTC.
Major incident
Critical incident: Vanta Application Unable to Load
Vanta reported a critical Core App outage starting 2025-11-10 19:40 UTC: a major performance regression prevented the application from loading. Loading resumed with high latency before mitigations restored normal latency; the incident was resolved at 2025-11-10 22:38 UTC after 2 h 58 min.
Major incident
Major incident: Issues installing Vanta Device Monitor
Vanta Device Monitor installations were failing in a major-impact outage that started at 2025-10-20 21:11 UTC and lasted 14 min. Vanta marked it resolved at 2025-10-20 21:25 UTC, stating installations should function as expected; no cause or specific fix was disclosed.
Major incident
Critical incident: Vanta web app loading issues (US region)
Vanta reported a critical outage affecting US-region web app loading, with slowness and errors across the platform attributed to the AWS US-East-1 outage. It started at 2025-10-20 15:25 UTC and was resolved at 2025-10-20 22:26 UTC, lasting 7 h 0 min; Vanta confirmed the web app was stable in all regions.
Major incident
Major incident: Jira Integration Unlinking
Vanta reported a major incident causing customers’ Jira integrations to unlink, starting 2025-10-02 14:39 UTC and resolved 2025-10-07 13:52 UTC, lasting 4 days 23 h. Vanta identified the issue and confirmed resolution but did not disclose a cause or specific fix.
Major incident