Critical impactResolvedCMS

Sanity outage: Studio, Dashboard, Content Agent, & Manage timeouts

Sanity reported this critical-impact incident on its official status page on Oct 28, 2026, 11:49 UTC. It was resolved after 4h 9m.

Right now Sanity is operational. Live Sanity status →

🔔 Get alerted when Sanity has issuesFree · email alerts · no credit card
Oct 28, 2026, 11:49 UTC
started
Oct 28, 2026, 15:57 UTC
resolved
4h 9m
duration
Critical
impact

Affected components

  • Dashboard
  • Studio
  1. resolvedOct 28, 2026, 15:57 UTC

    This incident has been resolved.

  2. monitoringOct 28, 2026, 14:09 UTC

    After two periods of disruption, between 11:49 - 12:41 UTC and 14:00 - 14:09 UTC, performance across Sanity Studio, Dashboard, Content Agent, and Manage has now stabilised. We are continuing to monitor this actively.

  3. investigatingOct 28, 2026, 11:49 UTC

    We have identified an issue affecting Sanity Studio, Dashboard, Content Agent, and parts of Manage, including the studio list and studio settings such as CORS. From 12:00 UTC, Studios and Dashboard may have been slow, failed to load, or timed out. Published content and content delivery through the Content APIs (api.sanity.io, apicdn.sanity.io, and cdn.sanity.io) are not affected. Our engineering team is actively investigating, and we will provide updates as soon as more information is available.

What APIStatus.watch saw

  • Oct 28, 2026, 11:15 UTCoperational → unknown
  • Oct 28, 2026, 11:20 UTCunknown → operational
  • Oct 28, 2026, 12:19 UTCoperational → degraded
  • Oct 28, 2026, 13:09 UTCdegraded → operational
  • Oct 28, 2026, 13:40 UTCoperational → unknown
  • Oct 28, 2026, 13:50 UTCunknown → operational

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

How often does Sanity have incidents?

Sanity reported 13 incidents in the last 90 days, 6 of them major or critical. A typical incident lasted 2h. See Sanity's uptime and incident history