Sanity reported this minor-impact incident on its official status page on Feb 9, 2026, 13:50 UTC. It was resolved after 23h 49m.
Right now Sanity is operational. Live Sanity status →
The issue has been resolved. All affected customer datasets have been remediated and the service is operating normally.
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.
We are continuing to work on a fix for this issue.
We are continuing to work on a fix for this issue.
We are continuing to work on a fix for this issue.
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.
Our 5-minute checks didn't record a change in Sanity's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.
Overlapping incidents aren't necessarily related.
Sanity reported 10 incidents in the last 90 days, 3 of them major or critical. A typical incident lasted 52 min. See Sanity's uptime and incident history