- Level
- confirmed
- Worst impact
- Degraded
- Components
- Dataset Management
- Down Index
- 24of 100
What to do
Check whether you use Sanity Dataset Management. 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 23h 49m it lasted.
Anything that failed between 2026-02-09 13:50 UTC and 2026-02-10 13:39 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 6
- identified
We are mitigating an issue causing inconsistencies in data returned from the History API for a subset of customers. This issue started on February 5th 2026 for the datasets created after December 9th 2025 and not mutated since until 26th January 2026, this also impacts the History view in the Sanity Studio. People may see the wrong document revision when querying by transaction ID or an inaccurate chronological order when viewing history entries. We will keep you posted as a fix is being implemented.
provider
- identified
We are continuing to work on a fix for this issue.
provider
- identified
We are continuing to work on a fix for this issue.
provider
- identified
We are continuing to work on a fix for this issue.
provider
- monitoring
The underlying cause of the issue has been resolved. We are continuing internal monitoring and completing remediation for a small number of affected customer datasets, working directly with impacted customers as needed.
provider
- resolved
The issue has been resolved. All affected customer datasets have been remediated and the service is operating normally.
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-7ccfbcad86
Is Sanity still down?
No, this incident was resolved 2026-02-10 13:39 UTC. For Sanity's live state, see https://down.guide/sanity.
How long did it last?
23h 49m, from 2026-02-09 13:50 UTC to 2026-02-10 13:39 UTC, by the times Sanity posted.
What was affected?
Sanity named Dataset Management.
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.