Minor impactResolvedCMS

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

Sanity reported this minor-impact incident on its official status page on Jan 20, 2026, 08:19 UTC. It was resolved after 50 min.

Right now Sanity is operational. Live Sanity status →

🔔 Get alerted when Sanity has issuesFree · email alerts · no credit card
Jan 20, 2026, 08:19 UTC
started
Jan 20, 2026, 09:10 UTC
resolved
50 min
duration
Minor
impact

Affected components

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

Timeline

updates from Sanity's status page ↗
  1. resolvedJan 20, 2026, 09:10 UTC

    This incident has been resolved.

  2. monitoringJan 20, 2026, 08:44 UTC

    We've identified and mitigated root cause of the issue. Performance has been stable since 8:36 UTC (start of degraded performance at 7:52 UTC) with no elevated error rates.

  3. investigatingJan 20, 2026, 08:34 UTC

    We are continuing to investigate this issue. And making adjustments in our internal systems.

  4. investigatingJan 20, 2026, 08:20 UTC

    We are continuing to investigate this issue.

  5. investigatingJan 20, 2026, 08:19 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.

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

← Previous: Elevated API and API CDN errors and latency for some customers (Jan 15, 2026)Next: Content Agent & Canvas experiencing elevated error rates (Jan 20, 2026) →
Sanity incident on Jan 20, 2026: Elevated API and API CDN errors and latency for some customers · APIStatus.watch