RevenueCat Outage History

RevenueCat experienced elevated API error rates due to reduced service capacity caused by an underlying cloud provider incident, affecting users across iOS, Android, and Web platforms who encountered intermittent issues with purchases, subscription restorations, and delayed subscription activations. The service was fully restored after approximately 1 hour of degradation, with Fortress protections ensuring no transactions were lost and all affected transactions automatically recovered. Analytics processing and exports were also temporarily delayed but resumed normal operation once capacity was restored.

RevenueCat experienced elevated error rates on their APIs for 58 minutes due to database deadlocks that degraded performance. The incident affected API uptime and caused delays in webhook delivery. The issue was resolved by implementing a fix to address the database deadlocks, restoring normal system operation and performance.

RevenueCat experienced increased rate-limit errors on API V2 endpoints affecting some developers from approximately 14:00 UTC to 19:42 UTC on April 22, 2026. The issue impacted API uptime and was resolved after the team identified the root cause and implemented a fix. The incident lasted 36 minutes from detection to resolution, with rate-limit errors returning to baseline levels.

RevenueCat experienced a 32-minute service degradation affecting their API uptime due to web infrastructure issues. During the incident, apps continued to function with cached data and users could complete purchases, but real-time features like offering experiments, customization, and webhooks were degraded or delayed. The underlying infrastructure issue was resolved and full service was restored, with queued requests being replayed to reconcile purchase records and events.

RevenueCat experienced delays with Scheduled Data Export deliveries to Google Cloud Platform (GCP) for 2.9 hours. The service identified the issue affecting data export scheduling and deployed a fix while redelivering the affected exports. The incident was resolved with all delayed exports successfully redelivered.

RevenueCat experienced an issue where ARR/MRR charts displayed inflated numbers for Play Store products with two introductory offers in Charts v3. The problem specifically affected revenue reporting accuracy for affected users' analytics dashboards. The issue was resolved after 5.8 hours with a fix deployment and backfilling of the affected chart data.

RevenueCat experienced an issue where webhook events failed to dispatch for integrations using AWS API Gateway, lasting 1.3 hours. The problem prevented certain webhook integrations from receiving events as expected. The issue was identified and fixed, with all failed webhook events successfully dispatched once the resolution was implemented.