Sanity incident: Elevated API and API CDN error rate for some customers

Affected components

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

1. resolvedNov 6, 2025, 10:34 UTC

   This incident has been resolved.

2. monitoringNov 6, 2025, 09:47 UTC

   A fix has been implemented and error rates have returned to normal as of 09:40 UTC. We continue monitoring results.

3. investigatingNov 6, 2025, 09:27 UTC

   We are continuing to investigate the issue.

4. investigatingNov 6, 2025, 09:07 UTC

   While error rates have improved we are still seeing elevated numbers and are continuing to investigate this issue.

5. investigatingNov 6, 2025, 08:40 UTC

   We are currently investigating an increase in API and API CDN errors and latency impacting a small 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.

• Confluent Cloud: Availability issues for Kafka clusters in Azure West EuropeMajor · Nov 5, 2025, 18:19 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