Is RevenueCat Down Right Now? Check if there is a current outage ongoing.

We are continuing to investigate this issue.

We're aware of an issue that inviting collaborators does not work if the collaborator is not already logged into a RevenueCat session in their browser. We're investigating and will have more updates to share soon.

There has been an increased delay in the delivery of integration events due to the ongoing GCP service degradation.

We are facing issues with our caching infrastructure and are temporarily increasing database capacity to handle the load.

We experienced an issue where the Web Purchases Links were unavailable due to a misconfiguration in our content delivery layer. The issue has been identified and resolved. We’re sorry for the disruption this caused.

We experienced an issue where the Web Purchases Links were unavailable due to a misconfiguration in our content delivery layer. The issue has been identified and resolved. We’re sorry for the disruption this caused.

The fix has been deployed. All subsequent Scheduled Data Exports will have the columns arranged in the original order. 2025-05-19 Update: For certain customers, the column order of first_seen_time and auto_resume_time in your Scheduled Data Export was still unexpectedly flipped since 2025-05-14 7AM UTC. This has been fixed, and we have contacted all affected customers. Sorry for the inconveniences.

A code change accidentally modified the order of the columns in data exports. We have identified the root cause and we are working on a fix. We will provide another update shortly. Sorry for the inconveniences.

Test mode isn’t available on new Stripe accounts that haven’t verified their business details. This means you won’t be able to connect unverified Stripe sandbox accounts to RevenueCat. Older test accounts or accounts that are already verified aren’t affected. To restore access to test mode, verify your business details in Stripe. We’re working on updates to support Stripe’s new sandbox behavior. These will be available soon.

We're getting reports from customers that test mode is not available for new Stripe accounts. We're investigating workarounds. You can still connect production Stripe accounts to RevenueCat. Both Web Billing and Stripe Billing are affected only for sandbox purchases on new Stripe accounts. If you are affected, reach out to RevenueCat Support at support@revenuecat.com.

We're no longer seeing these intermittent delays in our own testing, or in reports from developers, so we're consider this incident resolved. If you see any unexpected delays in your own sandbox or TestFlight testing, please feel free to reach out to us for assistance.

Sandbox, TestFlight, and App Review environments all appear to be intermittently affected by delays fetching products and displaying the pay sheet on the App Store's side. We'll continue monitoring to see if these delays subside.

TestFlight product fetching and purchase sheet display both seem to be experiencing displays. These delays appear to be isolated to TestFlight as far as we've observed.

We're seeing reports and examples of delayed product fetching for App Store apps in sandbox. We're currently investigating the problem, and will keep this incident updated as we learn more.

We are no longer seeing an increased error rate from App Store APIs. The RevenueCat team will be replaying all the failed receipts since the outage began. Update at 21:16 - Receipt replays for the duration of the outage are now complete.

We have noticed an increase in errors from Apple Store APIs. RevenueCat's team has enabled Storage Outage mode so operations will not be interrupted. We will update as we learn more.

An issue with a third-party has been resolved and SSO login looks to be back to normal.

We're seeing intermittent internal server errors when logging in with SSO accounts. Standard email/password is unaffected.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue has been identified and we are rolling out a fix.

We're currently fixing an issue on the paywall editor where text is cleared upon saving.

This incident has been resolved.

The issue has been identified and we're implementing a fix.

We're currently investigating an issue on the dashboard where developers are unable to import products. There are multiple paths that are still working. We recommend using the Import button that is available on the App section.

This incident has been resolved. The issue was caused by an upgrade to a library, which we have now addressed. Everything is back to normal. Thanks for your patience!

We’ve reverted a recent deployment that caused the issue. Users should now be able to access their account settings again. We’re continuing to investigate the root cause and will provide further updates as we learn more.

We’re investigating an issue causing some users to be automatically logged out of the RevenueCat dashboard. This issue does not affect our SDK or API, and subscriptions and purchases continue to function as expected. We’ll provide updates as we learn more.

All requests have been re-processed.

We are currently re-processing all the API requests that were falling back to our back-up systems during the incident to make sure no data is lost.

