Aug <var data-var='date'>10</var>, <var data-var='time'>19:59</var> UTC Resolved - Error rates and latency have returned back to normal. Aug <var data-var='date'>10</var>, <var data-var='time'>18:56</var> UTC Identified - We have rolled out a fix and are seeing early signs of improvement. Aug <var data-var='date'>10</var>, <var data-var='time'>18:37</var> UTC Investigating - We are currently investigating elevated error rates and latency across multiple of our APIs

Elevated error rates on RevenueCat APIs

Aug <var data-var='date'> 8</var>, <var data-var='time'>15:39</var> UTC Resolved - Apple has completed their maintenance. Aug <var data-var='date'> 6</var>, <var data-var='time'>14:49</var> UTC Monitoring - Apple has scheduled a maintenance window of App Store Connect on Saturday 2026/08/08 between 12:30pm to 3:00pm UTC. New and existing production purchases will be unaffected. Sandbox purchases might be affected. We also expect some features in the RevenueCat Dashboard, such as importing products automatically from App Store Connect or auto-applying settings from App Store Connect, may not function correctly during this time window.

App Store Connect undergoing maintenance by Apple

Aug <var data-var='date'> 7</var>, <var data-var='time'>19:54</var> UTC Resolved - Webhook delivery latency is still on normal levels and the system is stable. We consider the incident resolved. Aug <var data-var='date'> 7</var>, <var data-var='time'>17:29</var> UTC Monitoring - Webhook delivery latency is back down to normal levels. Aug <var data-var='date'> 7</var>, <var data-var='time'>16:47</var> UTC Identified - We are seeing increased latency on webhook delivery and are working to mitigate

Webhook delivery is delayed

Aug <var data-var='date'> 6</var>, <var data-var='time'>18:14</var> UTC Resolved - Rico continues recovered and stable, we consider the incident resolved. Aug <var data-var='date'> 6</var>, <var data-var='time'>17:16</var> UTC Monitoring - 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. Aug <var data-var='date'> 6</var>, <var data-var='time'>17:06</var> UTC Identified - 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. Aug <var data-var='date'> 6</var>, <var data-var='time'>17:04</var> UTC Investigating - 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.

Rico is having issues

Jul <var data-var='date'>31</var>, <var data-var='time'>06:30</var> UTC Resolved - The issue appears to have been resolved on Apple's side. We're seeing keys being correctly validated now. Jul <var data-var='date'>29</var>, <var data-var='time'>09:18</var> UTC Identified - 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. Jul <var data-var='date'>27</var>, <var data-var='time'>10:14</var> UTC Investigating - 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.

Newly created apps error with "The key is not valid or is not compatible with the Bundle ID of your app"

Jul <var data-var='date'>27</var>, <var data-var='time'>09:50</var> UTC Resolved - All the impacted purchases have been replayed. Jul <var data-var='date'>27</var>, <var data-var='time'>06:21</var> UTC Update - 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. Jul <var data-var='date'>27</var>, <var data-var='time'>00:41</var> UTC Update - 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 Jul <var data-var='date'>27</var>, <var data-var='time'>00:32</var> UTC Monitoring - 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 Jul <var data-var='date'>27</var>, <var data-var='time'>00:06</var> UTC Identified - 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. Jul <var data-var='date'>26</var>, <var data-var='time'>23:06</var> UTC Investigating - We are investigating errors with Apple's services. We have enabled a temporary fallback mechanism that should provide limited functionality.

Problems connecting to Apple services

Jul <var data-var='date'>16</var>, <var data-var='time'>21:40</var> UTC Resolved - App Store Connect issues are now resolved. Jul <var data-var='date'>16</var>, <var data-var='time'>18:43</var> UTC Identified - 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. Jul <var data-var='date'>16</var>, <var data-var='time'>13:47</var> UTC Investigating - 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 degraded performance

Jul <var data-var='date'>16</var>, <var data-var='time'>12:27</var> UTC Resolved - The issue has been resolved by Stripe and it's now possible to install again the RevenueCat Stripe app through the Stripe Marketplace page. Jul <var data-var='date'>16</var>, <var data-var='time'>10:53</var> UTC Investigating - 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.

