Sanity change history

Sanity reported a major degradation starting 2026-10-08 18:27 UTC, lasting 13 h 29 min and resolved at 2026-10-09 07:57 UTC. Elevated listener latency affected Studio performance for some customers; Dataset Embeddings could be stale, and Functions triggering could be delayed or time out. Sanity reported a fix fully implemented at 10-08 20:08 UTC while embedding processing caught up.

Sanity reported critical elevated listener latency and error rates affecting Studio loading, with slower performance and lag for some customers. The recorded incident ran from 2026-10-08 09:55 UTC to 2026-10-08 14:28 UTC (4 h 33 min), though Sanity noted issues began around 9:10 UTC. A fix was fully implemented and the incident resolved.

Sanity’s Content Agent failed to deliver responses to users in a major-impact incident starting 2026-09-23 10:54 UTC and lasting 59 min, until resolution at 2026-09-23 11:53 UTC. Sanity implemented a fix at 09-23 11:23 UTC and monitored the results before resolving the incident.

Sanity reported a major incident affecting api.sanity.io and apicdn.sanity.io, with elevated error rates identified from 14:34 UTC until a fix restored normal rates at 14:40 UTC. The incident record started at 2026-08-14 14:46 UTC and was resolved at 2026-08-14 15:32 UTC; its recorded duration was 45 min.

Sanity reported a major incident affecting api.sanity.io and Studio, with some users stuck on "Trying to connect" or unable to load Studio. It started at 2026-07-22 12:38 UTC and lasted 5 h 27 min, resolving at 2026-07-22 18:05 UTC; after a recurrence affecting additional services, Sanity implemented a fix.

Sanity reported major query performance degradation affecting a small subset of customers, with increased latency and intermittent timeouts. The recorded start, 2026-06-26 09:53 UTC, is after the recorded resolution, 2026-06-25 20:30 UTC; duration is unknown. Engineering implemented mitigations and restored normal query performance.

Sanity reported a major query-performance degradation affecting some customers across apicdn.sanity.io, api.sanity.io, and GraphQL, increasing content-query latency. It started at 2026-06-15 06:15 UTC and was resolved at 2026-06-15 10:24 UTC, lasting 4 h 9 min; a fix was implemented and monitored.

Sanity’s MCP server (mcp.sanity.io) returned 500 errors, disrupting access through tools such as Claude and Cursor in a major-impact outage. It started at 2026-05-01 12:00 UTC and was resolved at 2026-05-01 13:19 UTC; the reported duration was 1 h 18 min. Sanity implemented a fix and monitored results before resolution.

Sanity reported a major Asset CDN (cdn.sanity.io) incident causing elevated image-request 5xx errors for some customers from 12:47 UTC. The incident was logged at 2026-03-22 13:58 UTC and resolved at 2026-03-22 16:42 UTC, with a recorded duration of 2 h 43 min. A fix was implemented at 14:48 UTC.

Sanity reported a major Authentication outage affecting SAML SSO account logins; email/password login was unaffected. It started at 2026-03-12 12:11 UTC and was resolved at 2026-03-12 13:49 UTC, lasting 1 h 38 min. A fix was implemented at 13:22 UTC; no cause was stated.