Sanity: Intermittent API timeouts
Timeline of updates
- resolved
From about 5:30 am until about 14:20 PST some customers experienced intermittent timeouts. The reason was twofold: 1) a customer with demanding work-loads should have been assigned to dedicated hardware resources but was colocated with the freemium users on infrastructure scaled for freemium plans. 2) this customer had a runaway batch job distributed across data centers forming an unintentional DoS attack. The immediate problem has been eliminated, and we have taken steps to make sure customers with big plans are always assigned appropriate infrastructure.
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-12 22:37 UTC, resolved after 0 min, 1 update(s).
- Title
- Intermittent API timeouts
- Vendor
- Sanity
- Date
- URL
- https://rewindex.com/company/sanity/incidents/jzczysn991cw
Sanity profileRecent Sanity incidentsAll outages on February 12, 2019Sanity in February 2019MarkdownJSON