Live / Sanity / Incident
Sanity: API & API CDN timeouts for small subset of customers
Sanity · sanity.ioMajor incidentResolved2026-10-27 21:27 UTC
Public — what happened
Summary
Sanity said a small number of its customers saw slower responses and some errors when making API requests, with most customers unaffected. The company's first post, at 14:33 UTC on 2026-10-27, said the trouble had begun at 13:37 UTC. By 15:48 UTC Sanity said it had identified the problem and was working on a fix, and at 18:54 UTC it said the fix was in place and it was watching the results. The incident was marked resolved at 21:27 UTC.
Affected
api.sanity.io, apicdn.sanity.io
Timeline
- Started — 2026-10-27 14:33 UTC
- Investigating — 2026-10-27 14:33 UTC (2 updates)
- Identified — 2026-10-27 15:48 UTC
- Monitoring — 2026-10-27 18:54 UTC
- Resolved — 2026-10-27 21:27 UTC · 6h 54m 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.