Elevated listener latency and error rate impacting Studio loading
This incident has been resolved.
The latest update from Sanity.
State
Resolved
Started
24 d ago
2026-10-08 09:55 UTC
Lasted
4 h 34 min
until 2026-10-08 14:28 UTC
Worst impact
Major outage
Timeline
18 updatesInvestigating
3 h 18 min 72%
Identified
44 min 16%
Monitoring
31 min 11%
Updates
Times in UTCAs posted by Sanity
This incident has been resolved.
We are continuing to monitor for any further issues.
A fix has been fully implemented and we are monitoring the results.
We are continuing to apply fixes to mitigate the impact. No errors have been observed from the changes rolled out so far.
We are continuing to apply fixes to mitigate the impact.
The issue has been identified. We are continuing to apply fixes to mitigate its impact.
We're continuing to investigate this issue. And we are continuing to apply measures to mitigate its impact.
We're continuing to investigate this issue. And we are continuing rolling out measures to mitigate its impact.
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.
We're continuing to investigate this issue. And we are continuing rolling out preliminary measures to mitigate its impact.
We're continuing to investigate this issue. In the meantime, we've begun rolling out preliminary measures to mitigate its impact.
We are continuing to investigate this issue.
We are continuing to investigate this issue.
We are currently continuing to investigate the issue, while also preparing to roll a set of mitigations.
We are continuing to investigate the issue. Additionally, there might be a slight delay in document publishes for "scheduled publishing" functionality.
We are currently continuing to investigate the issue, while also rolling out mitigations.
We are continuing to investigate this issue.
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.
Affected components
1Sanity in the last 90 days
Full historyIncidents in 90 days
15
Days with an incident
16
Median duration
59 min
This incident
4.6× the median
Other Sanity incidents
All incidentsSanity·Studio, Dashboard, Content Agent, & Manage timeouts
This incident has been resolved.
Sanity·API & API CDN timeouts for small subset of customers
This incident has been resolved.
Sanity·API & API CDN timeouts for small subset of customers
This incident has been resolved.
Sanity·Elevated API error rates for some customers
This incident has been resolved.
Sanity·Intermittent increased API latency for some customers
This incident has been resolved.
Follow Sanity
Your coding agent knows when Sanity is down, and tells you when a failure is theirs, not yours. You can also get Sanity incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "sanity" and tell me if Sanity has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.cc/feed.xml?providers=sanity/feed subscribe https://outages.cc/feed.xml?providers=sanityFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane