Live / Sanity / Incident
Sanity: Intermittent increased API latency for some customers
Sanity · sanity.ioMinor incidentResolved2026-10-15 10:54 UTC
Public — what happened
Summary
Sanity said a small portion of its customers saw API requests slow down at times beginning on 2026-10-14 at 12:48 UTC, and some of those requests may have failed with errors, while most customers were not affected. The company said its engineers had found the cause, though it did not describe it, and had worked to limit the impact while looking into the problem further. By 13:44 UTC Sanity reported that a fix was in place and it was watching the results. The incident was marked resolved on 2026-10-15 at 10:54.
Affected
api.sanity.io
Timeline
- Started — 2026-10-14 12:48 UTC
- Investigating — 2026-10-14 12:48 UTC
- Monitoring — 2026-10-14 13:44 UTC
- Resolved — 2026-10-15 10:54 UTC · 22h 06m 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 43, 2026, our weekly internet health report.