- Level
- confirmed
- Worst impact
- Partial outage
- Down Index
- 18of 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-06-26 09:53 UTC and 2026-06-25 20:30 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
A small subset of customers experienced increased query latency and intermittent timeouts during this incident. Our engineering team identified the issue, implemented mitigations, and restored normal query performance. The 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-485e04a306
Is Sanity still down?
No, this incident was resolved 2026-06-25 20:30 UTC. For Sanity's live state, see https://down.guide/sanity.
How long did it last?
0m, from 2026-06-26 09:53 UTC to 2026-06-25 20:30 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.