Revenuecat outage history

We are seeing elevated errors when validating purchases made in Apple's sandbox environment, including TestFlight builds. Since about 06:00 UTC, most sandbox purchases and restores on iOS, macOS, and other Apple platforms are failing to validate, so test purchases may not unlock entitlements. Purchases made with real money in production apps are not affected.

The incident has been resolved. Apple Sandbox App Store API is correctly processing requests.

We’re observing a drop of the rate in Google Play pub-sub notifications. You may notice delay in the delivery of events. We are investigating.

We’re observing a drop in the rate of Google Play Pub-Sub notifications, and most purchases are currently failing. You may also notice delays in event delivery. Google has acknowledged the issue and we’re monitoring the situation.

This incident has been resolved.

We’re seeing an increased rate of errors when communicating with Apple’s backend services. This is resulting in some HTTP 522 responses from our receipts endpoint. We’ve enabled mitigations to minimize the impact on RevenueCat customers, and no purchases are currently being blocked as a result. We’ll continue monitoring the issue and update this thread.

Apple has reported that the issue is now resolved, and we’re also seeing error rates return to normal. We’ll keep monitoring.

The issue has been resolved. We’re now making sure that any purchases affected by the outage are reprocessed.

We are currently investigating elevated error rates and latency across multiple of our APIs

We have rolled out a fix and are seeing early signs of improvement.

Error rates and latency have returned back to normal.

We are seeing increased latency on webhook delivery and are working to mitigate

Webhook delivery latency is back down to normal levels.

Webhook delivery latency is still on normal levels and the system is stable. We consider the incident resolved.

We are currently investigating a complete outage affecting Rico. All requests to the service are failing at this time. We will provide an update as soon as we have more information.

We've identified the issue: an outage with one of our upstream AI inference providers is causing Rico to fail. This is an external dependency issue, and we are actively monitoring the provider's status and working on mitigation options. We will post another update as soon as we have more information.

Our upstream AI inference provider has recovered, and Rico is now operating normally. We're continuing to monitor closely to confirm full stability before marking this resolved. We will provide a final update shortly.

Rico continues recovered and stable, we consider the incident resolved.

Developers setting up a newly created app may see "Credentials need attention" for their In App Purchase key. This is caused by Apple's App Store Server API rejecting recently registered Bundle IDs. Existing apps are unaffected, and we have reported it to Apple. Regenerating the key does not resolve it.

We're awaiting a fix from Apple. Apple’s App Store Server API returns a 401 for Bundle IDs registered on or after 24 July. The same key works against older Bundle IDs in the same account, and we have reproduced this directly against Apple’s API. The failure happens before any RevenueCat logic. For affected apps, the “Credentials need attention” warning is not accurate. Your key is almost certainly correct. Regenerating the key, re registering the Bundle ID or recreating the app will not resolve it. We have reported the issue to Apple and will continue to assist Apple in resolving it.

The issue appears to have been resolved on Apple's side. We're seeing keys being correctly validated now.

We are investigating errors with Apple's services. We have enabled a temporary fallback mechanism that should provide limited functionality.

Apple have acknowledged problems with multiple services. We will keep granting short-lived, temporary entitlements until the problem is resolved. Once the error rate returns to normal, we will disable this mitigation and revalidate the affected purchases.

We're monitoring the Receipt Server for recovery Because we're unable to validate new purchases with the store, we're granting new users a short-term entitlement (at most 24 hours). This prevents customers from being denied access during exceptional situations, such as partial app store outages After connectivity is restored, if validation succeeds, expect a regular initial purchase. If validation fails, the temporary entitlements will expire

Apple's Receipt Server is back up We're replaying purchases Temporary entitlements will either turn into 'real' purchases, or will expire, and related webhook and intergation events for the duration of the outage will start coming through

We are continuing to replay impacted receipts. This does not impact customers that made purchases during the outage window as the temporary entitlement granted by RevenueCat will ensure a seamless transition. This incident will be closed out once all the purchases have been replayed.

All the impacted purchases have been replayed.

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.

App Store Connect is experiencing slow response times, which may affect some users. They may encounter delays or issues when managing App Store products in the dashboard or through MCP.

App Store Connect is experiencing slow response times, which may affect some users. They may encounter delays or issues when managing App Store products in the dashboard or through MCP.

App Store Connect issues are now resolved.

The Stripe Marketplace page for the RevenueCat app doesn't show anymore the Install button to install it in the Stripe account. This makes it impossible to install the RevenueCat app in new accounts from the Marketplace page. No existing Stripe connection is affected. Connecting new Stripe accounts to RevenueCat is only possible by using the new Stripe Projects integration through the Stripe cli at the moment. We are working with Stripe to restore the Install CTA button in the marketplace page, allowing customers that don't want to use the Stripe cli to connect Stripe to their RevenueCat account. Please contact support if you are having issues connecting your Stripe account to RevenueCat.

The issue has been resolved by Stripe and it's now possible to install again the RevenueCat Stripe app through the Stripe Marketplace page.

SSO sign-ins and sessions are experiencing degraded performance Customers using Single Sign-On may have difficulty signing in to the RevenueCat dashboard or may have their existing sessions interrupted. This issue only affects organizations with SSO configured. RevenueCat SDKs, purchases, subscriptions, entitlements, APIs, analytics, and data exports are unaffected. The issue is caused by degraded performance from our SSO provider. We are monitoring the situation and will provide another update as soon as we have more information. No action is required from customers at this time.

Our SSO provider has identified the cause of the elevated error rates and implemented a fix. We are seeing sign-in and session errors decrease as the service recovers. Some customers using Single Sign-On may still experience intermittent difficulty signing in to the RevenueCat dashboard or may have their existing sessions interrupted. This issue remains limited to organizations with SSO configured. We are continuing to monitor the recovery and will provide another update once the issue is fully resolved. No action is required from customers.

This incident has been resolved.

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.