outages.live
Live
SanityIncident · 2026-10-26 15:49 UTC

API & API CDN timeouts for small subset of customers

ResolvedOfficial update

This incident has been resolved.

The latest update from Sanity.

State

Resolved

Started

6 d ago

2026-10-26 15:49 UTC

Lasted

5 min

until 2026-10-26 15:54 UTC

Worst impact

Notice

Timeline

2 updates
15:4915:5015:5115:5215:54
NoticeUpdate postedTimes in UTC

Monitoring

5 min 100%

Updates

Times in UTC

As posted by Sanity

Resolved2026-10-26 15:54 UTC

This incident has been resolved.

Monitoring2026-10-26 15:49 UTC

From 13:12 to 15:13 UTC, a small subset of customers experienced intermittent increased latency on API requests, and some requests returned errors. Most customers were unaffected. Our engineers identified the cause and took steps to resolve it, and API performance has been back to normal since 15:07 UTC, and we are continued to monitor the results.

Affected components

2
api.sanity.ioapicdn.sanity.io

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

92% shorter than 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·Studio, Dashboard, Content Agent, & Manage timeouts

This incident has been resolved.

Resolvedresolved 4 d ago

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

This incident has been resolved.

Resolvedresolved 5 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 24 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