- Level
- confirmed
- Worst impact
- Degraded
- Components
- api.sanity.io, apicdn.sanity.io
- Down Index
- 14of 100
What to do
Check whether you use Sanity api.sanity.io, apicdn.sanity.io. 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 5m it lasted.
Anything that failed between 2026-10-26 15:49 UTC and 2026-10-26 15:54 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 2
- monitoring
From 13:12 to 15:13 UTC, a small subset of customers experienced intermittent increased latency on API requests, and some requests returned errors. Most customers were unaffected. Our engineers identified the cause and took steps to resolve it, and API performance has been back to normal since 15:07 UTC, and we are continued to monitor the results.
provider
- resolved
This incident has been resolved.
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-c21b3001c4
Is Sanity still down?
No, this incident was resolved 2026-10-26 15:54 UTC. For Sanity's live state, see https://down.guide/sanity.
How long did it last?
5m, from 2026-10-26 15:49 UTC to 2026-10-26 15:54 UTC, by the times Sanity posted.
What was affected?
Sanity named api.sanity.io, apicdn.sanity.io.
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.