Search

Companies / Sanity / incidents

Sanity: Elevated listener latency and error rate impacting Studio loading

Impact: criticalStatus: resolvedStarted Resolved (4.6 h)18 updatesSource: stspg.io (opens in new tab)
Summary

Sanity reported critical elevated listener latency and error rates affecting Studio loading, with slower performance and lag for some customers. The recorded incident ran from 2026-10-08 09:55 UTC to 2026-10-08 14:28 UTC (4 h 33 min), though Sanity noted issues began around 9:10 UTC. A fix was fully implemented and the incident resolved.

Machine-written from the archived incident (Sol). Check the timeline before relying on it.

Affected components: Studio

Timeline of updates

  1. 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. investigating

    We are continuing to investigate this issue.

  3. investigating

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

  4. investigating

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

  5. investigating

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

  6. investigating

    We are continuing to investigate this issue.

  7. investigating

    We are continuing to investigate this issue.

  8. investigating

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

  9. investigating

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

  10. 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. investigating

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

  12. investigating

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

  13. identified

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

  14. identified

    We are continuing to apply fixes to mitigate the impact.

  15. identified

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

  16. monitoring

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

  17. monitoring

    We are continuing to monitor for any further issues.

  18. resolved

    This incident has been resolved.

Rewindex changes for this incident

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