Sanity Outage History

The Sanity MCP server (mcp.sanity.io) experienced 500 errors that impacted access through MCP-compatible clients including Claude and Cursor. The incident lasted 5 minutes and was under investigation.

Sanity's MCP server (mcp.sanity.io) experienced a major outage for 1.4 hours, returning 500 errors and preventing access through tools like Claude and Cursor. The team identified the root cause and implemented a fix, with service fully restored after a brief monitoring period.

Sanity Studio experienced an issue where some users encountered failures when loading documents and document lists. The problem affected the core document management functionality within the Studio interface. The incident was resolved after 6.2 hours of investigation and remediation efforts.

Sanity's Asset CDN (cdn.sanity.io) experienced elevated 5xx error rates starting at 12:47 UTC, causing customers to encounter failures when requesting images. The issue was identified, a fix was implemented and monitored, and the incident was fully resolved after 2.8 hours.

The sales contact form on Sanity's website (www.sanity.io) became inoperative, preventing users from submitting sales inquiries. The issue was identified and investigated by the Sanity team. The incident was resolved after 20 minutes of downtime.

Sanity experienced elevated error rates affecting asset uploads for some customers, impacting the Asset Pipeline component. The incident lasted 1 hour, with error levels returning to normal and the issue being fully resolved after monitoring confirmed stability.

Sanity experienced elevated listener latency that caused slower performance and lag within Sanity Studio for some customers, affecting the api.sanity.io component. The team implemented a fix and monitored the results over 6.1 hours before resolving the issue and addressing underlying causes.