Cannot connect new Stripe accounts without creating a Stripe Project through the CLI

Jul <var data-var='date'>16</var>, <var data-var='time'>10:47</var> UTC Resolved - This incident has been resolved. Jul <var data-var='date'>16</var>, <var data-var='time'>10:29</var> UTC Monitoring - 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. Jul <var data-var='date'>16</var>, <var data-var='time'>09:13</var> UTC Investigating - 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.

Some users unable to login via single-sign-on (SSO)

Jul <var data-var='date'> 7</var>, <var data-var='time'>17:28</var> UTC Resolved - This incident has been resolved. Jul <var data-var='date'> 7</var>, <var data-var='time'>16:56</var> UTC Monitoring - The issue appears to have been resolved on Google's side. Event rates are returning to normal levels. We'll continue monitoring the situation. Jul <var data-var='date'> 7</var>, <var data-var='time'>14:37</var> UTC Investigating - 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.

Delays in Play Store subscriptions renewals

Jul <var data-var='date'> 7</var>, <var data-var='time'>14:13</var> UTC Resolved - This incident has been resolved. Jul <var data-var='date'> 7</var>, <var data-var='time'>11:40</var> UTC Monitoring - We have stopped getting errors from Apple Store Kit 2 and the service is operational. We will continue monitoring all the systems. Jul <var data-var='date'> 7</var>, <var data-var='time'>10:32</var> UTC Investigating - 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.

Apple Store Kit 2 elevated error rates

Jun <var data-var='date'>23</var>, <var data-var='time'>21:29</var> UTC Resolved - App Store Connect issues are now resolved. Jun <var data-var='date'>23</var>, <var data-var='time'>19:50</var> UTC Monitoring - 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. Jun <var data-var='date'>23</var>, <var data-var='time'>17:10</var> UTC Identified - 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 outage

Jun <var data-var='date'>23</var>, <var data-var='time'>14:42</var> UTC Resolved - This incident has been resolved. Jun <var data-var='date'>23</var>, <var data-var='time'>08:39</var> UTC Monitoring - 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. Jun <var data-var='date'>22</var>, <var data-var='time'>18:32</var> UTC Identified - 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.

Paywall Charts: Conversions not being attributed

Jun <var data-var='date'>22</var>, <var data-var='time'>00:46</var> UTC Resolved - This incident has been resolved. Jun <var data-var='date'>21</var>, <var data-var='time'>22:23</var> UTC Identified - 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.

Delays in receipt refresh processing

Jun <var data-var='date'>16</var>, <var data-var='time'>18:18</var> UTC Resolved - This incident has been resolved. Jun <var data-var='date'>16</var>, <var data-var='time'>17:43</var> UTC Monitoring - The outage was caused by an underlying service provider issue, which seems to have been resolved. We are monitoring the situation. Jun <var data-var='date'>16</var>, <var data-var='time'>17:38</var> UTC Update - We are continuing to investigate this issue. Jun <var data-var='date'>16</var>, <var data-var='time'>17:35</var> UTC Investigating - Our AI assistant Rico is currently unavailable. We are investigating.

Rico unavailable

Jun <var data-var='date'>12</var>, <var data-var='time'>08:22</var> UTC Resolved - 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. Jun <var data-var='date'>12</var>, <var data-var='time'>06:38</var> UTC Identified - 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.

Automatic paywall translations unavailable

May <var data-var='date'>29</var>, <var data-var='time'>19:55</var> UTC Resolved - Our mitigations have eliminated the impact on RevenueCat clients. We will continue tracking the situation and following up with Google on a permanent fix. May <var data-var='date'>29</var>, <var data-var='time'>19:38</var> UTC Monitoring - 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. May <var data-var='date'>29</var>, <var data-var='time'>15:45</var> UTC Investigating - 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.

Elevated Google Play API Error Rate

