Sanity incident: Elevated API and API CDN errors and latency for some customers

Affected components

• api.sanity.io
• apicdn.sanity.io

1. resolvedFeb 3, 2026, 21:17 UTC

   This incident has been resolved.

2. monitoringFeb 3, 2026, 16:34 UTC

   We've identified and mitigated the root cause of the issue. Performance has been stable since 16:17 UTC with no elevated error rates, and we are continuing to monitor.

3. investigatingFeb 3, 2026, 16:06 UTC

   We are currently investigating an increase in API and API CDN errors and latency impacting a subset of customers. We are actively mitigating impact while working to identify the issue.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Sanity's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• 1Password: Sign-in failure in some cases due to 2FA prompt not appearingMinor · Jan 23, 2026, 20:33 UTC
• Imgix: Asset Manager errors when uploading to an Azure SourceMinor · Feb 3, 2026, 13:49 UTC
• Render: Degraded deploys in Ohio and VirginiaMinor · Feb 3, 2026, 15:30 UTC

How often does Sanity have incidents?

Sanity reported 10 incidents in the last 90 days, 3 of them major or critical. A typical incident lasted 52 min. See Sanity's uptime and incident history