Our APIs are operating normally now. We keep moniroring.

We have mitigated the issue and now gradually going back to normal operation of our systems.

We are rolling back a release that might have caused the issue. We are continuing to investigate this issue.

We are investigating an issue with one of our database that's affecting RevenueCat API. We have enabled enabled emergency mitigations.

The incident has been resolved.

Error rates are back to normal. We are continuing to monitor the situation.

We have mitigated the root cause and error rates are decreasing. We're still experiencing elevated 500s but expect to have it fully restored shortly.

We are investigating an issue with the RevenueCat API. We have enabled enabled emergency mitigations.

Updated January 23, 2025 - extended data recovery is complete. In preparation for upgrading to Apple’s V5 Campaign Management API, we inadvertently omitted a header to retrieve campaign names from the Apple Search Ads API. On January 19th, we reverted the changes that caused the issue to ensure no further data is affected. To address the missing data, we are taking the following actions: - Immediate data recovery: On January 19th at approximately 6:00 PM UTC, we successfully ran a recovery job to repopulate ASA data from the past 24 hours. This limitation exists because Apple’s attribution tokens are valid for only 24 hours. - Extended data recovery: Data missing between January 16th and January 18th has been recovered.

The issue has been identified and the fix has been deployed. Sorry for the inconveniences.

We have encountered an issue preventing charts from loading. The team is investigating and will provide an update shortly.

The issue has been resolved, and as a result, we were able to reenable the database operations that were temporarily disabled. The root cause was identified as a corrupted index, which caused database restarts when autovacuum was triggered. The corrupted index was rebuilt, resolving the issue and restoring autovacuum functionality. We are still awaiting feedback from our cloud provider regarding the cause of the index corruption and will continue to monitor the situation. Thank you for your patience and understanding throughout this incident.

The service remains stable and fully operational, but the situation has not changed. We are still awaiting a response from our cloud provider. At the same time, we are investigating ways to safely reenable the database operations that were temporarily disabled to mitigate the issue. Thank you for your patience as we work towards a resolution.

The service remains stable, and we have taken additional measures to mitigate the issue, including adjustments to database operations that were impacting performance. We are continuing to work closely with our cloud infrastructure provider to address the root cause, which is not yet fully resolved.

The service remains stable, but we are continuing to monitor the situation and we are working with our cloud infrastructure provider for a long term solution.

We may still be experiencing some potential error spikes with the database maintenance patch that we had just performed. We're keeping to monitor and aim to resolve this fully.

The database upgrade has been successfully applied without any service interruption.

The team is conducting a minor database upgrade to address the previous incident. We don't expect any serious interruption to service, but have mitigation plans in place in the event of an emergency. This shouldn't take more than a few minutes.

The incident has been resolved and all our APIs are working normally.

We are continuing to monitor for any further issues.

We have recovered from the elevated error rate and should be back to normal. We're actively monitoring.

We are noticing an increased of error rate on our API. It appears to have recovered but we're currently investigating.

The fix mentioned in the previous update has been confirmed. If there any questions please don't hesitate to reach out to support.

We are continuing to investigate this issue. In the meantime, you can enable our proxy server to address this issue by following these instructions: https://www.revenuecat.com/docs/getting-started/configuring-sdk#configuration-for-users-in-mainland-china

We are currently investigating the issue

Incident is resolved, Apple downstream error rates are back to normal and we're investigating failures in our mitigation attempts.

Part of our Apple downtime mitigation process caused a secondary failure in our API, elevating the RevenueCat API error rates as well. This primarily affected get subscriber info and post receipt. SDK caches and redundancies will provide fallbacks for most cases, but S2S calls will also be affected. Apple's servers have recovered and we're investigating the root cause of our mitigation failures.

Apple's StoreKit 2 APIs are returning 5xx errors about 60% of the time, we've enabled RC Fortress™ so any purchases that do go through with Apple will process, however we are seeing issues on the purchasing side between the device and Apple that may depress purchase rates as well.

We're investigating an increase in errors from Apple's API.

Additional resources seem to have improved the issue, we're continuing to monitor the situation but error rates are normal.

