Sanity incident

Elevated API and API CDN errors and latency for some customers

Minor Resolved View vendor source →

Sanity experienced a minor incident on January 20, 2026 affecting api.sanity.io and apicdn.sanity.io, lasting 50m. The incident has been resolved; the full update timeline is below.

Started
Jan 20, 2026, 08:19 AM UTC
Resolved
Jan 20, 2026, 09:10 AM UTC
Duration
50m
Detected by Pingoru
Jan 20, 2026, 08:19 AM UTC

Affected components

api.sanity.ioapicdn.sanity.io

Update timeline

  1. investigating Jan 20, 2026, 08:19 AM 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.

  2. investigating Jan 20, 2026, 08:20 AM UTC

    We are continuing to investigate this issue.

  3. investigating Jan 20, 2026, 08:34 AM UTC

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

  4. monitoring Jan 20, 2026, 08:44 AM 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.

  5. resolved Jan 20, 2026, 09:10 AM UTC

    This incident has been resolved.