- Level
- confirmed
- Worst impact
- Degraded
- Components
- api.sanity.io, apicdn.sanity.io
- Down Index
- 23of 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 5h 11m it lasted.
Anything that failed between 2026-02-03 16:06 UTC and 2026-02-03 21:17 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 3
- investigating
We are currently investigating an increase in API and API CDN errors and latency impacting a subset of customers. We are actively mitigating impact while working to identify the issue.
provider
- monitoring
We've identified and mitigated the root cause of the issue. Performance has been stable since 16:17 UTC with no elevated error rates, and we are continuing to monitor.
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-f34f0ff381
Is Sanity still down?
No, this incident was resolved 2026-02-03 21:17 UTC. For Sanity's live state, see https://down.guide/sanity.
How long did it last?
5h 11m, from 2026-02-03 16:06 UTC to 2026-02-03 21:17 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.