# Elevated listener latency and error rate impacting Studio loading - Provider: [Sanity](https://down.guide/sanity) - Level: confirmed - Impact: Major outage - lasted 4h 34m - started 2026-10-08 09:55 UTC - Studio - id: DWN-3457159fbf - Official page: https://stspg.io/160t1f18vnlh ## Root cause > Our team is actively working to identify the root cause and mitigate the impact. [Postmortem](https://stspg.io/160t1f18vnlh) ## Updates from Sanity ### 2026-10-08 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. ### 2026-10-08 10:10 UTC: investigating We are continuing to investigate this issue. ### 2026-10-08 10:27 UTC: investigating We are currently continuing to investigate the issue, while also rolling out mitigations. ### 2026-10-08 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. ### 2026-10-08 10:56 UTC: investigating We are currently continuing to investigate the issue, while also preparing to roll a set of mitigations. ### 2026-10-08 11:01 UTC: investigating We are continuing to investigate this issue. ### 2026-10-08 11:21 UTC: investigating We are continuing to investigate this issue. ### 2026-10-08 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. ### 2026-10-08 11:58 UTC: investigating We're continuing to investigate this issue. And we are continuing rolling out preliminary measures to mitigate its impact. ### 2026-10-08 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. ### 2026-10-08 12:33 UTC: investigating We're continuing to investigate this issue. And we are continuing rolling out measures to mitigate its impact. ### 2026-10-08 12:50 UTC: investigating We're continuing to investigate this issue. And we are continuing to apply measures to mitigate its impact. ### 2026-10-08 13:13 UTC: identified The issue has been identified. We are continuing to apply fixes to mitigate its impact. ### 2026-10-08 13:32 UTC: identified We are continuing to apply fixes to mitigate the impact. ### 2026-10-08 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. ### 2026-10-08 13:57 UTC: monitoring A fix has been fully implemented and we are monitoring the results. ### 2026-10-08 14:13 UTC: monitoring We are continuing to monitor for any further issues. ### 2026-10-08 14:28 UTC: resolved This incident has been resolved. --- down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by Sazabi (https://sazabi.com/?utm_source=down-guide&utm_medium=markdown).