RevenueCat: Degraded Response Times
Timeline of updates
- resolved
For about 5 minutes, our API response times were severely degraded. This was caused dyue to a bad config change to one of our databases. We are now fully back to normal. Any failed requests from a RevenueCat SDK will be retried and customers should not notice anything.
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 2022-08-10 01:02 UTC, resolved after 0 min, 1 update(s).
- Title
- Degraded Response Times
- Vendor
- RevenueCat
- Date
- URL
- https://rewindex.com/company/revenuecat/incidents/58g5q7dwtx0d
RevenueCat profileRecent RevenueCat incidentsAll outages on August 10, 2022RevenueCat in August 2022MarkdownJSON