
Sanity Incident History
Sanity is currently operational with all systems functioning normally.
Incident History
Showing incidents from the last 15 days
Report: "Elevated errors serving images and assets"
Last updateBetween 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.
Report: "Partial Live Content API outages in some regions"
Last updateBetween 18:00 and 21:00 UTC, we experienced partial outages on the Live Content API in some regions. The incident is now resolved.
Report: "Studio Connectivity Issues"
Last updateThis incident has been resolved.
A fix has been implemented and we are monitoring the results.
We are continuing to work on a fix for this issue.
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.
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 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.
Report: "Issue Viewing Webhooks"
Last updateThis incident has been resolved.
A fix has been implemented, and we are monitoring the results.
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.