Changes / Sanity / Elevated listener latency and error rate impacting Studio loading

Sanity: Critical incident: Elevated listener latency and error rate impacting Studio loading

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 diff below (Sol; type: incident degradation). Check the diff before relying on it.

Major incidentLabel: degradation (model (Jev), 81%)Changed Detected Source: stspg.io

What changed

AddedTitle#1
Before: not present
After: Elevated listener latency and error rate impacting Studio loading
AddedImpact#2
Before: not present
After: critical
AddedStatus#3
Before: not present
After: resolved
AddedStart time#4
Before: not present
After: 2026-10-08 09:55 UTC
AddedResolved time#5
Before: not present
After: 2026-10-08 14:28 UTC
AddedAffected components#6
Before: not present
After: Studio
AddedUpdateinvestigating#7
Before: not present
After: 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.
AddedUpdateinvestigating#8
Before: not present
After: We are continuing to investigate this issue.
AddedUpdateinvestigating#9
Before: not present
After: We are currently continuing to investigate the issue, while also rolling out mitigations.
AddedUpdateinvestigating#10
Before: not present
After: We are continuing to investigate the issue. Additionally, there might be a slight delay in document publishes for "scheduled publishing" functionality.
AddedUpdateinvestigating#11
Before: not present
After: We are currently continuing to investigate the issue, while also preparing to roll a set of mitigations.
AddedUpdateinvestigating#12
Before: not present
After: We are continuing to investigate this issue.
AddedUpdateinvestigating#13
Before: not present
After: We are continuing to investigate this issue.
AddedUpdateinvestigating#14
Before: not present
After: We're continuing to investigate this issue. In the meantime, we've begun rolling out preliminary measures to mitigate its impact.
AddedUpdateinvestigating#15
Before: not present
After: We're continuing to investigate this issue. And we are continuing rolling out preliminary measures to mitigate its impact.
AddedUpdateinvestigating#16
Before: not present
After: 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.
AddedUpdateinvestigating#17
Before: not present
After: We're continuing to investigate this issue. And we are continuing rolling out measures to mitigate its impact.
AddedUpdateinvestigating#18
Before: not present
After: We're continuing to investigate this issue. And we are continuing to apply measures to mitigate its impact.
AddedUpdateidentified#19
Before: not present
After: The issue has been identified. We are continuing to apply fixes to mitigate its impact.
AddedUpdateidentified#20
Before: not present
After: We are continuing to apply fixes to mitigate the impact.
AddedUpdateidentified#21
Before: not present
After: We are continuing to apply fixes to mitigate the impact. No errors have been observed from the changes rolled out so far.
AddedUpdatemonitoring#22
Before: not present
After: A fix has been fully implemented and we are monitoring the results.
AddedUpdatemonitoring#23
Before: not present
After: We are continuing to monitor for any further issues.
AddedUpdateresolved#24
Before: not present
After: This incident has been resolved.

First version of this incident archived by Rewindex. View the live incident.

History of this incident

When (UTC)ChangeKind
Critical incident: Elevated listener latency and error rate impacting Studio loading (this change)
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.
Major incident

All Sanity changes → · Sanity profile · Markdown · JSON