RevenueCat: All API calls timing out
Timeline of updates
- resolved
From approx 5:56AM UTC until approx. 6:07AM UTC, all API calls were timing out across Khepri. Engineers have traced the cause to a cache failover under unusually high load during a one-off data import. Failover took longer than usual due to the heavy load, and, combined with a recently added backoff strategy that was overly aggressive, the temporarily unavailable cache caused all available threads in the backend to stall. After the cache finished failing over, the system returned to normal operation.
From RevenueCat’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 status.revenuecat.com (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by RevenueCat, started 2024-03-14 19:00 UTC, resolved after 0 min, 1 update(s).
- Title
- All API calls timing out
- Vendor
- RevenueCat
- Date
- URL
- https://rewindex.com/company/revenuecat/incidents/tnsr10pprczd
RevenueCat profileRecent RevenueCat incidentsAll outages on March 14, 2024RevenueCat in March 2024MarkdownJSON