We've identified the issue at the database level and have provisioned additional resources to mitigate degradation. We're continuing to investigate the root cause.

We are investigating an elevation of 500s on the API.

We have deployed the fix and dashboard is working as expected. You should be able to save any changes in your app configuration now. We apologize for any convenience caused.

We are continuing to investigate this issue.

We're aware of a bug on the dashboard where users are unable to save their app configuration. We're working on a fix right now. Apologies for the inconvenience.

All Overview metrics have been updated, along with the corresponding "last updated" tooltips. Thanks for your patience in the meantime!

We've identified the issue, and it is specifically causing some metrics on Overview to be stale. All Charts are up to date. The issue additionally affects the "last updated" tooltips provided on Overview and Charts. We'll update the incident once the Overview metrics have been refreshed, and the "last updated" values have been fixed.

We are currently investigating an issue with our data pipelines. Charts, subscriber lists, scheduled data exports, and other dashboard features may be showing data that is more stale than usual. This doesn't impact the RevenueCat SDK and other non-dashboard features.

This issue is fully resolved now.

Everything except experiments results has caught up. We have also updated our monitoring to address this blind spot to ensure similar issues do not happen again in the future. This incident will be closed out once experiments results have caught up.

Last seen data (last seen time, last seen country, last seen platform, etc) is missing from roughly 11/28 until now in charts, overview tiles, and customer lists. We have identified the problem and the data is catching up. This incident will be closed out once everything is caught up.

Issue has been resolved.

A fix has been implemented and we are monitoring the results.

Our cache system was down temporarily and we had elevated error rates from 15:14 UTC to 15:24 UTC. We've remediated the issue and error rates have returned to normal. We're working through further resolution steps now.

Issue has been fixed, sorry for the inconvenience.

We are currently investigating an issue with the RevenueCat dashboard (app.revenuecat.com) not loading correctly. API traffic (including apps using the RevenueCat SDK) are not impacted.

For about 55 mins Apple servers were returning HTTP 5xx errors or had degraded performance for 2% of POST receipt requests. The service seems to operate normally again since 20:30 UTC. We have re-processed all the purchases that were potentially affected so there is NO data loss or missed purchases.

This incident has been resolved.

We identified the issue as an ongoing outage on Stripe. Stripe notified us that a fix should roll out soon. Our team is monitoring and will update shortly. Thanks for your patience.

Developers are currently unable to connect their Stripe accounts through the RevenueCat app in the Stripe Marketplace. Existing integrations between RevenueCat and Stripe continue to function normally, so there is no disruption for current users or ongoing billing operations. We're currently investigating.

We experienced an increased in error rate between UTC 09:43 to 09:48am. The issue has been resolved.

We experienced an increased error rate between 10:27 and 10:29am UTC. You may see a spike of 500 errors as a result. It has since been resolved.

Apple StoreKit1 still operates normally according to our metrics and Apple has now marked the issue as resolved on their side. We will keep re-submitting the failed receipts.

Service seems to be working normally for quite some time now. However, Apple has not marked the incident as resolved yet. We are re-submitting all the incoming receipts that were failing during the incident to make sure that there is no data loss.

The errors seem to be down. We keep monitoring.

Apple is now reporting the incident. We slowly see the errors going down. https://www.apple.com/support/systemstatus/

We started receiving bad responses from Apple's Store Kit 1 endpoint. This causes some of the Apple receipt submissions to fail. We are investigating the issue and working on a mitigation.

Our team noticed a delay in our processing of purchase status changes. A fix to our infrastructure was applied. Our frequency of updates is back to normal. Apologies for this issue happening again - we are actively working on improvements to prevent future regressions.

And we're back! Or rather, the effected Stripe API is: Subscriptions are being validated again We've disabled Fortress, and any temporarily granted entitlements will be rechecked

To mitigate the impact of Stripe's subscription API issue, we’ve enabled Fortress for Stripe payments. This means new purchases will temporarily have entitlements granted without the usual validation checks. Once the effected Stripe API is functioning normally, we’ll disable Fortress and revalidate purchases. Any mistakenly granted entitlements will be revoked, but all legitimate purchases will retain uninterrupted access to content. We’ll continue to monitor the situation closely and provide further updates. Thank you for your understanding!

