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 Feb 19, 2026, 19:53 UTC. It was resolved after 53 min.

Right now Sanity is operational. Live Sanity status →

🔔 Get alerted when Sanity has issuesFree · email alerts · no credit card
Feb 19, 2026, 19:53 UTC
started
Feb 19, 2026, 20:46 UTC
resolved
53 min
duration
Minor
impact

Affected components

  • api.sanity.io
  • apicdn.sanity.io
  1. resolvedFeb 19, 2026, 20:46 UTC

    This incident has been resolved.

  2. monitoringFeb 19, 2026, 20:19 UTC

    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.

  3. investigatingFeb 19, 2026, 19:53 UTC

    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.

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.

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

Sanity incident on Feb 19, 2026: Elevated API and API CDN errors and latency for some customers · APIStatus.watch