- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 8of 100
What to do
Check whether your product depends on Sanity. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.
Anything that failed between 2026-01-22 16:50 UTC and 2026-01-20 09:00 UTC may need a replay.Subscribe to Sanity's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=sanity works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Sanity 1
- resolved
On January 20th at 8:52pm UTC, there was an update to the Sanity CLI that had a regression when trying to run the init flow (`npm create sanity@latest`) that resulted in a non-functioning project. This update was rolled back at January 21st at ~2am UTC. As of January 21st, the latest version should be 5.2.1.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-9be28bd7a6
Is Sanity still down?
No, this incident was resolved 2026-01-20 09:00 UTC. For Sanity's live state, see https://down.guide/sanity.
How long did it last?
0m, from 2026-01-22 16:50 UTC to 2026-01-20 09:00 UTC, by the times Sanity posted.
What caused it?
Sanity hasn't published a root cause. If it does, it shows here.
Where does this come from?
Sanity's official status page, https://www.sanity-status.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.