Live  /  Sanity  /  Incident

Sanity: Elevated listener latency and error rate impacting Studio loading

Sanity · sanity.ioCritical outageResolved2026-10-08 14:28 UTC
Public — what happened

Summary

Sanity reported a critical incident in which slow listener response times caused lag and sluggish loading in Sanity Studio for some of its customers, with the company saying the problem began around 9:10 UTC on 2026-10-08. During the investigation it briefly warned that scheduled publishing might see small delays, but later said that feature was not affected. Sanity said it had identified the issue at 13:13 UTC but did not describe a cause, and it rolled out a series of mitigations through the morning and early afternoon. A fix was fully in place by 13:57 UTC, and the incident was marked resolved at 14:28.

Affected

Studio

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 42, 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.