Sanity: Temporary data API errors
Timeline of updates
- resolved
The data API returned errors with status code 500 for roughly 1 minute from 18:40:19 UTC. About 40% of projects without SLAs were affected. The errors were caused by the simultaneous loss of two database nodes due to a bug in the underlying database - we are working on mitigations, but do not expect further disruptions.
From Sanity’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
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.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
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 2019-01-23 19:27 UTC, resolved after 0 min, 1 update(s).
- Title
- Temporary data API errors
- Vendor
- Sanity
- Date
- URL
- https://rewindex.com/company/sanity/incidents/cjlk6bxnyxq9
Sanity profileRecent Sanity incidentsAll outages on January 23, 2019Sanity in January 2019MarkdownJSON