Critical incident

Sanity: Elevated listener latency and error rate impacting Studio loading

Affected: Studio

Current status of Sanity: Operational — live Sanity status

Timeline

1. Oct 8, 2026, 09:55 UTC
   investigating
   We are currently investigating an issue where elevated listener latency may result in slower performance and lag within Sanity Studio for a subset of customers. Our team is actively working to identify the root cause and mitigate the impact. Issue starting around 9:10 UTC.
2. Oct 8, 2026, 10:10 UTC
   investigating
   We are continuing to investigate this issue.
3. Oct 8, 2026, 10:27 UTC
   investigating
   We are currently continuing to investigate the issue, while also rolling out mitigations.
4. Oct 8, 2026, 10:37 UTC
   investigating
   We are continuing to investigate the issue. Additionally, there might be a slight delay in document publishes for "scheduled publishing" functionality.
5. Oct 8, 2026, 10:56 UTC
   investigating
   We are currently continuing to investigate the issue, while also preparing to roll a set of mitigations.
6. Oct 8, 2026, 11:01 UTC
   investigating
   We are continuing to investigate this issue.
7. Oct 8, 2026, 11:21 UTC
   investigating
   We are continuing to investigate this issue.
8. Oct 8, 2026, 11:38 UTC
   investigating
   We're continuing to investigate this issue. In the meantime, we've begun rolling out preliminary measures to mitigate its impact.
9. Oct 8, 2026, 11:58 UTC
   investigating
   We're continuing to investigate this issue. And we are continuing rolling out preliminary measures to mitigate its impact.
10. Oct 8, 2026, 12:18 UTC
    investigating
    We're continuing to investigate this issue. And we are continuing rolling out measures to mitigate its impact. "scheduled publishing" functionality confirmed unaffected by this incident.
11. Oct 8, 2026, 12:33 UTC
    investigating
    We're continuing to investigate this issue. And we are continuing rolling out measures to mitigate its impact.
12. Oct 8, 2026, 12:50 UTC
    investigating
    We're continuing to investigate this issue. And we are continuing to apply measures to mitigate its impact.
13. Oct 8, 2026, 13:13 UTC
    identified
    The issue has been identified. We are continuing to apply fixes to mitigate its impact.
14. Oct 8, 2026, 13:32 UTC
    identified
    We are continuing to apply fixes to mitigate the impact.
15. Oct 8, 2026, 13:46 UTC
    identified
    We are continuing to apply fixes to mitigate the impact. No errors have been observed from the changes rolled out so far.
16. Oct 8, 2026, 13:57 UTC
    monitoring
    A fix has been fully implemented and we are monitoring the results.
17. Oct 8, 2026, 14:13 UTC
    monitoring
    We are continuing to monitor for any further issues.
18. Oct 8, 2026, 14:28 UTC
    resolved
    This incident has been resolved.

Updates as published by Sanity (original).