Sanity had 45 outages in the last 2 years totaling 39h 15m of downtime — averaging 1.8 incidents per month.
There were 45 Sanity outages since September 10, 2025 totaling 39h 15m of downtime. Each is summarised below — incident details, duration, and resolution information.
Starting at approximating 19:51 UTC, we saw elevated error rates (HTTP 5xx) on requests to the Embeddings Index service. The issue was identified and resolved at roughly 20:32 UTC.
Starting at approximately 13:25–13:30 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.
Some customers experienced intermittent Studio connectivity issues between approximately 07:25 and 07:45 UTC on August 17. The issue has been resolved and services have returned to normal operation.
Starting at approximately 14:30 UTC, we have seen elevated API and API CDN error rates. We are currently investigating the issue.
A fix was implemented and service rates returned to normal at 14:40 UTC. The period of elevated error rates was identified to have started at 14:34 UTC. We are continuing to monitor.
This incident has been resolved.
Between approximately 09:25 and 09:45 UTC on August 6, some requests to api.sanity.io and apicdn.sanity.io returned errors or timed out for a small subset of customers. The issue has been resolved and API services have returned to normal operation.
Between approximately 23:16 UTC on July 24 and 00:10 UTC on July 25, some requests for images and assets served from cdn.sanity.io returned errors or loaded slowly for users in North America and Europe. Image and asset delivery has since returned to normal operation. The Content APIs (api.sanity.io, apicdn.sanity.io) and Studio editing were not affected.
Between 18:00 and 21:00 UTC, we experienced partial outages on the Live Content API in some regions. The incident is now resolved.
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.
A fix has been implemented and we are monitoring the results.
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.
A fix has been implemented and we are monitoring the results.
We've identified a recurrence of the issue affecting additional services. Our engineering team is actively implementing further mitigation and investigating the remaining impact. We will continue to provide updates as they become available.
We are continuing to work on a fix for this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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.
A fix has been implemented, and we are monitoring the results.
This incident has been resolved.
A small subset of customers experienced increased query latency and intermittent timeouts during this incident. Our engineering team identified the issue, implemented mitigations, and restored normal query performance. The incident has been resolved.
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.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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.
The issue has been identified and we are working on a fix.
A fix has been implemented and we are monitoring the results.
This incident has now been resolved.
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.
We are implementing a fix that should resolve the issue.
We’ve identified the issue affecting the MCP server (mcp.sanity.io) and are actively working on a fix. We’ll share another update as soon as we have more information.
We are continuing to work on a fix for this issue.
We are continuing to work on a fix for this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Between 06:01 and 06:35 UTC today, some users encountered errors when attempting to create organizations, create projects, or make plan changes. This was caused by an internal service configuration issue that has since been rolled back.
Between approximately 06:35 and 06:52 UTC today, some users may have experienced issues loading Sanity Studio. This was caused by a temporary service disruption in our infrastructure. The issue is resolved and a fix has been deployed to prevent recurrence.
Between 14:14 UTC and 14:20 UTC, we observed elevated error rates on our API for some customers. The issue has since been resolved and all systems are operating normally.
We’re currently investigating an issue affecting Sanity Studio where some users may see documents and document lists fail to load.
We’ve taken steps to address an issue affecting Sanity Studio where some users experienced documents and document lists failing to load, and are continuing to monitor the situation closely.
This incident has been resolved.
Starting 12:47 UTC, we are experiencing a sustained error rate on the Asset CDN. Some customers will be seeing elevated rates of 5xx errors when requesting images during this time.
The issue has been identified and we are working on a fix.
A fix has been implemented and we are monitoring results.
This incident has been resolved.
We are currently investigating an issue with account logins via SAML SSO. This is not affecting the email/password login flow.
We are continuing to investigate this issue.
We are continuing to investigate this issue.
We are continuing to investigate this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Our sales contact form on www.sanity.io is currently inoperative. We are working to restore functionality.
This incident has been resolved.
Resolved: Between 16:00–23:10 UTC, a subset of customers experienced elevated API CDN latency. The issue has been mitigated and performance is back to normal.
We are aware of elevated errors with the uploading of assets for some customers, and are currently investigating.
We can see that error levels have returned to normal, and are continuing to monitor.
We are continuing to monitor for any further issues.
This incident has been resolved.
We are currently investigating an issue where elevated listener latency may result in slower performance and lag within Sanity Studio for some customers. Our team is actively working to identify the root cause and mitigate the impact. We’ll provide further updates as more information becomes available.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
We are continuing to monitor for any further issues.
The incident has been resolved
We are currently investigating an increase in API and API CDN errors and latency impacting a subset of customers. We are actively mitigating the impact while working to identify the issue.
We've identified and mitigated the issue. Performance has been stable since 19:46 UTC with no elevated error rates, and we are continuing to monitor.
This incident has been resolved.