Is Vanta Down?

No — Vanta is up

Vanta's status page: Operational · no open incidents
FlareWarden checks: Website reachable · 8 of 8 regions · 190 ms

Right now

The verdict is the worse of these two. How we decide

Vanta's status page

status.vanta.com · read 3 minutes ago · checked every 3 minutes

Operational

Vanta's components, as its status page reports them
Component	Status
Core App	Operational
Access Reviews	Operational
Questionnaire Automation	Operational
Vendor Risk Management	Operational
Trust Center	Operational
Vanta AI	Operational
Audit Hub	Operational
Customer Commitments	Operational
3rd Party Integrations	Operational
Private/Partner Integrations	Operational
Vanta Device Monitor	Operational
Vanta Public API	Operational

1 more, all operational · show all 13

All of Vanta's components
Component	Status
Vanta Web App
Core App	Operational
Access Reviews	Operational
Questionnaire Automation	Operational
Vendor Risk Management	Operational
Trust Center	Operational
Vanta AI	Operational
Audit Hub	Operational
Customer Commitments	Operational
Vanta Integrations
3rd Party Integrations	Operational
Private/Partner Integrations	Operational
Vanta Device Monitor	Operational
Vanta Public API	Operational
Vanta MCP Server	Operational

Open their status page

FlareWarden checks

vanta.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable

Regions up: 8 of 8
Response: 190 ms
Checked: 3 hours ago

By region

Amsterdam reachable, 112 ms
Dallas reachable, 155 ms
Newark reachable, 202 ms
Paris reachable, 126 ms
San Jose reachable, 150 ms
Stockholm reachable, 221 ms
Sydney reachable, 243 ms
Toronto reachable, 311 ms

Timing by region

Connection timing for each region that loaded the page
Region	DNS	TCP	TLS	TTFB
Amsterdam	31 ms	2 ms	9 ms	104 ms
Dallas	98 ms	2 ms	12 ms	145 ms
Newark	134 ms	2 ms	10 ms	194 ms
Paris	56 ms	2 ms	12 ms	118 ms
San Jose	66 ms	2 ms	13 ms	141 ms
Stockholm	178 ms	1 ms	7 ms	214 ms
Sydney	207 ms	0 ms	6 ms	239 ms
Toronto	237 ms	1 ms	15 ms	303 ms

We check that vanta.com loads, not every feature behind it. Test it yourself

History

Incidents Vanta reported

Since Oct 22, 2 days · from status.vanta.com

Incidents: 1
Major or critical: 1
Median to resolve: 7h 42m

Stale data for CloudflareDomainInventory and CloudflareZoneRule
major · Oct 21
lasted 7h 42m

Vanta website availability

Measured by FlareWarden · vanta.com

Last 7 days: 100%
Last 30 days: 100%
Last 90 days: 100%
Avg response, 30 days: 228ms

Last 30 days

67-day clean streak

Sep 24 Today

No downtime Partial Downtime Not measurable No data

Measured by FlareWarden's own checks of vanta.com from multiple regions every 6 hours. Vanta's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 67 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

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 up to 17 cities across three 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 — the most recent check ran from 8 of them. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
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. Our checks only change their 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, and the verdict is the worse of what it reports and what our checks see: a major outage of Vanta itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.

Get alerted when Vanta goes down

We check Vanta every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required