Live  /  Sanity  /  Incident

Sanity: Elevated API error rates for some customers

Sanity · sanity.ioMinor incidentResolved2026-10-20 17:38 UTC
Public — what happened

Summary

Sanity said a small group of its customers saw a slight rise in 524 errors on its API between 14:56 and 15:16 UTC on 2026-10-20. The company reported that error rates had gone back to normal by the time it posted its first update at 15:54 UTC, while it kept looking into what happened. At 16:25 UTC Sanity said it had put in place a fix meant to prevent such errors in future and was watching the rollout, and the incident was marked resolved at 17:38 UTC.

Affected

api.sanity.io

As listed on Sanity’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

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 see
Customers 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 44, 2026, our weekly internet health report.

The full archive is on the Sanity status & history page.

Related: Sanity status & history. SquidGrid is not affiliated with Sanity.