RevenueCat: Potential error spikes with database patch
Timeline of updates
- resolved
The issue has been resolved, and as a result, we were able to reenable the database operations that were temporarily disabled. The root cause was identified as a corrupted index, which caused database restarts when autovacuum was triggered. The corrupted index was rebuilt, resolving the issue and restoring autovacuum functionality. We are still awaiting feedback from our cloud provider regarding the cause of the index corruption and will continue to monitor the situation. Thank you for your patience and understanding throughout this incident.
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 2025-01-10 09:00 UTC, resolved after 26 h, 1 update(s).
- Title
- Potential error spikes with database patch
- Vendor
- RevenueCat
- Date
- URL
- https://rewindex.com/company/revenuecat/incidents/v6vzq02qky5h
RevenueCat profileRecent RevenueCat incidentsAll outages on January 10, 2025RevenueCat in January 2025MarkdownJSON