- Level
- confirmed
- Worst impact
- Degraded
- Components
- api.sanity.io
- Down Index
- 24of 100
What to do
Check whether you use Sanity api.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 22h 6m it lasted.
Anything that failed between 2026-10-14 12:48 UTC and 2026-10-15 10: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 3
- investigating
We are investigating intermittent increased latency affecting API requests for a small subset of customers. Some requests may also have returned errors. Most customers are unaffected. Our engineers have identified the cause and have taken steps to reduce the impact while we continue to investigate. We will post another update as soon as we have more information.
provider
- monitoring
A fix has been implemented, and we are currently monitoring 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-668096b96a
Is Sanity still down?
No, this incident was resolved 2026-10-15 10:54 UTC. For Sanity's live state, see https://down.guide/sanity.
How long did it last?
22h 6m, from 2026-10-14 12:48 UTC to 2026-10-15 10:54 UTC, by the times Sanity posted.
What was affected?
Sanity named api.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.