Elevated listener latency affecting Studio performance
This incident has been resolved.
The latest update from Sanity.
State
Resolved
Started
24 d ago
2026-10-08 18:27 UTC
Lasted
13 h 30 min
until 2026-10-09 07:57 UTC
Worst impact
Partial outage
Timeline
6 updatesInvestigating
57 min 7%
Identified
44 min 5%
Monitoring
11 h 49 min 88%
Updates
Times in UTCAs posted by Sanity
This incident has been resolved.
A fix has been fully implemented, and we are monitoring results. Some users may see stale Dataset Embeddings while processing catches up.
The triggering of Functions and listener performance have returned to normal. Dataset embeddings may continue to be stale for some customers.
We are investigating an issue of elevated listener latency, which may cause performance issues in the Studio for some customers. Dataset embeddings may be stale at this time. The triggering of Functions may be delayed or time out.
We are investigating an issue of elevated listener latency, which may cause performance issues in the Studio for some customers. Dataset embeddings may be stale at this time.
We are investigating an issue of elevated listener latency, which may cause performance issues in the Studio for some customers.
Affected components
3Sanity in the last 90 days
Full historyIncidents in 90 days
15
Days with an incident
16
Median duration
59 min
This incident
14× 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