- Level
- confirmed
- Worst impact
- Degraded
- Components
- apicdn.sanity.io
- Down Index
- 17of 100
What to do
Check whether you use Sanity 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 38m it lasted.
Anything that failed between 2026-01-05 14:05 UTC and 2026-01-05 14:43 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
Beginning around 13:40 UTC we began experiencing elevated error rates on our API CDN in certain regions. As a result, some requests may respond with a 5xx status. We're investigating the issue now.
provider
- monitoring
We've mitigated the original issue and are no longer seeing elevated error rates. We're continuing to monitor and while we investigate the root cause.
provider
- resolved
The issue was related to a higher than expected load which has been resolved. All operations are back to normal and we'll continue to monitor our systems closely.
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-9d06bc6b61
Is Sanity still down?
No, this incident was resolved 2026-01-05 14:43 UTC. For Sanity's live state, see https://down.guide/sanity.
How long did it last?
38m, from 2026-01-05 14:05 UTC to 2026-01-05 14:43 UTC, by the times Sanity posted.
What was affected?
Sanity named 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.