Is Vanta Down?

No — Vanta is up

Reachable from all 8 checked regions

Average response time: 85ms

Last checked 5 hours ago · checks run every 6 hours

Official status page: https://status.vanta.com

Vanta uptime

100%

Last 7 days

—

Last 30 days

—

Last 90 days

—

Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 6 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

6-day clean streak

Jul 26 Today

No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

arn

86ms

DNS 0ms TCP 1ms TLS 17ms TTFB 69ms

bom

67ms

DNS 0ms TCP 3ms TLS 11ms TTFB 48ms

cdg

58ms

DNS 0ms TCP 2ms TLS 9ms TTFB 47ms

dfw

53ms

DNS 0ms TCP 1ms TLS 8ms TTFB 44ms

ewr

54ms

DNS 0ms TCP 2ms TLS 8ms TTFB 42ms

fra

60ms

DNS 0ms TCP 1ms TLS 9ms TTFB 51ms

gru

56ms

DNS 0ms TCP 3ms TLS 10ms TTFB 39ms

iad

42ms

DNS 0ms TCP 1ms TLS 7ms TTFB 30ms

jnb

295ms

DNS 0ms TCP 0ms TLS 10ms TTFB 283ms

What Vanta does

Vanta automates the evidence collection behind SOC 2, ISO 27001, HIPAA, PCI and GDPR programmes. It connects to a company's cloud accounts, identity provider and laptops, watches controls continuously, and hands auditors the results. Security and compliance teams run access reviews, vendor risk and customer security questionnaires through it, and publish a Trust Center from the same data.

What an outage looks like

The core app will not load or shows controls without evidence behind them. Integrations stop syncing, so cloud and identity checks drift to failing and raise alarms about controls that are fine. The Vanta Device Monitor on employee laptops reports nothing. Access Reviews and Questionnaire Automation stall mid-workflow, and a public Trust Center may not render for prospects.

What to do about it

status.vanta.com lists Core App, 3rd Party Integrations, Access Reviews, Vanta Device Monitor, the Public API and Trust Center separately, so identify which part is affected. Treat control failures raised during an integration incident as unconfirmed until syncing resumes rather than chasing them. If an audit deadline is close, tell the auditor the evidence export is delayed.

Is it down for everyone, or just you?

If this page says Vanta is up but it is not loading for you, the problem is between you and them. Run a check against any URL from all 18 regions to find out where it breaks.

Test it yourself

Related services

Vanta outage FAQ

Are the failing controls real or caused by the outage?

Treat them as unconfirmed. Vanta marks a control as failing when the evidence behind it is missing, and an integration incident makes evidence missing without anything changing in your infrastructure. Wait for 3rd Party Integrations to recover and for a full sync before investigating; controls that failed for this reason return to passing on their own.

Does a Vanta outage affect our SOC 2 audit?

Not the audit itself. Vanta collects and organises evidence, so an outage delays evidence gathering and export rather than invalidating anything already collected. If a deadline falls during a longer incident, tell the auditor early. Monitoring gaps caused by the platform are a Vanta matter to explain, not a control failure on your side.

Our Trust Center will not load for a prospect. Is that us?

Check the status page first. Trust Center is listed as its own component, so it can fail while the core app works normally. Since prospects reach it during security reviews, an outage looks like a broken link at an awkward moment. If it persists, send the documentation directly rather than leaving a buyer at an error page.

Why is Vanta Device Monitor reporting nothing on our laptops?

The agent reports into Vanta, so when that path is disrupted the fleet appears to go dark at once. A whole company's laptops falling off simultaneously is a platform symptom, not a fleet-wide failure. The status page lists Vanta Device Monitor separately. The devices are unaffected and reappear once reporting resumes.

How we measure this

We request Vanta's public endpoint every 6 hours from Fly.io regions across six continents — 8 of them answered the most recent check.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
Response times average only the regions that actually served the page, so a timeout never inflates the number.
Where Vanta publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Vanta goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from the same 18 regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required