Company Logo

Is there an RevenueCat outage?

RevenueCat status: Systems Active

Last checked: a minute 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: Feb. 20, 2024, 2:21 p.m.
    Status: Resolved
    Update: All purchases were replayed. Marking the incident as resolved
  • Time: Feb. 20, 2024, 12:27 a.m.
    Status: Monitoring
    Update: We have released a fix to Google Play Store consumables. We are working on replaying all purchases from the past few days that did not go through. If end users are not seeing their purchases, a restore will also fix it
  • Time: Feb. 20, 2024, 12:08 a.m.
    Status: Identified
    Update: Some updates: - We believe this is affecting ~10% of non-subscription purchases on Android - Google began, randomly, responding with the an incorrect error message on an API we use to determine if a purchase is a subscription or not. - We're rolling out a change that handles the Google error. - Following the deploy of the change, we will reprocess any receipts and should be able to correct most if not all instances of the issue.
  • Time: Feb. 19, 2024, 11:02 p.m.
    Status: Identified
    Update: There was a change on Google's endpoint that made RevenueCat not process consumables purchases correctly, releasing a fix
  • Time: Feb. 19, 2024, 10:44 p.m.
    Status: Investigating
    Update: We are seeing reports from customers that there are problems with consumables in Google Play Store. We are investigating

Updates:

  • Time: Feb. 13, 2024, 11:44 a.m.
    Status: Resolved
    Update: The team found the root cause of the incident and fixed it. The scheduled data exports should now be delivered on time.
  • Time: Feb. 13, 2024, 6:08 a.m.
    Status: Investigating
    Update: Our scheduled data exports infrastructure is running behind which is causing possible delays in the delivery of exports. Our engineers are investigating.

Updates:

  • Time: Feb. 13, 2024, 11:44 a.m.
    Status: Resolved
    Update: The team found the root cause of the incident and fixed it. The scheduled data exports should now be delivered on time.
  • Time: Feb. 13, 2024, 6:08 a.m.
    Status: Investigating
    Update: Our scheduled data exports infrastructure is running behind which is causing possible delays in the delivery of exports. Our engineers are investigating.

Updates:

  • Time: Feb. 5, 2024, 7:49 a.m.
    Status: Resolved
    Update: From 6:30 AM UTC on January 30th 2024 to 7:00 AM UTC on February 5th 2024, the subscriber details in the subscriber info endpoint (`/v1/subscribers`), the receipt endpoint (`/v1/receipts`) and the `customer_info` field in events sent to Firebase Cloud Functions can potentially contain incorrect information for subscribers with multiple RevenueCat promotional transactions. This only impacts customers that have 2 or more RevenueCat promotional transactions. It does not impact unlocking of entitlements via the RevenueCat SDK, even if a customer has 2 or more RevenueCat promotional transactions. For impacted subscribers, the subscriber response would have the following incorrect values: * The `product_id` field in the `entitlements` section can be incorrect for entitlements that are unlocked via RevenueCat promotional transactions. * In the `subscriptions` block, when there are multiple RevenueCat promotional transactions, only one will be in the block. Additionally, the key used (which is supposed to be the product identifier) can incorrectly be the product identifier for another promotional transaction for the customer. If you have any questions or concerns, please reach out to our support team. We apologize for any inconvenience caused, our test suite has been updated to ensure better coverage for multiple promotional transactions on the same subscriber.

Updates:

  • Time: Feb. 5, 2024, 7:49 a.m.
    Status: Resolved
    Update: From 6:30 AM UTC on January 30th 2024 to 7:00 AM UTC on February 5th 2024, the subscriber details in the subscriber info endpoint (`/v1/subscribers`), the receipt endpoint (`/v1/receipts`) and the `customer_info` field in events sent to Firebase Cloud Functions can potentially contain incorrect information for subscribers with multiple RevenueCat promotional transactions. This only impacts customers that have 2 or more RevenueCat promotional transactions. It does not impact unlocking of entitlements via the RevenueCat SDK, even if a customer has 2 or more RevenueCat promotional transactions. For impacted subscribers, the subscriber response would have the following incorrect values: * The `product_id` field in the `entitlements` section can be incorrect for entitlements that are unlocked via RevenueCat promotional transactions. * In the `subscriptions` block, when there are multiple RevenueCat promotional transactions, only one will be in the block. Additionally, the key used (which is supposed to be the product identifier) can incorrectly be the product identifier for another promotional transaction for the customer. If you have any questions or concerns, please reach out to our support team. We apologize for any inconvenience caused, our test suite has been updated to ensure better coverage for multiple promotional transactions on the same subscriber.

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