Company Logo

Is there an RevenueCat outage?

RevenueCat status: Systems Active

Last checked: 6 minutes ago

Get notified about any outages, downtime or incidents for RevenueCat and 1800+ other cloud vendors. Monitor 10 companies, for free.

Subscribe for updates

RevenueCat outages and incidents

Outage and incident data over the last 30 days for RevenueCat.

There have been 2 outages or incidents for RevenueCat in the last 30 days.

Severity Breakdown:

Tired of searching for status updates?

Join OutLogger to be notified when any of your vendors or the components you use experience an outage. It's completely free and takes less than 2 minutes!

Sign Up Now

Components and Services Monitored for RevenueCat

Outlogger tracks the status of these components for Xero:

API Uptime Active
Documentation Active
Event Dispatching Active
Scheduled Data Exports Active
Apple Receipt Server Active
Apple Sandbox Receipt Server Active
Google Play Store Receipt Server Active
Stripe Receipt Server Active
Charts Active
Customer Lists Active
Overview Active
Component Status
API Uptime Active
Documentation Active
Event Dispatching Active
Scheduled Data Exports Active
Active
Apple Receipt Server Active
Apple Sandbox Receipt Server Active
Google Play Store Receipt Server Active
Stripe Receipt Server Active
Active
Charts Active
Customer Lists Active
Overview Active

Latest RevenueCat outages and incidents.

View the latest incidents for RevenueCat and check for official updates:

Updates:

  • Time: April 13, 2023, 9:56 p.m.
    Status: Resolved
    Update: This incident has been resolved.
  • Time: April 13, 2023, 7:31 p.m.
    Status: Monitoring
    Update: Service are operational but we'll keep monitoring the situation
  • Time: April 13, 2023, 7:14 p.m.
    Status: Monitoring
    Update: Apple's servers seem to have recovered, we are not getting elevated errors from App Store Servers anymore. We have gone to regularly processing purchases and we are monitoring the situation closely.
  • Time: April 13, 2023, 7:02 p.m.
    Status: Identified
    Update: We are mitigating the issue by granting entitlements without verifying receipts through Apple's servers to ensure that end customers get access to their purchases and will verify the purchases with Apple once Apple's servers have recovered.
  • Time: April 13, 2023, 6:30 p.m.
    Status: Investigating
    Update: We are seeing an increase of errors coming from Apple's App Store servers, impacting purchases in production. We are monitoring if Apple's servers will recover and investigating ways to mitigate the impact for RevenueCat customers.

Updates:

  • Time: April 13, 2023, 9:56 p.m.
    Status: Resolved
    Update: This incident has been resolved.
  • Time: April 13, 2023, 7:31 p.m.
    Status: Monitoring
    Update: Service are operational but we'll keep monitoring the situation
  • Time: April 13, 2023, 7:14 p.m.
    Status: Monitoring
    Update: Apple's servers seem to have recovered, we are not getting elevated errors from App Store Servers anymore. We have gone to regularly processing purchases and we are monitoring the situation closely.
  • Time: April 13, 2023, 7:02 p.m.
    Status: Identified
    Update: We are mitigating the issue by granting entitlements without verifying receipts through Apple's servers to ensure that end customers get access to their purchases and will verify the purchases with Apple once Apple's servers have recovered.
  • Time: April 13, 2023, 6:30 p.m.
    Status: Investigating
    Update: We are seeing an increase of errors coming from Apple's App Store servers, impacting purchases in production. We are monitoring if Apple's servers will recover and investigating ways to mitigate the impact for RevenueCat customers.

