Live / Sanity / Incident
Sanity: Studio & Dashboard timeouts for some customers
Sanity · sanity.ioMajor incidentResolved2026-10-28 15:57 UTC
Public — what happened
Summary
Sanity said some customers were seeing slowness, failed page loads, or timed-out requests while editing in Sanity Studio and the Dashboard, starting at 12:16 UTC on 2026-10-28. The company said published content and delivery through its Content APIs were not affected. By 13:05 UTC it reported that performance had stabilised and it was continuing to monitor, and the incident was marked resolved at 15:57 UTC. The status text did not name a cause.
Affected
Dashboard, Studio
Timeline
- Started — 2026-10-28 12:16 UTC
- Investigating — 2026-10-28 12:16 UTC
- Monitoring — 2026-10-28 13:05 UTC
- Resolved — 2026-10-28 15:57 UTC · 3h 42m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Sanity against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Sanity: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Sanity report →
More from Sanity
Covered in The Squid’s Ink, Week 45, 2026, our weekly internet health report.