Is Sanity Down?

No — Sanity is up

Reachable from all 8 checked regions

Average response time: 391ms

Last checked 5 hours ago · checks run every 6 hours

Official status page: https://www.sanity-status.com

Sanity 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 25 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.

bom

263ms

DNS 170ms TCP 2ms TLS 8ms TTFB 246ms

cdg

202ms

DNS 64ms TCP 9ms TLS 14ms TTFB 166ms

dfw

356ms

DNS 72ms TCP 25ms TLS 31ms TTFB 277ms

ewr

251ms

DNS 173ms TCP 0ms TLS 17ms TTFB 243ms

fra

105ms

DNS 32ms TCP 1ms TLS 8ms TTFB 96ms

gru

441ms

DNS 355ms TCP 3ms TLS 9ms TTFB 424ms

iad

226ms

DNS 156ms TCP 1ms TLS 7ms TTFB 207ms

jnb

1267ms

DNS 442ms TCP 2ms TLS 61ms TTFB 1236ms

lax

282ms

DNS 124ms TCP 1ms TLS 23ms TTFB 269ms

What Sanity does

Sanity is a headless content platform: editors work in Sanity Studio while the content itself lives in a hosted Content Lake that applications query over an API. Marketing sites, e-commerce catalogues and documentation built on Next.js or similar frameworks read from it at build time or on each request, so its availability shapes what visitors see.

What an outage looks like

Queries to api.sanity.io fail or slow, and pages that fetch content at request time return errors while statically built pages keep serving. Images from cdn.sanity.io do not load, leaving broken placeholders. Editors cannot sign in to Studio or their changes will not save. Webhooks do not fire, so downstream rebuilds never trigger and a site quietly serves old content.

What to do about it

sanity-status.com reports api.sanity.io, apicdn.sanity.io, cdn.sanity.io, Authentication, GraphQL, Webhooks and the Dashboard as separate components, which usually identifies the fault quickly. If the API is affected but your site is statically generated, hold off on triggering a rebuild until it clears, because a deploy during the incident can replace working pages with empty ones.

Is it down for everyone, or just you?

If this page says Sanity 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

Sanity outage FAQ

My site works but editors cannot publish. Is Sanity down?

That pattern points at Studio or authentication rather than content delivery. A statically generated site serves pages built earlier and does not call Sanity on each request, so visitors see nothing wrong while the editing path is broken. The status page lists Authentication and the Dashboard separately from the content APIs, which usually confirms it.

Should I redeploy my site during a Sanity incident?

Wait if you can. A build fetches content from the API, so deploying while the API is degraded can produce pages with missing or empty content and publish them over the working version. That turns a problem invisible to visitors into one they can see. Hold the deploy until the API components are healthy again.

Why are images broken but text still loading?

They come from different components. Text is served from api.sanity.io or apicdn.sanity.io, while images are delivered by cdn.sanity.io, and the status page tracks each one. A CDN incident leaves copy intact and pictures missing, which is exactly what a reader sees as broken placeholders on an otherwise working page.

Do webhooks that failed during an outage fire later?

Do not count on it. Webhooks are listed as their own component, and events that fail to dispatch may not be replayed, which means a rebuild that should have been triggered never was. After recovery, check whether your site reflects the latest content and trigger a deploy by hand if it does not.

How we measure this

We request Sanity'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 Sanity 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 Sanity 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