Companies / Sanity / incidents

Sanity: History API inconsistencies

Affected components: Dataset Management

Timeline of updates

1. identified2026-02-09 13:50 UTC

   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.

2. identified2026-02-09 14:34 UTC

   We are continuing to work on a fix for this issue.

3. identified2026-02-09 15:12 UTC

   We are continuing to work on a fix for this issue.

4. identified2026-02-09 15:54 UTC

   We are continuing to work on a fix for this issue.

5. monitoring2026-02-09 16:21 UTC

   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.

6. resolved2026-02-10 13:39 UTC

   The issue has been resolved. All affected customer datasets have been remediated and the service is operating normally.

Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab). Sanity profile · Recent Sanity incidents · Markdown · JSON