Skip to main content
RevenueCat

API partial outage, Scheduled Data Exports and Dashboard is down

Degraded Lasted 14h 37m · started · RevenueCat's page

Level
confirmed
Worst impact
Degraded
Components
API Uptime, Overview, Charts, Collaborators, Customer Lists, Scheduled Data Exports, Login, Event Dispatching, Paywalls Editor, RevenueCat Companion App
Down Index
34of 100

What to do

  • Check whether you use RevenueCat API Uptime, Overview, Charts, Collaborators and 6 more. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 14h 37m it lasted.

    Anything that failed between 2025-10-20 10:47 UTC and 2025-10-21 01:24 UTC may need a replay.
  • Subscribe to RevenueCat's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=revenuecat works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from RevenueCat 20

  1. identified

    A major outage in AWS is causing our Scheduled Data Exports and the data in our Charts to be delayed. Despite AWS services show some symptoms of recovery, there are big capacity problems and we are trying to bring more capacity as well as disabling non-critical features to handle the increasing load.

    provider

  2. identified

    We are adding capacity by transferring resources from non-critical services, and we are managing to keep up with the load.

    provider

  3. identified

    We have taken down our Charts temporarily to optimize traffic towards purchase handling, while AWS continues to have issues.

    provider

  4. identified

    We are continuing to work on a fix for this issue, optimizing traffic towards purchase handling while AWS continues to have issues.

    provider

  5. identified

    We are operating at elevated error rates on our API. We are continuing to add capacity and work to mitigate the issue.

    provider

  6. identified

    We are operating at elevated error rates on our API. We are continuing to add capacity and work to mitigate the issue. New purchases are partially down, however, we have enabled RevenueCat Fortress which will allow new purchases to get processed.

    provider

  7. identified

    We are operating at elevated error rates on our API. We are continuing to add capacity and work to mitigate the issue.

    provider

  8. identified

    We are continuing to work on a fix for this issue.

    provider

  9. identified

    Unfortunately our API backup service is also affected by the outage. A large percentage of new purchases being made through the SDK are still getting served with no visible issues due to our offline entitlements support: https://www.revenuecat.com/blog/engineering/introducing-offline-entitlements/ We continue our effort to bring our systems back to normal as soon as possible.

    provider

  10. identified

    We are working on implementing a fallback for SDK purchases in another AWS region. We'll provide another update in 30 minutes.

    provider

  11. identified

    We are continuing to work on the mitigations. We'll provide another update in 30 minutes.

    provider

  12. identified

    We are continuing to work on mitigations. We are slowly ramping up traffic to some AWS servers and monitoring.

    provider

  13. identified

    We're continuing to ramp up traffic to AWS servers and monitor performance. RevenueCat's dashboard and API will return errors as we work to mitigate them. Offline entitlements continue to work as before. We'll share another update in 30 minutes.

    provider

  14. identified

    We've directed all traffic to AWS and are seeing some improvements. - Purchasing in the SDK is operational - RevenueCat V1 APIs and V2 non-charts APIs are operational. - RevenueCat customer history is operational. - RevenueCat charts, Overview metrics, and SDEs are not operational. We plan on focusing next on replaying purchases that happened during the outage to recover purchase activity. We're continuing to monitor the system and will provide another update in 30 minutes.

    provider

  15. identified

    Our API's performance looks good, we are now working on replaying purchases from during the outage. We'll provide another update in 60 minutes.

    provider

  16. identified

    We have completed replaying all purchases that happened during the outage. We also attempted to deliver events to integrations corresponding to these purchases. Some integrations might not accept these events depending on their specific policies. If you have questions about your integrations, please reach out to support@revenuecat.com. As of right now, charts are outdated and SDEs are disabled. We are working next on recalculating charts and SDEs. We will provide another update in 60 minutes.

    provider

  17. monitoring

    Some charts have been recalculated and SDEs have been resumed. Customer lists are outdated and are being recalculated. We're continuing to recalculate charts. We'll provide another update in 60 minutes.

    provider

  18. monitoring

    Most charts have been recalculated and the remaining ones will be recalculated over the course of a few hours. Scheduled data exports are resumed and are being delivered over the course of a few hours. Customer Lists have been recalculated and are fully up to date. We'll continue monitoring and send a final update when we confirm the incident is resolved.

    provider

  19. monitoring

    Charts, scheduled data exports, and customer lists have fully recovered. All services are now operational. We will continue to monitor the situation closely.

    provider

  20. resolved

    There haven't been any issues since the last update so we are considering this incident resolved. A postmortem will be published soon.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-66e201c6cc

Is RevenueCat still down?

No, this incident was resolved 2025-10-21 01:24 UTC. For RevenueCat's live state, see https://down.guide/revenuecat.

How long did it last?

14h 37m, from 2025-10-20 10:47 UTC to 2025-10-21 01:24 UTC, by the times RevenueCat posted.

What was affected?

RevenueCat named API Uptime, Overview, Charts, Collaborators and 6 more.

What caused it?

RevenueCat hasn't published a root cause. If it does, it shows here.

Where does this come from?

RevenueCat's official status page, https://status.revenuecat.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.