RevenueCat had 48 outages in the last 2 years totaling 145h 48m of downtime — averaging 2 incidents per month.
There were 48 RevenueCat outages since May 6, 2025 totaling 145h 48m of downtime. Each is summarised below — incident details, duration, and resolution information.
We're investigating an issue where charts v3 data is delayed
We identified and resolved the issue. Charts v3 data is now up-to-date.
We are currently investigating elevated API error rates caused by reduced service capacity. Some end users may experience intermittent issues when making purchases or restoring subscriptions. Subscription activations may also be delayed temporarily. Most requests will continue to succeed, and affected transactions will automatically recover once service is restored. This issue is impacting RevenueCat API requests across iOS, Android, and Web platforms. Analytics processing and exports may also be delayed during this incident. We are actively restoring capacity and mitigating the issue. RevenueCat Fortress protections remain active to help preserve transaction data during the disruption. We will continue to provide updates as recovery progresses.
We are continuing to investigate this issue.
We are starting to see some recovery. The underlying incident on our cloud provider is still not resolved, but metrics look good on our end. We are continuing to monitor.
We are fully recovered now. We'll leave this incident open until our cloud provider confirms a full recovery.
Our API has been fully operational since ~ 01:20 UTC. The underlying incident on our cloud provider is not yet closed, but is not impacting our service. As of ~ 05:20 UTC, all transactions processed by our Fortress protection have been replayed and should show up in the dashboard. The RevenueCat SDK will handle the API service degradation (from 00:17 UTC to 01:20 UTC) gracefully (no lost transactions).
This incident has been resolved.
We're currently investigating an increased error rate on some of our APIs
A fix has been implemented to address database deadlocks that were degrading API performance. The system is now stable and performance has recovered. We are still observing some delays in webhook delivery, but these are improving and we expect them to fully recover shortly.
All systems are now operating normally. Event delivery has fully caught up, and performance has returned to expected levels.
At 18:27 UTC we noticed an increase in rate-limit errors from our v2 API endpoints for some developers since ~14:00 UTC. We have identified the issue and are implementing a fix.
A fix has been implemented and rate-limit errors are back to baseline. We will continue to monitor.
The incident has been resolved.
Earlier today, around 7:20 AM UTC, we had slightly elevated error rates on our API for about 5 minutes due to database maintenance. The RevenueCat SDK will handle this gracefully, but API users may have noticed a brief increase in errors.
We have detected some issues causing some delays with Schedule Data Export deliveries to GCP
We have identified an issue with Scheduled Data Exports. We’re rolling out a fix.
Fix has been rolled out and we are redelivering exports that were affected.
The issue affecting Scheduled Data Exports to GCP has been fully resolved. All delayed exports have now been successfully delivered, and export processing is operating normally.
This incident has been resolved.
We have identified a problem affecting the Play Store which results in inflated MRR/ARR numbers for Charts v3. We have identified the problem and we are working on a fix.
We have found that the issue only affects charts for Play Store products that have two introductory offers. We are currently testing our fix before the final deployment and backfilling of the affected charts.
We have applied the fix, and we are currently backfilling the affected charts.
This incident has been resolved.
We're currently investigating an issue with dispatching events via webhooks for certain integration
We are continuing to investigate this issue.
We've located and fixed the issue that was causing webhook integrations using AWS API gateway to fail.
The issue has been identified and a fix is being implemented.
The issue has been resolved and all failed webhook events have been dispatched.
From 6:10 to 6:25 UTC, we had slightly higher API error rates due to a database infrastructure issue. The incident has been resolved. App using the RevenueCat SDK were not impacted.
We are currently investigating an issue with the Charts V3 Beta not showing data. Workaround: Disable Charts V3 via the switch (top right) in the dashboard.
The issue has been identified and a fix is being implemented.
* Charts V3 Beta is currently disabled for all users. * We have repaired the underlying problem, but we have to apply further fixes to prevent the issue from re-triggering.
The underlying infrastructure issue has been resolved. We are gradually re-enabling services and monitoring for stability. Charts V3 Beta remains disabled as a precaution and will be re-enabled once we confirm full stability.
Charts V3 Beta is now available again for all users. The underlying infrastructure issue has been resolved. Data processing jobs are still being re-enabled and any data gaps will be backfilled automatically.
We're currently investigating an increased error rate on some of our APIs.
We believe we have identified an issue with Cloudfront, and we have applied an emergency mitigation. We're seeing recovery on SDK APIs.
We’ve recovered the SDK API, and purchases from your app are now being processed successfully. Some dashboard functionality may still be unreliable. Our team is continuing to work on mitigating the CloudFront issues, and we’ll share further updates as progress is made.
We’ve recovered the SDK API, and purchases from your app are now being processed successfully. Some dashboard functionality and paywall assets may still be unavailable. Our team is continuing to work on mitigating the CloudFront issues, and we’ll share further updates as progress is made.
We are continuing to monitor for any further issues.
We purged the DNS cache and are starting to see improving dashboard error rates. There is still a long tail of errors we are monitoring.
The primary DNS servers have recovered and updates have propagated to most DNS providers. Note that some ISPs and network setups might cache DNS entries longer, so errors might persist and might take longer to resolve for some users.
This incident has been resolved.
We are currently experiencing delayed data in our experiments pipelines. The issue has been identified and fixed. We are now waiting for the jobs to finish processing.
All experiment pipeline jobs have finish successfully and the data is now up to date. We are sorry for the inconveniences this may have caused you.
From ~4:30 UTC to ~5:30 UTC webhook delivery time regressed to up to a few minutes delay (from the usual second or two). The underlying issue has been fixed and delivery time is back down to normal latency.
The issue has been identified and we are working on a fix, sorry for the inconveniences.
The incident has resolved, and the experimental results are up to date.
We identified an issue where Charts data freshness indicators are displaying outdated timestamps. The underlying chart data is being updated correctly, but the freshness timestamps shown in the UI are not reflecting the latest refresh times. A fix has been deployed and we are monitoring the rollout.
This incident has been resolved.
We are investigating an issue affecting our analytics pipeline that is causing delayed or inaccurate data in Charts, Experiments, and Scheduled Data Exports. Deleted records are not being properly removed from these products. We are actively working to identify the root cause and will provide an update once we have more information.
We have identified the root cause of the issue affecting Charts, Experiments, and Scheduled Data Exports. A recent configuration change was preventing deleted records from being synced correctly. We are now deploying a fix and will continue to monitor the systems.
We have identified and fixed the issue preventing deleted records from syncing to our analytics products. Deletes are now flowing correctly. We are processing a backlog of data to ensure Charts, Experiments, and Scheduled Data Exports reflect accurate information.
We have resolved an issue that was preventing some deleted records from syncing to Charts, Experiments, and Scheduled Data Exports. The fix has been deployed and data is now flowing correctly. The vast majority of customers were not impacted. We are continuing to monitor the systems
This incident has been resolved.
We have detected a spike in errors related to our database and have enabled Fortress to mitigate while we investigate.
We have disabled fortress and the error rate is back to normal. We will be monitoring the systems.
All fortress receipts have been replayed.
We are currently experiencing delays in the data source that powers charts, experiments, data exports, and customer lists. Our team has identified the issue and is actively working on a fix. Thank you for your patience.
Data exports and customer lists are now fully up to date. Updates for charts and experiments are still in progress.
Charts are now up to date as well. The only remaining stale data is for experiment results.
Experiment results are now also updated and all data is fully up to date. Some scheduled data exports contained missing data, but they will repopulate automatically during the next export cycle.
We are seeing issues with delivery of push notifications to the RevenueCat app, and are investigating the issue.
Push notifications to the RevenueCat app are now being delivered in time. Notifications affected by the issue have also been delivered.
We’re currently experiencing a delay in data updates for the Active Customers chart and the Overview dashboard. Our team is actively working to bring the data up to date.
We have identified the root cause of the issue and are processing the backlog of data. The Active Customers charts (currently in beta) and Overview panel will start showing up-to-date information within 24 hours.
We have finished processing the data backlog. Real-time charts now show up-to-date information in the Active Customers chart and the Overview panel.
We are seeing an increase in 500 error responses from Apple's App Store server APIs. To prevent this from impacting customers, we have enabled an outage mode that grants a temporary short-lived entitlement when a purchase is unable to be validated due to a 500 error from Apple. Once the error rate returns to normal, we'll disable the outage mode mitigation.
We are continuing to monitor for any further issues.
We haven't seen any errors for about two hours now. All the impacted receipts have been replayed so there is no customer impact.
We have identified an issue that was affecting our charts pipelines, resulting in delayed updated. We have corrected it and we are monitoring. Charts will get updated in the next few hours.
The incident has been resolved and charts show up-to-date data.
Scheduled Data Exports are not running at the expected schedule. We have identified the issue and are working on executing them as soon as possible. No action required. We are very sorry for the inconveniences.
Scheduled Data Exports are running again. Depending on your configuration you might have received multiple export files, so we will contact affected customers individually.
All operations are back to normal