Studio, Dashboard, Content Agent, & Manage timeouts

What to do

• Check whether you use Sanity Dashboard, Studio. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 4h 9m it lasted.

  Anything that failed between 2026-10-28 11:49 UTC and 2026-10-28 15:57 UTC may need a replay.

• Subscribe to Sanity's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=sanity works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Sanity 3

1. investigatingOct 28, 2026, 11:49 AM 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.

   provider

2. monitoringOct 28, 2026, 2:09 PM 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.

   provider

3. resolvedOct 28, 2026, 3:57 PM UTC

   This incident has been resolved.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.