outages.live
Live
SanityIncident · 2026-10-28 11:49 UTC

Studio, Dashboard, Content Agent, & Manage timeouts

ResolvedOfficial update

This incident has been resolved.

The latest update from Sanity.

State

Resolved

Started

4 d ago

2026-10-28 11:49 UTC

Lasted

4 h 9 min

until 2026-10-28 15:57 UTC

Worst impact

Major outage

Timeline

3 updates
11:4912:5113:5314:5515:57
Major outageUpdate postedTimes in UTC

Investigating

2 h 20 min 56%

Monitoring

1 h 49 min 44%

Updates

Times in UTC

As posted by Sanity

Resolved2026-10-28 15:57 UTC

This incident has been resolved.

Monitoring2026-10-28 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.

Investigating2026-10-28 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.

Affected components

2
DashboardStudio

Sanity in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

15

Days with an incident

16

Median duration

59 min

This incident

4.2× the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

22 h 6 min
median 59 min
90 days agoToday

Other Sanity incidents

All incidents

Sanity·API & API CDN timeouts for small subset of customers

This incident has been resolved.

Resolvedresolved 5 d ago

Sanity·API & API CDN timeouts for small subset of customers

This incident has been resolved.

Resolvedresolved 6 d ago

Sanity·Elevated API error rates for some customers

This incident has been resolved.

Resolvedresolved 12 d ago

Sanity·Intermittent increased API latency for some customers

This incident has been resolved.

Resolvedresolved 17 d ago

Sanity·Elevated listener latency affecting Studio performance

This incident has been resolved.

Resolvedresolved 23 d ago

Follow Sanity

Your coding agent knows when Sanity is down, and tells you when a failure is theirs, not yours. You can also get Sanity incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "sanity" and tell me if Sanity has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.cc/feed.xml?providers=sanity
Slack
/feed subscribe https://outages.cc/feed.xml?providers=sanity

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane