
Sanity Status
Real-time updates of Sanity issues and outages
Sanity status is Operational
Sanity api.sanity.io
Sanity apicdn.sanity.io
Sanity Dashboard
Sanity Studio
Active Incidents
No active incidents
Recently Resolved Incidents
We have identified an issue affecting Sanity Studio, Dashboard, Content Agent, and parts of Manage, including the studio list and studio settings such as CORS. From 12:00 UTC, Studios and Dashboard may have been slow, failed to load, or timed out. Published content and content delivery through the Content APIs (api.sanity.io, apicdn.sanity.io, and cdn.sanity.io) are not affected. Our engineering team is actively investigating, and we will provide updates as soon as more information is available.
Since 13:37UTC, a small subset of customers have been seeing intermittent increased latency on API requests, and some requests are returning errors. Most customers are not affected. Our engineers are investigating the cause and working to resolve it. We will post another update as soon as we have more information.
From 13:12 to 15:13 UTC, a small subset of customers experienced intermittent increased latency on API requests, and some requests returned errors. Most customers were unaffected. Our engineers identified the cause and took steps to resolve it, and API performance has been back to normal since 15:07 UTC, and we are continued to monitor the results.
Sanity Outage Survival Guide
You're checking on Sanity - but is your own site converting?
Outages aren't the only thing that costs you visitors.
Get a visual audit that shows exactly where your site loses conversions.
Free, takes 2 minutes.
Sanity Components
Sanity api.sanity.io
From 13:12 to 15:13 UTC, a small subset of customers experienced intermittent increased latency on API requests, and some requests returned errors. Most customers were unaffected. Our engineers identified the cause and took steps to resolve it, and API performance has been back to normal since 15:07 UTC, and we are continued to monitor the results.
Since 13:37UTC, a small subset of customers have been seeing intermittent increased latency on API requests, and some requests are returning errors. Most customers are not affected. Our engineers are investigating the cause and working to resolve it. We will post another update as soon as we have more information.
Sanity apicdn.sanity.io
From 13:12 to 15:13 UTC, a small subset of customers experienced intermittent increased latency on API requests, and some requests returned errors. Most customers were unaffected. Our engineers identified the cause and took steps to resolve it, and API performance has been back to normal since 15:07 UTC, and we are continued to monitor the results.
Since 13:37UTC, a small subset of customers have been seeing intermittent increased latency on API requests, and some requests are returning errors. Most customers are not affected. Our engineers are investigating the cause and working to resolve it. We will post another update as soon as we have more information.
Sanity cdn.sanity.io
Sanity Authentication
Sanity GraphQL
Sanity Content Agent
Sanity Agent Actions
Sanity Datasets
Sanity Studio
Sanity AI Assist
Sanity Canvas
Sanity Media Library
Sanity Webhooks
Sanity Functions
Sanity Blueprints
Sanity Dashboard
We have identified an issue affecting Sanity Studio, Dashboard, Content Agent, and parts of Manage, including the studio list and studio settings such as CORS. From 12:00 UTC, Studios and Dashboard may have been slow, failed to load, or timed out. Published content and content delivery through the Content APIs (api.sanity.io, apicdn.sanity.io, and cdn.sanity.io) are not affected. Our engineering team is actively investigating, and we will provide updates as soon as more information is available.
Sanity Asset Pipeline
Sanity Dataset Management
Sanity Studio
We have identified an issue affecting Sanity Studio, Dashboard, Content Agent, and parts of Manage, including the studio list and studio settings such as CORS. From 12:00 UTC, Studios and Dashboard may have been slow, failed to load, or timed out. Published content and content delivery through the Content APIs (api.sanity.io, apicdn.sanity.io, and cdn.sanity.io) are not affected. Our engineering team is actively investigating, and we will provide updates as soon as more information is available.