Company Logo

Is there an RevenueCat outage?

RevenueCat status: Systems Active

Last checked: 8 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: March 18, 2024, 11:18 p.m.
    Status: Resolved
    Update: We have replayed all the purchases, and the incident is now resolved.
  • Time: March 18, 2024, 7:04 p.m.
    Status: Monitoring
    Update: After some troubleshooting, we realized that the problem was on our side affecting that small percentage of requests. Our internal metrics were wrongly reporting that the problem was on Apple's side. We are replaying all requests to make sure no purchases were lost
  • Time: March 18, 2024, 5:01 p.m.
    Status: Monitoring
    Update: We are still seeing connection errors on Apple side when using StoreKit 1 - it bounces between 5% and 10% of those requests
  • Time: March 18, 2024, 2:03 p.m.
    Status: Monitoring
    Update: We are monitoring the problem. Seems that Apple is recovering. We'll continue to monitor the situation and once it's fully recovered, we'll replay all purchases that failed during that period. If users are affected, they will be able to resolve by restoring purchases or re opening the app
  • Time: March 18, 2024, 2:01 p.m.
    Status: Identified
    Update: All errors are coming from Apples' Servers - Connection Timeouts
  • Time: March 18, 2024, 1:59 p.m.
    Status: Investigating
    Update: We are seeing a low percentage (~7%) of failures on POST /receipts using Apple - StoreKit 1

Updates:

  • Time: March 18, 2024, 11:18 p.m.
    Status: Resolved
    Update: We have replayed all the purchases, and the incident is now resolved.
  • Time: March 18, 2024, 7:04 p.m.
    Status: Monitoring
    Update: After some troubleshooting, we realized that the problem was on our side affecting that small percentage of requests. Our internal metrics were wrongly reporting that the problem was on Apple's side. We are replaying all requests to make sure no purchases were lost
  • Time: March 18, 2024, 5:01 p.m.
    Status: Monitoring
    Update: We are still seeing connection errors on Apple side when using StoreKit 1 - it bounces between 5% and 10% of those requests
  • Time: March 18, 2024, 2:03 p.m.
    Status: Monitoring
    Update: We are monitoring the problem. Seems that Apple is recovering. We'll continue to monitor the situation and once it's fully recovered, we'll replay all purchases that failed during that period. If users are affected, they will be able to resolve by restoring purchases or re opening the app
  • Time: March 18, 2024, 2:01 p.m.
    Status: Identified
    Update: All errors are coming from Apples' Servers - Connection Timeouts
  • Time: March 18, 2024, 1:59 p.m.
    Status: Investigating
    Update: We are seeing a low percentage (~7%) of failures on POST /receipts using Apple - StoreKit 1

Updates:

  • Time: March 18, 2024, 5:24 a.m.
    Status: Resolved
    Update: All metrics have been stable for some time now. Last seen data is being served as normal and all service is fully restored. This concludes the incident. Thank you for your patience and understanding.
  • Time: March 18, 2024, 4:41 a.m.
    Status: Monitoring
    Update: Last seen data is now back to normal. Updates are being stored, and the information is read back for the appropriate requests. We are doing some final checks and monitoring before declaring the incident as resolved.
  • Time: March 18, 2024, 4:06 a.m.
    Status: Monitoring
    Update: Engineers are still in the process of reading last seen data from the new cluster, but last seen data is now being written.
  • Time: March 17, 2024, 11:35 p.m.
    Status: Monitoring
    Update: The new cluster is online; engineers are slowly ramping up traffic to it and verifying correctness and load.
  • Time: March 17, 2024, 11:18 p.m.
    Status: Monitoring
    Update: Unfortunately in the process of trying to recover last seen data during the previous incident, the cluster was discovered not to be able to handle the load. Engineers have worked to bring last seen data into a brand new cluster with increased capacity that will be sufficiently stable for the longer term, and will soon be able to begin using it for last seen data reads and writes.
  • Time: March 17, 2024, 10:15 p.m.
    Status: Identified
    Update: We are currently working to make the cluster that holds last seen data fully operational.
  • Time: March 17, 2024, 9:01 p.m.
    Status: Investigating
    Update: We are continuing to investigate this issue.
  • Time: March 17, 2024, 7:51 p.m.
    Status: Investigating
    Update: Last seen data may be missing from some responses and outdated in others. Our engineers are working on the cluster that stores this data to recover this functionality fully.

Updates:

  • Time: March 18, 2024, 5:24 a.m.
    Status: Resolved
    Update: All metrics have been stable for some time now. Last seen data is being served as normal and all service is fully restored. This concludes the incident. Thank you for your patience and understanding.
  • Time: March 18, 2024, 4:41 a.m.
    Status: Monitoring
    Update: Last seen data is now back to normal. Updates are being stored, and the information is read back for the appropriate requests. We are doing some final checks and monitoring before declaring the incident as resolved.
  • Time: March 18, 2024, 4:06 a.m.
    Status: Monitoring
    Update: Engineers are still in the process of reading last seen data from the new cluster, but last seen data is now being written.
  • Time: March 17, 2024, 11:35 p.m.
    Status: Monitoring
    Update: The new cluster is online; engineers are slowly ramping up traffic to it and verifying correctness and load.
  • Time: March 17, 2024, 11:18 p.m.
    Status: Monitoring
    Update: Unfortunately in the process of trying to recover last seen data during the previous incident, the cluster was discovered not to be able to handle the load. Engineers have worked to bring last seen data into a brand new cluster with increased capacity that will be sufficiently stable for the longer term, and will soon be able to begin using it for last seen data reads and writes.
  • Time: March 17, 2024, 10:15 p.m.
    Status: Identified
    Update: We are currently working to make the cluster that holds last seen data fully operational.
  • Time: March 17, 2024, 9:01 p.m.
    Status: Investigating
    Update: We are continuing to investigate this issue.
  • Time: March 17, 2024, 7:51 p.m.
    Status: Investigating
    Update: Last seen data may be missing from some responses and outdated in others. Our engineers are working on the cluster that stores this data to recover this functionality fully.

Updates:

  • Time: March 17, 2024, 6:48 p.m.
    Status: Resolved
    Update: Update: last seen data is fully restored and we are fully recovered. This resolves the incident. Engineers will continue monitoring, and will follow up internally with intention of preventing further recurrences.
  • Time: March 17, 2024, 6:34 p.m.
    Status: Identified
    Update: Engineers have increased the capacity of the cluster which serves last seen data, and are bringing load back over to it gradually. We will update again when last seen data is enabled 100%.
  • Time: March 17, 2024, 6:34 p.m.
    Status: Identified
    Update: We are continuing to work on a fix for this issue.
  • Time: March 17, 2024, 5:26 p.m.
    Status: Identified
    Update: Engineers have completed re-synchronizing purchases which were temporarily granted during the initial mitigation, and have restored RevenueCat's backend systems to their non-degraded state, with the exception of last seen data which is not being read or written. As a result of this unplanned downtime and until further notice, last seen data may be missing from some responses and outdated in others. However, response times and success rates can be expected to be normal. Engineers are working to bring back the systems that store and provide last seen information.
  • Time: March 17, 2024, 4:44 p.m.
    Status: Identified
    Update: Most systems are back to normal. Only impacted problem that we haven't solved is last_seen fields. We are replaying all impacted purchases
  • Time: March 17, 2024, 4:29 p.m.
    Status: Identified
    Update: We've isolated the system causing the issue and disabled it. Service is slightly degraded
  • Time: March 17, 2024, 4:15 p.m.
    Status: Investigating
    Update: Our engineers detected degraded performance and performed an emergency mitigation while we investigate

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