Sanity: Studio, Dashboard, Content Agent, & Manage timeouts
Sanity raised the timeout incident’s impact from major to critical and updated its title to include Content Agent and Manage alongside Studio and Dashboard, removing “for some customers.” The edit provides no start time, duration, cause, or fix.
Machine-written from the archived incident (Sol). Check the timeline before relying on it.
Affected components: DashboardStudio
Timeline of updates
- investigating
We have identified an issue affecting Sanity Studio, Dashboard, Content Agent, and parts of Manage, including the studio list and studio settings such as CORS. From 12:00 UTC, Studios and Dashboard may have been slow, failed to load, or timed out. Published content and content delivery through the Content APIs (api.sanity.io, apicdn.sanity.io, and cdn.sanity.io) are not affected. Our engineering team is actively investigating, and we will provide updates as soon as more information is available.
- investigatingDeleted by the vendor
We are investigating reports of timeouts affecting Sanity Studio & Dashboard. Some users may find that the Studio & Dashboard is slow or failing to load or that requests time out while editing. Published content and content delivery through the Content APIs (api.sanity.io and apicdn.sanity.io) are not affected. Our engineering team is actively investigating, and we will provide updates as soon as more information is available.
- monitoringDeleted by the vendor
Performance has now stabilised, and we are continuing to monitor this actively.
- monitoring
After two periods of disruption, between 11:49 - 12:41 UTC and 14:00 - 14:09 UTC, performance across Sanity Studio, Dashboard, Content Agent, and Manage has now stabilised. We are continuing to monitor this actively.
- resolved
This incident has been resolved.
Changes Rewindex caught on this incident
- Critical incident: Studio & Dashboard timeouts for some customers
- Incident silently edited: Studio & Dashboard timeouts for some customers
- Incident updated: Studio & Dashboard timeouts for some customers
- Incident updated: Studio & Dashboard timeouts for some customers
- Incident updated: Studio & Dashboard timeouts for some customers
- Incident silently edited: Studio, Dashboard, Content Agent, & Manage timeouts
- Incident updated: Studio, Dashboard, Content Agent, & Manage timeouts
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves these records existed by then and have not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-10-28 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
254b0854110e362c…Version 2 captured
In the 2026-10-28 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
2228b15d9fb1723d…Version 3 captured
In the 2026-10-28 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
e36940814641d2fe…Version 4 captured
In the 2026-10-28 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
a470319b3d007391…Version 5 captured
In the 2026-10-29 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
3951e255295f81b6…Version 6 captured
In the 2026-10-29 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
78c2949e8a7ccbe4…Version 7 captured
In the 2026-10-29 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
1ec5724d7889b0cf…
Impact, status and times are the vendor’s own, as last archived. View on www.sanity-status.com (opens in new tab).
Cite this
Status incident (vendor impact label: critical) posted by Sanity, started 2026-10-28 12:16 UTC, resolved after 3.7 h, 5 update(s); edited after publishing.
- Title
- Studio, Dashboard, Content Agent, & Manage timeouts
- Vendor
- Sanity
- Date
- URL
- https://rewindex.com/company/sanity/incidents/vwb8tnd29lck
Sanity profileRecent Sanity incidentsAll outages on October 28, 2026Sanity in October 2026MarkdownJSON