An ongoing issue with one of Stripe’s subscription API's is impacting our ability to validate purchases. Our engineering team is monitoring the issue, actively exploring ways to mitigate the impact for RevenueCat users and will provide updates as soon as we have more information. We apologize for any inconvenience this may cause and appreciate your patience.

Our team noticed a delay in our processing of purchase status changes. A fix to our infrastructure was applied. Our frequency of updates is back to normal.

This incident has been resolved.

We continue monitoring metrics.

Looks the like the main issues has been resolved, latency and errors have dropped back to normal values. All APIs are working as expected now.

We are observing elevated error rates for our API. A minority of our web servers have been marked as unhealthy by our cloud provider. We are currently investigating and rotating the affected servers.

This incident has been resolved.

Issue has been fix, our team is monitoring and running tests

Customer list export CSVs are returning additional currency conversions in the total_spent column, our team is working towards fixing the issue.

This incident has been resolved.

Issue has been mitigated, we are monitoring to ensure all charts are back to normal.

Due to a data issue the revenue chart is not loading properly. We have identified the issues and we are working on a fix. Sorry for the inconveniences.

This incident has been resolved.

We experienced a delay in delivering webhook and integration events to our customers. The issue has been mitigated, and normal operations should resume shortly. We apologize for any inconvenience this may have caused and appreciate your patience.

This incident has been resolved.

We have discovered an issue that was affecting the data replication so charts and other data features were being generated with stale data. This has been fixed and the fresh data will start to show up shortly. We apologize for any inconvenience this might have caused.

We have discovered an issue that was affecting the data replication so charts and other data features were being generated with stale data. This has been fixed and the fresh data will start to show up shortly. We apologize for any inconvenience this might have caused.

We have discovered an issue that was affecting the data replication so charts and other data features were being generated with stale data. This has been fixed and the fresh data will start to show up shortly. We apologize for any inconvenience this might have caused.

We are currently investigating this issue.

Everything is all caught up now.

Scheduled data exports (aka ETLs) are now all caught up.

An infrastructure change to our data warehouse system has inadvertently caused delays to scheduled data exports (previously known as ETL exports), charts data, and customer lists data. We have identified the issue and it should resolve itself in the coming hours. For scheduled data exports, they will resume delivery automatically once the incident is resolved. This incident will remain open until things are fully resolved.

All Charts have been refreshed, and will continue to be refreshed at their typical cadence.

Most charts such as Active Subscriptions, Revenue, MRR, and our conversion charts have now been refreshed and are back to their normal schedule. We expect the last delayed charts such as the Realized LTV charts to be refreshed soon, at which point the incident will be marked as resolved.

We've identified an issue causing delayed data refreshes for Charts. We're working to resolve that issue now and refresh all Charts, and will keep this incident updated as that process completes. We apologize for any inconvenience caused in the meantime!

This incident has been resolved. API is operating normally.

We experienced a degraded performance in our AP from around 21:32 to 21:39 UTC today. It has now recovered and we’re monitoring.

This incident has been resolved.

The issue has been fixed and normal API traffic is recovering. This outage will be closed out once all impacted traffic has been replayed.

The RevenueCat backend is experiencing significant performance issues. We have redirected traffic to our emergency failover system to capture purchases. All receipts will be captured and replayed.

The bug on Apple’s side is not yet resolved, but with the mitigation we have in place the impact remains negligible. Particularly, in very rare cases, “Billing Issue” events with wrong timing may appear in RC dashboard and ETL exports. Those events will not be dispatched to integrations such as Webhooks. Provision of Entitlements, subscriptions status and other critical functionalities are completely unaffected. We consider the issue solved for Revenue Cat customers but we will continue seeking updates from Apple for the resolution of the root cause.

Since July 16 at 23:30 UTC we started getting a significantly lower amount of problematic receipts. There is no official answer about the issue from Apple yet. Our mitigation is still enabled and we keep tracking the issue. We will be updating this status page with any news.

