RevenueCat: Increased API latency for 11 minutes
Timeline of updates
- resolved
A database migration that dropped deprecated columns caused some timeouts and 500s because the API tried to query those columns for 11 minutes. The incident impacted new users created during that period exposed to a paywall. The team quickly jumped into the issue and fixed it.
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: minor) posted by RevenueCat, started 2024-02-27 10:23 UTC, resolved after 0 min, 1 update(s).
- Title
- Increased API latency for 11 minutes
- Vendor
- RevenueCat
- Date
- URL
- https://rewindex.com/company/revenuecat/incidents/cyxjrt4ws1zq
RevenueCat profileRecent RevenueCat incidentsAll outages on February 27, 2024RevenueCat in February 2024MarkdownJSON