Elevated listener latency and error rate impacting Studio loading
Resolved
Critical impact
Updates
Resolved
This incident has been resolved.
Monitoring
We are continuing to monitor for any further issues.
Monitoring
A fix has been fully implemented and we are monitoring the results.
Identified
We are continuing to apply fixes to mitigate the impact. No errors have been observed from the changes rolled out so far.
Identified
We are continuing to apply fixes to mitigate the impact.
Identified
The issue has been identified. We are continuing to apply fixes to mitigate its impact.
Investigating
We're continuing to investigate this issue. And we are continuing to apply measures to mitigate its impact.
Investigating
We're continuing to investigate this issue. And we are continuing rolling out measures to mitigate its impact.
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.
Investigating
We're continuing to investigate this issue. And we are continuing rolling out preliminary measures to mitigate its impact.
Investigating
We're continuing to investigate this issue. In the meantime, we've begun rolling out preliminary measures to mitigate its impact.
Investigating
We are continuing to investigate this issue.
Investigating
We are continuing to investigate this issue.
Investigating
We are currently continuing to investigate the issue, while also preparing to roll a set of mitigations.
Investigating
We are continuing to investigate the issue. Additionally, there might be a slight delay in document publishes for "scheduled publishing" functionality.
Investigating
We are currently continuing to investigate the issue, while also rolling out mitigations.
Investigating
We are continuing to investigate this issue.
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.