outages.live
Live

Sanity

Sanity is operational

Checked 2 min ago Operational

History

90 days agoToday

Incidents in 90 days

15

Days with an incident

16

Median duration

59 min

Longest incident

22 h 6 min

Components

25
api.sanity.io Operational
90 days ago8 days with an incidentToday
apicdn.sanity.io Operational
90 days ago4 days with an incidentToday
cdn.sanity.io Operational
90 days agoNo incidentsToday
Authentication Operational
90 days agoNo incidentsToday
GraphQL Operational
90 days agoNo incidentsToday
Content Agent Operational
90 days ago1 day with an incidentToday
Agent Actions Operational
90 days agoNo incidentsToday
AI Assist Operational
90 days agoNo incidentsToday
Canvas Operational
90 days agoNo incidentsToday
Media Library Operational
90 days agoNo incidentsToday
Webhooks Operational
90 days agoNo incidentsToday
Functions Operational
90 days ago2 days with an incidentToday
Blueprints Operational
90 days agoNo incidentsToday
Dashboard Operational
90 days ago1 day with an incidentToday
Asset Pipeline Operational
90 days agoNo incidentsToday
Dataset Management Operational
90 days agoNo incidentsToday
Studio Operational
90 days ago5 days with an incidentToday
SDK Operational
90 days agoNo incidentsToday
Dataset Embeddings Operational
90 days ago2 days with an incidentToday
Partner Integrations Operational
90 days agoNo incidentsToday
Manage Operational
90 days ago1 day with an incidentToday
www.sanity.io Operational
90 days agoNo incidentsToday
Documentation Operational
90 days agoNo incidentsToday
MCP Server Operational
90 days agoNo incidentsToday

Past incidents

Provider status pageTimes in UTC

Oct 28, 2026

Duration4 h 9 min11:49 to 15:57Studio, Dashboard, Content Agent, & Manage timeoutsMajor outage

This incident has been resolved.

Oct 27, 2026

Duration6 h 54 min14:33 to 21:27API & API CDN timeouts for small subset of customersPartial outage

This incident has been resolved.

Oct 26, 2026

Duration5 min15:49 to 15:54API & API CDN timeouts for small subset of customersNotice

This incident has been resolved.

Oct 20, 2026

Duration2 h 25 min15:54 to 18:20Elevated API error rates for some customersDegraded

This incident has been resolved.

Oct 14, 2026

Duration22 h 6 min12:48 to 10:54Intermittent increased API latency for some customersDegraded

This incident has been resolved.

Oct 8, 2026

Duration13 h 30 min18:27 to 07:57Elevated listener latency affecting Studio performancePartial outage

This incident has been resolved.

Duration4 h 34 min09:55 to 14:28Elevated listener latency and error rate impacting Studio loadingMajor outage

This incident has been resolved.

Sep 23, 2026

Duration59 min10:54 to 11:53Content Agent - Elevated error ratesPartial outage

This incident has been resolved.

Sep 22, 2026

Duration1 h 36 min08:27 to 10:02Elevated listener latency impacting Studio performanceDegraded

The incident has been resolved. Further optimization work is planned as part of a broader effort.

Sep 15, 2026

Duration35 min11:46 to 12:21Elevated API ErrorsDegraded

This incident has been resolved. Error rates have returned to normal.

Sep 1, 2026

Duration16 min07:31 to 07:46Payment form not loading in ManageDegraded

This incident has been resolved.

Aug 26, 2026

Duration1 min08:00 to 08:00Elevated Embedding Index and Agentic flows Error RatesDegraded

Starting at approximating 19:51 UTC, we saw elevated error rates (HTTP 5xx) on requests to the Embeddings Index, Agent Actions and AI Assist services. The issue was identified and resolved at roughly 20:32 UTC.

Aug 20, 2026

Duration1 min14:33 to 14:33Elevated API error rateNotice

Starting at approximately 13:05–13:45 UTC, we saw elevated API error rates for a small subset of customers due to intermittent timeouts on API requests. The issue has been identified and resolved.

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

Go from tracking outages to fixing production issues with Polylane.

Try Polylane