Elevated listener latency impacting Studio performance
The incident has been resolved. Further optimization work is planned as part of a broader effort.
The latest update from Sanity.
State
Resolved
Started
40 d ago
2026-09-22 08:27 UTC
Lasted
1 h 36 min
until 2026-09-22 10:02 UTC
Worst impact
Degraded
Timeline
6 updatesInvestigating
1 h 6 min 69%
Monitoring
30 min 31%
Updates
Times in UTCAs posted by Sanity
The incident has been resolved. Further optimization work is planned as part of a broader effort.
We have identified the core issue and planning to roll out a set of updates to mitigate the problem. Studio performance should not be affected anymore. We are monitoring the incident now.
We have had another occurrence of listener latency. We are continuing to investigate the issue.
The issue should not affect the performance of any Studios anymore. We are continuing to investigate the issue.
We are currently continuing to investigate the issue.
We are currently investigating an issue where elevated listener latency may result in slower performance and lag within Sanity Studio for a small subset of customers. Our team is actively working to identify the root cause and mitigate the impact. Issue starting around 7:40 UTC. We’ll provide further updates as more information becomes available.
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
1.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