Sanity Outage History

Between 14:56 and 15:16 UTC, we observed a slight increase in 524 error rates for a small subset of customers. The error rates have returned to normal, though we continue to investigate the cause.

We are investigating intermittent increased latency affecting API requests for a small subset of customers. Some requests may also have returned errors. Most customers are unaffected. Our engineers have identified the cause and have taken steps to reduce the impact while we continue to investigate. We will post another update as soon as we have more information.

We are investigating an issue of elevated listener latency, which may cause performance issues in the Studio for some customers.

We are investigating an issue of elevated listener latency, which may cause performance issues in the Studio for some customers. Dataset embeddings may be stale at this time.

We are investigating an issue of elevated listener latency, which may cause performance issues in the Studio for some customers. Dataset embeddings may be stale at this time. The triggering of Functions may be delayed or time out.

We are aware of an issue with the Content Agent where responses are not being delivered back to the user. We are investigating and will provide an update shortly.

We are continuing to investigate this issue.

We are continuing to investigate this issue.

We are currently investigating an issue where elevated listener latency may result in slower performance and lag within Sanity Studio for a small subset of customers. Our team is actively working to identify the root cause and mitigate the impact. Issue started around 7:40 UTC. We’ll provide further updates as more information becomes available.

We are currently continuing to investigate the issue.

The issue should not affect the performance of any Studios anymore. We are continuing to investigate the issue.

We have had another occurrence of listener latency. We are continuing to investigate the issue.

Some of our users may be experiencing an elevated level of API errors. We are currently looking into the issue.

We are investigating elevated error rates affecting write requests (mutations) for a subset of projects, starting at approximately 11:20 UTC today. Affected users may see intermittent errors or slower response times when creating, updating, or publishing documents, including from Sanity Studio.

We are continuing to investigate this issue.

Starting at approximately 14:30 UTC, we have seen elevated API and API CDN error rates. We are currently investigating the issue.

We are investigating reports of connectivity issues affecting Sanity Studio. Some users may experience the Studio getting stuck on "Trying to connect" or failing to load. Our engineering team is actively investigating the issue and we will provide updates as soon as more information is available.

We have identified that the issue has recurred for some users after the earlier mitigation. Our engineering team is actively investigating the remaining connectivity issues and working to restore full service. We will continue to provide updates as more information becomes available.

We're currently investigating an issue where the Webhooks page fails to load webhook data. This does not affect webhook delivery. Webhooks configured on your project will continue to fire as expected.

We are currently investigating an issue causing slower-than-expected query performance for some customers. A subset of users may experience increased latency when querying content. Our team is actively investigating the issue and working to mitigate the impact. We will provide further updates as more information becomes available.

We are aware of an issue with the Content Agent in Dashboard where a small number of responses in longer-running threads may not be delivered to the user. We are investigating and will provide an update shortly.

We’re investigating an issue with the MCP server (mcp.sanity.io) returning 500 errors. This may impact access via tools like Claude, Cursor, and other MCP-compatible clients. Updates to follow.

Our MCP server is currently inoperative. We are working to restore functionality.