May <var data-var='date'>25</var>, <var data-var='time'>17:29</var> UTC Resolved - This incident has been resolved. May <var data-var='date'>25</var>, <var data-var='time'>16:23</var> UTC Monitoring - A fix has been implemented and error rate is going down. We'll keep monitoring. May <var data-var='date'>25</var>, <var data-var='time'>15:57</var> UTC Identified - We are experiencing an increased error rate when fetching subscriber information coming from an incorrect cache. We are currently working on a fix.

Increased error rate when fetching subscriber information

May <var data-var='date'>12</var>, <var data-var='time'>07:24</var> UTC Resolved - We identified and resolved the issue. Charts v3 data is now up-to-date. May <var data-var='date'>12</var>, <var data-var='time'>04:01</var> UTC Investigating - We're investigating an issue where charts v3 data is delayed

Delayed Charts v3 Data

May <var data-var='date'> 8</var>, <var data-var='time'>13:27</var> UTC Resolved - This incident has been resolved. May <var data-var='date'> 8</var>, <var data-var='time'>10:03</var> UTC Update - 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). May <var data-var='date'> 8</var>, <var data-var='time'>01:22</var> UTC Monitoring - We are fully recovered now. We'll leave this incident open until our cloud provider confirms a full recovery. May <var data-var='date'> 8</var>, <var data-var='time'>01:15</var> UTC Identified - 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. May <var data-var='date'> 8</var>, <var data-var='time'>00:52</var> UTC Update - We are continuing to investigate this issue. May <var data-var='date'> 8</var>, <var data-var='time'>00:51</var> UTC Investigating - 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.

Increased API error rates due to reduced service capacity.

Apr <var data-var='date'>28</var>, <var data-var='time'>22:54</var> UTC Resolved - All systems are now operating normally. Event delivery has fully caught up, and performance has returned to expected levels. Apr <var data-var='date'>28</var>, <var data-var='time'>22:32</var> UTC Monitoring - 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. Apr <var data-var='date'>28</var>, <var data-var='time'>21:59</var> UTC Investigating - We're currently investigating an increased error rate on some of our APIs

Elevated error rates

Apr <var data-var='date'>22</var>, <var data-var='time'>19:42</var> UTC Resolved - The incident has been resolved. Apr <var data-var='date'>22</var>, <var data-var='time'>19:24</var> UTC Monitoring - A fix has been implemented and rate-limit errors are back to baseline. We will continue to monitor. Apr <var data-var='date'>22</var>, <var data-var='time'>19:09</var> UTC Identified - 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.

Increased rate-limit errors on API V2 endpoints

Apr <var data-var='date'>18</var>, <var data-var='time'>21:10</var> UTC Resolved - 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. Apr <var data-var='date'>18</var>, <var data-var='time'>20:46</var> UTC Update - 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 Apr <var data-var='date'>18</var>, <var data-var='time'>20:42</var> UTC Investigating - We have noticed a degradation of service and are investigating the issue.

Degradation of service

Apr <var data-var='date'>17</var>, <var data-var='time'>07:00</var> UTC 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.

Degraded API Performance

Apr <var data-var='date'>10</var>, <var data-var='time'>10:42</var> UTC Resolved - This incident has been resolved. Apr <var data-var='date'>10</var>, <var data-var='time'>10:42</var> UTC Update - 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. Apr <var data-var='date'>10</var>, <var data-var='time'>09:04</var> UTC Monitoring - Fix has been rolled out and we are redelivering exports that were affected. Apr <var data-var='date'>10</var>, <var data-var='time'>08:24</var> UTC Identified - We have identified an issue with Scheduled Data Exports. We’re rolling out a fix. Apr <var data-var='date'>10</var>, <var data-var='time'>07:49</var> UTC Investigating - We have detected some issues causing some delays with Schedule Data Export deliveries to GCP

Is RevenueCat down?

RevenueCat status is UP

Lastest published events

Elevated error rates on RevenueCat APIs

App Store Connect undergoing maintenance by Apple

Webhook delivery is delayed

RevenueCat Services, Components and Regions

Recent RevenueCat events

Elevated error rates on RevenueCat APIs

App Store Connect undergoing maintenance by Apple

Webhook delivery is delayed

Rico is having issues

Newly created apps error with "The key is not valid or is not compatible with the Bundle ID of your app"

Problems connecting to Apple services