Sanity: Elevated API and API CDN errors and latency for some customers
Affected components: apicdn.sanity.ioapi.sanity.io
Timeline of updates
- investigating
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.
- investigating
We are continuing to investigate this issue.
- investigating
We are continuing to investigate this issue. And making adjustments in our internal systems.
- monitoring
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.
- resolved
This incident has been resolved.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-10-17 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
3563f642d51de599…
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by Sanity, started 2026-01-20 08:19 UTC, resolved after 50 min, 5 update(s).
- Title
- Elevated API and API CDN errors and latency for some customers
- Vendor
- Sanity
- Date
- URL
- https://rewindex.com/company/sanity/incidents/llv2lf4y6h6s
Sanity profileRecent Sanity incidentsAll outages on January 20, 2026Sanity in January 2026MarkdownJSON