Elevated API and API CDN errors and latency for some customers
Monitoring - 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.
Feb 19, 2026 - 20:19 UTC
Investigating - 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.
Feb 19, 2026 - 19:53 UTC
Uptime over the past 90 days. View historical uptime.
api.sanity.io Operational
90 days ago
100.0 % uptime
Today
apicdn.sanity.io Operational
90 days ago
100.0 % uptime
Today
cdn.sanity.io Operational
90 days ago
100.0 % uptime
Today
Authentication Operational
90 days ago
100.0 % uptime
Today
Webhooks Operational
90 days ago
100.0 % uptime
Today
GraphQL Operational
90 days ago
100.0 % uptime
Today
Content Agent Operational
90 days ago
99.95 % uptime
Today
Agent Actions Operational
90 days ago
100.0 % uptime
Today
AI Assist Operational
90 days ago
100.0 % uptime
Today
Canvas Operational
90 days ago
99.98 % uptime
Today
Media Library Operational
90 days ago
100.0 % uptime
Today
Functions Operational
90 days ago
100.0 % uptime
Today
Blueprints Operational
90 days ago
100.0 % uptime
Today
Dashboard Operational
90 days ago
100.0 % uptime
Today
Manage Operational
90 days ago
100.0 % uptime
Today
www.sanity.io Operational
90 days ago
100.0 % uptime
Today
Documentation Operational
90 days ago
100.0 % uptime
Today
Asset Pipeline Operational
90 days ago
100.0 % uptime
Today
Partner Integrations Operational
90 days ago
99.87 % uptime
Today
Dataset Management Operational
90 days ago
100.0 % uptime
Today
Studio Operational
90 days ago
99.39 % uptime
Today
SDK Operational
90 days ago
100.0 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

No incidents or maintenance related to this downtime.

Feb 19, 2026

Unresolved incident: Elevated API and API CDN errors and latency for some customers.

Feb 18, 2026
Installation issues affecting the Sanity package
Resolved - This incident has been resolved.
Feb 18, 19:43 UTC
Monitoring - The dependency maintainer has implemented a fix, and we are currently monitoring the results.
Feb 18, 19:22 UTC
Identified - We’re investigating an issue where Sanity may fail to install due to a third-party dependency.

We’ve identified the cause and have reached out to the dependency maintainer. We’ll share an update as soon as more information is available.
Feb 18, 18:45 UTC
Feb 17, 2026

No incidents reported.

Feb 16, 2026

No incidents reported.

Feb 15, 2026

No incidents reported.

Feb 14, 2026

No incidents reported.

Feb 13, 2026

No incidents reported.

Feb 12, 2026

No incidents reported.

Feb 11, 2026

No incidents reported.

Feb 10, 2026
History API inconsistencies
Resolved - The issue has been resolved. All affected customer datasets have been remediated and the service is operating normally.
Feb 10, 13:39 UTC
Monitoring - The underlying cause of the issue has been resolved. We are continuing internal monitoring and completing remediation for a small number of affected customer datasets, working directly with impacted customers as needed.
Feb 9, 16:21 UTC
Update - We are continuing to work on a fix for this issue.
Feb 9, 15:54 UTC
Update - We are continuing to work on a fix for this issue.
Feb 9, 15:12 UTC
Update - We are continuing to work on a fix for this issue.
Feb 9, 14:34 UTC
Identified - We are mitigating an issue causing inconsistencies in data returned from the History API for a subset of customers. This issue started on February 5th 2026 for the datasets created after December 9th 2025 and not mutated since until 26th January 2026, this also impacts the History view in the Sanity Studio. People may see the wrong document revision when querying by transaction ID or an inaccurate chronological order when viewing history entries. We will keep you posted as a fix is being implemented.
Feb 9, 13:50 UTC
Feb 9, 2026
Feb 8, 2026

No incidents reported.

Feb 7, 2026

No incidents reported.

Feb 6, 2026

No incidents reported.

Feb 5, 2026

No incidents reported.

← Incident History Powered by Atlassian Statuspage