Sanity Status
Real-time updates of Sanity issues and outages
Sanity status is Operational
Sanity api.sanity.io
Sanity Studio
Sanity Manage
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.
Active Incidents
No active incidents
Recently Resolved Incidents
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.
Sanity Outage Survival Guide
Sanity Components
Sanity api.sanity.io
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.
Sanity apicdn.sanity.io
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
Sanity Asset Pipeline
Sanity Dataset Management
Sanity Studio
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.
Sanity SDK
Sanity Dataset Embeddings
Sanity Partner Integrations
Sanity Manage
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.