Live  /  Sanity  /  Incident

Sanity: Elevated listener latency affecting Studio performance

Sanity · sanity.ioMajor incidentResolved2026-10-09 07:57 UTC
Public — what happened

Summary

Sanity reported a major incident starting at 17:49 UTC on 2026-10-08, in which delays in its listener service could slow down the Studio for some customers. As the investigation went on, the company added that Dataset embeddings might be out of date and that Functions could be slow to trigger or time out. By 19:24 UTC Sanity said Functions and listener performance were back to normal, and at 20:08 UTC it said a fix was in place while embeddings caught up, though it did not describe a cause. The incident was marked resolved on 2026-10-09 at 07:57.

Affected

Functions, Studio, Dataset Embeddings

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.