Updates:

  • Time: April 5, 2023, 6:47 p.m.
    Status: Resolved
    Update: This incident has been resolved.
  • Time: April 5, 2023, 6:47 p.m.
    Status: Resolved
    Update: This incident has been resolved.
  • Time: April 5, 2023, 6:37 p.m.
    Status: Monitoring
    Update: The data in Customer Lists has been updated with the most recent changes. We are going to keep monitoring for a while but all should be back to normal.
  • Time: April 5, 2023, 6:37 p.m.
    Status: Monitoring
    Update: The data in Customer Lists has been updated with the most recent changes. We are going to keep monitoring for a while but all should be back to normal.
  • Time: April 5, 2023, 6:27 p.m.
    Status: Identified
    Update: The issue that caused the errors has been identified and fixed. We are now working on adding the most up-to-date data into the Customer Lists feature.
  • Time: April 5, 2023, 5:54 p.m.
    Status: Identified
    Update: We've detected an increase in errors in our Customer lists exports. Current data in exports is delayed around 12 hours. Customer lists in dashboard are not affected, but exports contain delayed information. We are currently fixing the problem and we will update soon once it is done.
  • Time: April 5, 2023, 5:54 p.m.
    Status: Identified
    Update: We've detected an increase in errors in our Customer lists exports. Current data in exports is delayed around 12 hours. Customer lists in dashboard are not affected, but exports contain delayed information. We are currently fixing the problem and we will update soon once it is done.

