Sanity: Intermittent errors during failover
Timeline of updates
- resolved
From 15:48 to 15:49 we had an emergency maintenance failover of an internal service, and while this was going on we served HTTP 500 errors instead of GROQ results. This lasted around 30 seconds. We will investigate methods to improve this failover routine. We apologize for any inconvenience this might have caused.
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-02-16 16:04 UTC, resolved after 0 min, 1 update(s).
- Title
- Intermittent errors during failover
- Vendor
- Sanity
- Date
- URL
- https://rewindex.com/company/sanity/incidents/xgc9yq42fcm7
Sanity profileRecent Sanity incidentsAll outages on February 16, 2019Sanity in February 2019MarkdownJSON