Sanity: API & API CDN timeouts for small subset of customers
Affected components: apicdn.sanity.ioapi.sanity.io
Timeline of updates
- monitoring
From 13:12 to 15:13 UTC, a small subset of customers experienced intermittent increased latency on API requests, and some requests returned errors. Most customers were unaffected. Our engineers identified the cause and took steps to resolve it, and API performance has been back to normal since 15:07 UTC, and we are continued to monitor the results.
- resolved
This incident has been resolved.
Changes Rewindex caught on this incident
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 these records existed by then and have 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-26 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
9d52ac812e822d83…Version 2 captured
In the 2026-10-26 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
64c1fb0cf8c2abbb…
Impact, status and times are the vendor’s own, as last archived. View on www.sanity-status.com (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by Sanity, started 2026-10-26 15:49 UTC, resolved after 5 min, 2 update(s); edited after publishing.
- Title
- API & API CDN timeouts for small subset of customers
- Vendor
- Sanity
- Date
- URL
- https://rewindex.com/company/sanity/incidents/fhv5grlc7mg4
Sanity profileRecent Sanity incidentsAll outages on October 26, 2026Sanity in October 2026MarkdownJSON