Revenuecat driftsforstyrrelser

We noticed that over the last hour, Google has been delaying expected subscription renewals and instead extending the expiration dates of the previously active subscription periods. As a result, RevenueCat is observing a reduced rate of renewal, cancellation, expiration, and billing issue events. We are currently investigating this unusual behavior.

The issue appears to have been resolved on Google's side. Event rates are returning to normal levels. We'll continue monitoring the situation.

This incident has been resolved.

We are getting 5xx errors when calling Apple Store Kit 2 to validate receipts. We have enabled mitigations to keep customer purchases uninterrupted and we are investigating the issue.

We have stopped getting errors from Apple Store Kit 2 and the service is operational. We will continue monitoring all the systems.

This incident has been resolved.

App Store Connect is experiencing an outage that affects some users. Our users may experience issues when handling their app store products on the dashboard or on MCP.

App Store Connect is experiencing degraded performance. Our users may experience issues when handling their app store products on the dashboard or on MCP. This does not impact purchases.

App Store Connect issues are now resolved.

Conversions in the Paywalls Charts are currently not being attributed. We've identified the issue and are working to resolve it. We'll keep this incident open until the issue has been fixed & data has been corrected.

We have deployed a fix for this issue and are currently backfilling the affected data. New conversions are being attributed correctly. We will continue monitoring the backfill process.

This incident has been resolved.

We're observing delays in our background Apple receipt-refresh processing, which may cause some subscription statuses to update later than usual. New purchases, webhooks, and API requests are processing normally. Our team is working on it.

This incident has been resolved.

Our AI assistant Rico is currently unavailable. We are investigating.

We are continuing to investigate this issue.

The outage was caused by an underlying service provider issue, which seems to have been resolved. We are monitoring the situation.

This incident has been resolved.

We are currently investigating an issue affecting automatic translations in the Paywall editor. Customers may be unable to generate new paywall translations from the dashboard. Existing paywall translations are not affected. We have identified the likely cause as a breaking change in one of our translation provider dependencies and are working on updating our integration.

This incident has been resolved. Automatic translations in the Paywall editor are working again. Customers should now be able to generate new paywall translations from the dashboard as expected.

We are observing elevated error rates from the Google Play API. This might prevent some user's entitlements from being granted after purchase. We're working on a mitigation to unlock these customers.

Google Play API started returning some new, undocumented error responses for a subset of subscriptions over the last few hours. Our investigation revealed that the vast majority of them are associated with purchases that expired a long time ago. This means that no new purchases are being blocked, but API requests were still impacted by these unexpected errors. We have implemented suppression for these errors when we can programmatically confirm that they refer to long-expired purchases. This has reduced the errors returned by the RevenueCat receipts endpoint by almost 100%, so the issue is now mitigated. We have informed Google about these new unexpected errors and expect them to work on a permanent fix.

Our mitigations have eliminated the impact on RevenueCat clients. We will continue tracking the situation and following up with Google on a permanent fix.

We are experiencing an increased error rate when fetching subscriber information coming from an incorrect cache. We are currently working on a fix.

A fix has been implemented and error rate is going down. We'll keep monitoring.

This incident has been resolved.

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.

We have noticed a degradation of service and are investigating the issue.

We are currently experiencing an incident affecting parts of RevenueCat’s web infrastructure. To reduce impact for customers and their users, mitigations have been activated: What should continue to work normally: apps should continue to load paywalls using cached product data, users should still be able to complete purchases, and users who purchase during this period should continue to receive access to the content or features they bought What will not work normally during this incident: some real-time and customization features may be degraded while Fortress is active. This includes Offering experiments and customer-specific Offering customization, which may not be applied during the incident. Webhooks and some third-party integration events may also be delayed rather than delivered in real time What happens after recovery: once normal service is restored, we will replay queued requests so purchase records, entitlement confirmation, webhooks, and downstream events can be reconciled We are actively working to restore full service and will continue to share updates as we make progress

The underlying infrastructure issue has been addressed, and RevenueCat services are now operating normally again. Temporary mitigations have been removed as full service has been restored. We are continuing to monitor the system closely to ensure stability.

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.