Sanity: Elevated error rates on our API CDN
Affected components: apicdn.sanity.io
Timeline of updates
- investigating
Beginning around 13:40 UTC we began experiencing elevated error rates on our API CDN in certain regions. As a result, some requests may respond with a 5xx status. We're investigating the issue now.
- monitoring
We've mitigated the original issue and are no longer seeing elevated error rates. We're continuing to monitor and while we investigate the root cause.
- resolved
The issue was related to a higher than expected load which has been resolved. All operations are back to normal and we'll continue to monitor our systems closely.
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
4af3808aa4103157…
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-05 14:05 UTC, resolved after 38 min, 3 update(s).
- Title
- Elevated error rates on our API CDN
- Vendor
- Sanity
- Date
- URL
- https://rewindex.com/company/sanity/incidents/347tqql57x0m
Sanity profileRecent Sanity incidentsAll outages on January 5, 2026Sanity in January 2026MarkdownJSON