We are continuing to monitor the situation and our fix mitigated the old receipts that were being marked as “with billing issues” due to Apple returning isInBillingRetryPeriod for them. The involved receipts are old and they won’t affect the current user entitlements or subscription statuses. They were causing an increased number of events on our side since we constantly refresh them to keep their status up to date and catch differences.

We applied a mitigation to the issue. We are temporarily ignoring the changes sent by Apple that we believe to be wrong. Namely, the isInBillingRetryPeriod field is being incorrectly set to true for long expired transactions. We are keeping track of all the affected transactions and we will make sure to update them with accurate data once the issue is resolved by Apple. We will keep monitoring the situation and we’ll update this incident as soon as the situation is solved on Apple side.

We identified the issue in a change happening on Apple side. We notified Apple and we are working on a mitigation to reduce the impact until they provide a fix.

We noticed a significant increase of billing issues for long ago expired purchases reported by Apple APIs. We are suspecting a malfunction on Apple's systems and have already reported it. We will keep tracking the issue and look for possible mitigations on our side.

This incident has been resolved.

A fix has been implemented and data from July 1st looks good. We are monitoring the results.

Starting on July 1st, we have identified an issue where data is missing in Charts. Our engineering team is actively investigating the root cause of this issue.

All Apple consumable purchases have been restored. This incident is now resolved.

We have found and mitigated the issue. The issue was caused by a change in how consumables are processed. We are now restoring the Apple consumable purchases.

We have received reports that iOS non-subscription purchases are failing for some customers. We’re working to find the root cause now.

The issue has been resolved, and all customer statuses reported in Customer Lists are up to date as of the latest data refresh. The displayed values in your lists may still be cached for up to an hour, but you can hard refresh them by modifying the list definition, or waiting for the next refresh. Should you have any questions regarding your Customer Lists data, please feel free to reach out to us and we will be happy to assist.

We've identified a problem causing the statuses of some customers in Customer Lists to be stale, and are working to remediate the issue now. We will provide updates as we make progress.

All purchases were replayed. Marking the incident as resolved

The release is now live and non subscription purchases on Google should be working as expected. We are working on replaying all failed to process purchases

We have just merged the fix to handle this unexpected change. Going through the release pipeline

Updated status page title to reflect impact. Non subscription products are impacted. We are working on a fix. Will replay the purchases once the fix is live

We have identified the issue. There was a change in the response from Google that made us wrongly process consumable purchases. We are working on a fix

We have reports of google consumables not working for some customers. We are investigating

This incident has been resolved, duplicate customers in customer lists have been removed and numbers are back to normal.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

We are continuing to investigate this issue.

We are currently investigating an issue in which customers appear to be duplicated in customer lists

The incident has been resolved.

A fix has been implemented and we are monitoring the results.

We recently deployed a change to our authentication cookie domain and we've started seeing errors after login. We are currently working on a fix.

We identified and resolved an issue that affected the IP address information within our event data. Our system has built-in protections to ensure that the IP address recorded in subscriber attributes is always accurately captured. A refactor in our codebase inadvertently extended these protections to read operations, which led to an unintended override of the IP address when events were being created, generating the erroneous IP data in the events payload. This issue was confined to the event data and did not affect the integrity of the data stored in our databases. As a result, none of the data features \(Charts, SDEs, Customer Lists, Experiments etc\) have been impacted. We deeply regret any inconvenience this may have caused, maintaining the accuracy of our data is very important for us, and we will improve our system and processes to prevent these type of issues in the future. If you need events to be re-delivered with the correct IP address, do not hesitate to reach out to support.

The incident has been resolved and IP addresses reported in the webhook & integration events sent by our system should be correct.

The issue has been identified and a fix is being implemented

We have identified an issue where the IP addresses reported in the webhook & integration events sent by our system may be incorrect. We're currently investigating the issue.

All Apple services seem to be back online and outages have been marked as resolved in their status page.

New In-app purchases seem to be failing now as well. AppStore continues to be down.

The AppStore seems to be down, new apps cannot be downloaded but in-app purchases in already installed apps seem to be working. No customer impact.