Is Drata Down?

No — Drata is up

We cannot measure Drata directly — it blocks automated checks — but Drata's own status page currently reports no issues.

Last checked 2 hours ago · checks run every 6 hours

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

Why there is no uptime figure on this page

The last time we fetched Drata's page directly, the origin answered and turned our client away rather than serving the page. That answer tells us the origin was reachable and responding, but it is a response about our automation, not about whether Drata works for you.

A percentage built from those checks would measure our own access, so we do not publish one. What this page does show is each region's most recent result and Drata's own status feed, which you can weigh yourself.

30-day history

Aug 22 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.

ams

edge reachable

A static asset loaded in 219ms. That proves the edge is up, but not that the site works.

arn

edge reachable

A static asset loaded in 313ms. That proves the edge is up, but not that the site works.

bom

edge reachable

A static asset loaded in 295ms. That proves the edge is up, but not that the site works.

cdg

edge reachable

A static asset loaded in 130ms. That proves the edge is up, but not that the site works.

sin

edge reachable

A static asset loaded in 293ms. That proves the edge is up, but not that the site works.

sjc

edge reachable

A static asset loaded in 185ms. That proves the edge is up, but not that the site works.

syd

edge reachable

A static asset loaded in 326ms. That proves the edge is up, but not that the site works.

yyz

edge reachable

A static asset loaded in 232ms. That proves the edge is up, but not that the site works.

What Drata does

Drata automates security compliance evidence for frameworks such as SOC 2 and ISO 27001. It pulls configuration and control data from cloud accounts, identity providers and employee laptops, then presents it to auditors and to customers through a hosted Trust Center. Companies rely on it during audit windows and while answering security questionnaires from prospects.

What an outage looks like

The web application fails to load or sign-in stalls. Evidence collection is the quieter failure: incoming webhooks and the agent reporting path stop, so control checks show stale or missing data without any obvious error. Drata also hosts customer-facing Trust Center pages, so an incident there breaks a public page linked from your own marketing site and sales emails.

What to do about it

Open status.drata.com and read your own region. Drata reports US, EU and APAC as separate groups, each with its own API, Agent API, Public API, Auditor API and Incoming Webhooks. Trust Center Pages and the Trust Center Admin Page are listed apart from the Web Application, so confirm which is affected before telling a prospect your compliance page is fine. Postpone audit exports rather than retrying them.

Is it down for everyone, or just you?

If this page says Drata 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 18 cities across three regions to find out where it breaks.

Test it yourself

Related services

Vanta

Snyk

Wiz

Okta

Drata outage FAQ

Does a Drata outage put my SOC 2 compliance at risk?

An outage interrupts evidence collection and reporting, not the underlying controls. Your cloud configuration, access policies and endpoint settings are unchanged by Drata being unreachable. The practical risk is a gap in the collected record during an audit window, which is a documentation question for your auditor rather than a control failure, and is usually resolved once collection resumes.

Is my public Trust Center down too?

Check separately. Drata lists Trust Center Pages and the Trust Center Admin Page as components distinct from the Web Application, so the page prospects visit can be broken while your internal console works, or the reverse. This matters more than it looks: a Trust Center is normally linked from sales material, so an outage there is visible to people outside your company.

Which region am I on?

Drata operates US, EU and APAC as separate component groups on its status page, each with its own API, Agent API, Public API, Auditor API and Incoming Webhooks rows. An incident affecting the EU group leaves US accounts working normally. Reading the wrong group is the usual reason a status page appears to contradict what you are seeing.

My controls suddenly show as failing. Is that real?

Not necessarily during an incident. Control status is derived from collected evidence, and the Agent API and Incoming Webhooks components are the paths that evidence arrives on. When those are degraded, checks can report stale or absent data rather than a genuine configuration change. Confirm against the source system before treating a newly failing control as a real finding.

Can auditors still access my evidence?

Drata reports an Auditor API for each region as its own component, separate from the main API and the web application. During an incident scoped to that component, auditor access can be affected while your own console works. If an audit is in progress, tell the auditor what the status page reports rather than leaving repeated failed access attempts unexplained.

How we measure this

We request Drata's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
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 Drata 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 — and when Drata blocks our checks entirely, we report the vendor's own status directly.

Get alerted when Drata goes down

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

Start Free Monitoring

Free plan available No credit card required