Elevated listener latency and error rate impacting Studio loading

Update timeline

1. investigating Oct 08, 2026, 09:55 AM UTC

   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. investigating Oct 08, 2026, 10:10 AM UTC

   We are continuing to investigate this issue.

3. investigating Oct 08, 2026, 10:27 AM UTC

   We are currently continuing to investigate the issue, while also rolling out mitigations.

4. investigating Oct 08, 2026, 10:37 AM UTC

   We are continuing to investigate the issue. Additionally, there might be a slight delay in document publishes for "scheduled publishing" functionality.

5. investigating Oct 08, 2026, 10:56 AM UTC

   We are currently continuing to investigate the issue, while also preparing to roll a set of mitigations.

6. investigating Oct 08, 2026, 11:01 AM UTC

   We are continuing to investigate this issue.

7. investigating Oct 08, 2026, 11:21 AM UTC

   We are continuing to investigate this issue.

8. investigating Oct 08, 2026, 11:38 AM UTC

   We're continuing to investigate this issue. In the meantime, we've begun rolling out preliminary measures to mitigate its impact.

9. investigating Oct 08, 2026, 11:58 AM UTC

   We're continuing to investigate this issue. And we are continuing rolling out preliminary measures to mitigate its impact.

10. investigating Oct 08, 2026, 12:18 PM UTC

    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. investigating Oct 08, 2026, 12:33 PM UTC

    We're continuing to investigate this issue. And we are continuing rolling out measures to mitigate its impact.

12. investigating Oct 08, 2026, 12:50 PM UTC

    We're continuing to investigate this issue. And we are continuing to apply measures to mitigate its impact.

13. identified Oct 08, 2026, 01:13 PM UTC

    The issue has been identified. We are continuing to apply fixes to mitigate its impact.

14. identified Oct 08, 2026, 01:32 PM UTC

    We are continuing to apply fixes to mitigate the impact.

15. identified Oct 08, 2026, 01:46 PM UTC

    We are continuing to apply fixes to mitigate the impact. No errors have been observed from the changes rolled out so far.

16. monitoring Oct 08, 2026, 01:57 PM UTC

    A fix has been fully implemented and we are monitoring the results.

17. monitoring Oct 08, 2026, 02:13 PM UTC

    We are continuing to monitor for any further issues.

18. resolved Oct 08, 2026, 02:28 PM UTC

    This incident has been resolved.