Updates:

  • Time: March 29, 2023, 6:06 p.m.
    Status: Resolved
    Update: Engineers have confirmed that all of the receipts that made it to our servers were replayed and reprocessed. We have another redundant layer of logs that we have also replayed as a backup. Number of purchases in our systems look consistent with the traffic from previous days. Additionally, SDKs will retry any receipt that did not make it to our severs, although we expect them to be minimal. Customer Lists are also catching up with the latest updates. We are closing the incident as all systems are operational. We are very sorry for any inconvenience caused, and we will keep working to make sure our backup systems are even smoother for the future. If you have any specific concerns related to your app or customers, do not hesitate to reach out to RevenueCat support.
  • Time: March 29, 2023, 2:16 p.m.
    Status: Monitoring
    Update: All read paths have been restored. This incident will stay open until we confirm that all receipts have been replayed correctly. The vast majority of receipts have been replayed earlier, but we are doing final checks to make sure everything has been captured.
  • Time: March 29, 2023, 1:27 p.m.
    Status: Monitoring
    Update: Last seen data (subscriber last seen time, last seen country, last seen platform, etc) is being written again. Everything should now be receiving accurate last seen data with the exception of the subscriber info endpoint. Once we verify our last seen data infrastructure is reliable, we will enable this last read path.
  • Time: March 29, 2023, 9:10 a.m.
    Status: Investigating
    Update: To learn more about the work done on new mitigation tooling, check here: https://twitter.com/jeiting/status/1639393214837694464
  • Time: March 29, 2023, 9:06 a.m.
    Status: Investigating
    Update: Services are fully restored. With our new mitigation tool in place (details here: https://twitter.com/jeiting/status/1639393214837694464), there was minimal disruption for the customers and there was no data loss. SDK users were able to unlock purchases. However there were delays in Stripe and consumable purchases, as well as some webhooks. But purchase data was not lost. We are working on catching up on the last-seen data (which mostly affects charts). We will keep you posted on the progress. Meanwhile if you have any questions, please do not hesitate to reach out to RevenueCat Support.
  • Time: March 29, 2023, 6:46 a.m.
    Status: Investigating
    Update: Update: Most services have been restored, however some users may see stale last-seen data. Engineers are arranging to replay purchases into the primary database. We will update again when the system is fully restored.
  • Time: March 29, 2023, 5:37 a.m.
    Status: Investigating
    Update: Engineers have traced the issue to one of our non-critical storage layers and are looking at ways to bypass. New purchases are still succeeding. More updates as investigation proceeds.
  • Time: March 29, 2023, 5:15 a.m.
    Status: Investigating
    Update: We are continuing to investigate this issue.
  • Time: March 29, 2023, 5:13 a.m.
    Status: Investigating
    Update: Engineers are mitigating the issue by enabling our backup systems which is expected to allow purchases to proceed. Engineers anticipate no impact to new and existing purchases. Webhooks may be delayed. More updates as investigation proceeds.

Updates:

  • Time: March 29, 2023, 6:06 p.m.
    Status: Resolved
    Update: Engineers have confirmed that all of the receipts that made it to our servers were replayed and reprocessed. We have another redundant layer of logs that we have also replayed as a backup. Number of purchases in our systems look consistent with the traffic from previous days. Additionally, SDKs will retry any receipt that did not make it to our severs, although we expect them to be minimal. Customer Lists are also catching up with the latest updates. We are closing the incident as all systems are operational. We are very sorry for any inconvenience caused, and we will keep working to make sure our backup systems are even smoother for the future. If you have any specific concerns related to your app or customers, do not hesitate to reach out to RevenueCat support.
  • Time: March 29, 2023, 2:16 p.m.
    Status: Monitoring
    Update: All read paths have been restored. This incident will stay open until we confirm that all receipts have been replayed correctly. The vast majority of receipts have been replayed earlier, but we are doing final checks to make sure everything has been captured.
  • Time: March 29, 2023, 1:27 p.m.
    Status: Monitoring
    Update: Last seen data (subscriber last seen time, last seen country, last seen platform, etc) is being written again. Everything should now be receiving accurate last seen data with the exception of the subscriber info endpoint. Once we verify our last seen data infrastructure is reliable, we will enable this last read path.
  • Time: March 29, 2023, 9:10 a.m.
    Status: Investigating
    Update: To learn more about the work done on new mitigation tooling, check here: https://twitter.com/jeiting/status/1639393214837694464
  • Time: March 29, 2023, 9:06 a.m.
    Status: Investigating
    Update: Services are fully restored. With our new mitigation tool in place (details here: https://twitter.com/jeiting/status/1639393214837694464), there was minimal disruption for the customers and there was no data loss. SDK users were able to unlock purchases. However there were delays in Stripe and consumable purchases, as well as some webhooks. But purchase data was not lost. We are working on catching up on the last-seen data (which mostly affects charts). We will keep you posted on the progress. Meanwhile if you have any questions, please do not hesitate to reach out to RevenueCat Support.
  • Time: March 29, 2023, 6:46 a.m.
    Status: Investigating
    Update: Update: Most services have been restored, however some users may see stale last-seen data. Engineers are arranging to replay purchases into the primary database. We will update again when the system is fully restored.
  • Time: March 29, 2023, 5:37 a.m.
    Status: Investigating
    Update: Engineers have traced the issue to one of our non-critical storage layers and are looking at ways to bypass. New purchases are still succeeding. More updates as investigation proceeds.
  • Time: March 29, 2023, 5:15 a.m.
    Status: Investigating
    Update: We are continuing to investigate this issue.
  • Time: March 29, 2023, 5:13 a.m.
    Status: Investigating
    Update: Engineers are mitigating the issue by enabling our backup systems which is expected to allow purchases to proceed. Engineers anticipate no impact to new and existing purchases. Webhooks may be delayed. More updates as investigation proceeds.

Check the status of similar companies and alternatives to RevenueCat

Hudl
Hudl

Systems Active

OutSystems
OutSystems

Systems Active

Postman
Postman

Systems Active

Mendix
Mendix

Systems Active

DigitalOcean
DigitalOcean

Issues Detected

Bandwidth
Bandwidth

Issues Detected

DataRobot
DataRobot

Systems Active

Grafana Cloud
Grafana Cloud

Systems Active

SmartBear Software
SmartBear Software

Systems Active

Test IO
Test IO

Systems Active

Copado Solutions
Copado Solutions

Systems Active

CircleCI
CircleCI

Systems Active

Frequently Asked Questions - RevenueCat

Is there a RevenueCat outage?
The current status of RevenueCat is: Systems Active
Where can I find the official status page of RevenueCat?
The official status page for RevenueCat is here
How can I get notified if RevenueCat is down or experiencing an outage?
To get notified of any status changes to RevenueCat, simply sign up to OutLogger's free monitoring service. OutLogger checks the official status of RevenueCat every few minutes and will notify you of any changes. You can veiw the status of all your cloud vendors in one dashboard. Sign up here
What does RevenueCat do?
RevenueCat simplifies in-app purchases and subscriptions on iOS, Android, and the web without the need for server code. Sign up for free.

Start monitoring now!

Join OutLogger to be notified when any of your vendors or the components you use experience an outage or down time. Join for free - no credit card required.

Get Started for Free