Sanity logo and current status indicator

Sanity Incident History

Operational

sanity.io ↗25 components

checked Nov 1, 2026 3:54 AM UTC · Sanity's official status page

Sanity is up and running.

Sanity is currently operational with all systems functioning normally.

All components operational

Be the first to know

Statusfield watches Sanity alongside the rest of your stack and tells you when its status changes. Email, Slack, Microsoft Teams, PagerDuty, and webhooks.

30-day free trial — no card needed. First-time customers; continued monitoring requires a paid subscription.

Sanity incident history

7 reports published by Sanity in the last 30 days

When Sanity breaks, it is typically resolved in 6h 11m — median across 6 resolved incidents over 30 days.

October 28, 2026

Studio, Dashboard, Content Agent, & Manage timeouts

Last update
  1. resolvedOct 28 · 15:57 UTC

    This incident has been resolved.

Reported by Sanity on their status page.

October 27, 2026

API & API CDN timeouts for small subset of customers

Last update
  1. resolvedOct 27 · 21:27 UTC

    This incident has been resolved.

Reported by Sanity on their status page.

October 26, 2026

API & API CDN timeouts for small subset of customers

Last update
  1. resolvedOct 26 · 15:54 UTC

    This incident has been resolved.

Reported by Sanity on their status page.

October 20, 2026

Elevated API error rates for some customers

Last update
  1. resolvedOct 20 · 18:20 UTC

    This incident has been resolved.

Reported by Sanity on their status page.

October 14, 2026

Intermittent increased API latency for some customers

Last update
  1. resolvedOct 15 · 10:54 UTC

    This incident has been resolved.

Reported by Sanity on their status page.

October 8, 2026

Elevated listener latency affecting Studio performance

Last update
  1. resolvedOct 9 · 07:57 UTC

    This incident has been resolved.

Reported by Sanity on their status page.

Elevated listener latency and error rate impacting Studio loading

Last update
  1. resolvedOct 8 · 14:28 UTC

    This incident has been resolved.

Reported by Sanity on their status page.