Loading status…
Loading status…
Sanity status · Data & Backend · checked (1m ago)
Also searched as Sanity.io, Sanity CMS.
No — Sanity is not down. All Sanity systems are reported operational.
According to Sanity's official status page, Sanity was reporting “All Systems Operational” when isuptime last checked at . Over the last 30 days, Sanity's feed reported no outage in 100.00% of our checks.
Everything above is read from Sanity's own status feed. This is what other visitors are saying in the last 24 hours — useful when the feed is green and you are still stuck, and never used to change the status above.
Nobody has reported Sanity in the last 24 hours. Yours would be the first.
Reports are anonymous counts and are kept for 24 hours, then deleted. No account, no message, nothing stored about who reported. One report per service per hour, changeable until the hour is out.
Sanity is a headless CMS: content lives in a hosted document store, is edited in the Studio, and is read by applications through its APIs and the GROQ query language. Websites built on it fetch content at build time, at request time, or both.
The status page separates the content APIs from the Studio and the asset CDN. That split determines how much an incident costs you: a site that fetches content at build time and serves it statically is unaffected by an API outage, while one querying on every request goes down with it. Assets are served from a separate CDN that survives most API problems.
isuptime reads this feed on a schedule and reports what it says — how that works, in detail.
One bar per day. Each shows the share of that day's checks where Sanity's own status feed reported no outage — degraded counts as no-outage. Days with no bar are days isuptime recorded no checks, not days Sanity was down.
14 other services isuptime tracks were also reporting a problem as of the same check, 1m ago. They are checked on one schedule, so the timing is comparable — but overlapping in time does not mean they share a cause.
Each point is one check of Sanity's status endpoint.
Sanity has published 50 incidents in the last 12 months, the 20 most recent shown here. Only what Sanity posted itself — not every problem users hit.
resolved · Sep 15, 11:46 AM (4d ago)
resolved · Sep 1, 07:31 AM (18d ago)
resolved · Aug 27, 04:30 AM (24d ago)
resolved · Aug 26, 08:00 AM (24d ago)
resolved · Aug 20, 02:33 PM (30d ago)
resolved · Aug 17, 07:45 AM (33d ago)
resolved · Aug 14, 02:46 PM (36d ago)
resolved · Aug 6, 09:45 AM (44d ago)
resolved · Jul 24, 11:16 PM (57d ago)
resolved · Jul 22, 09:30 PM (59d ago)
resolved · Jul 22, 11:45 AM (59d ago)
resolved · Jul 21, 04:32 PM (60d ago)
resolved · Jun 25, 08:30 PM (86d ago)
resolved · Jun 15, 06:15 AM (96d ago)
resolved · May 29, 09:19 AM (113d ago)
resolved · May 1, 12:00 PM (141d ago)
resolved · Apr 14, 07:48 AM (158d ago)
resolved · Apr 13, 07:45 AM (159d ago)
resolved · Apr 6, 02:00 PM (166d ago)
resolved · Apr 3, 01:38 PM (169d ago)
The API CDN caches aggressively, so newly published content genuinely may not be visible for a short time — that is caching, not loss. A query returning nothing is usually a GROQ filter or the wrong dataset name, and drafts are invisible to a token that lacks draft access. Rate limits apply per project and are easy to hit from a build that fetches in a loop.
Sanity is reporting no problems right now. If it stops, these cover the same job — each shows its own live status.
Status shown for each is read from that provider's own feed, on the same schedule as this page.