Skip to main content
RevenueCat

Increased API error rates due to reduced service capacity.

Degraded Lasted 12h 36m · started · RevenueCat's page

Level
confirmed
Worst impact
Degraded
Components
API Uptime
Down Index
24of 100

What to do

  • Check whether you use RevenueCat API Uptime. 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 12h 36m it lasted.

    Anything that failed between 2026-05-08 00:51 UTC and 2026-05-08 13:27 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 6

  1. investigating

    We are currently investigating elevated API error rates caused by reduced service capacity. Some end users may experience intermittent issues when making purchases or restoring subscriptions. Subscription activations may also be delayed temporarily. Most requests will continue to succeed, and affected transactions will automatically recover once service is restored. This issue is impacting RevenueCat API requests across iOS, Android, and Web platforms. Analytics processing and exports may also be delayed during this incident. We are actively restoring capacity and mitigating the issue. RevenueCat Fortress protections remain active to help preserve transaction data during the disruption. We will continue to provide updates as recovery progresses.

    provider

  2. investigating

    We are continuing to investigate this issue.

    provider

  3. identified

    We are starting to see some recovery. The underlying incident on our cloud provider is still not resolved, but metrics look good on our end. We are continuing to monitor.

    provider

  4. monitoring

    We are fully recovered now. We'll leave this incident open until our cloud provider confirms a full recovery.

    provider

  5. monitoring

    Our API has been fully operational since ~ 01:20 UTC. The underlying incident on our cloud provider is not yet closed, but is not impacting our service. As of ~ 05:20 UTC, all transactions processed by our Fortress protection have been replayed and should show up in the dashboard. The RevenueCat SDK will handle the API service degradation (from 00:17 UTC to 01:20 UTC) gracefully (no lost transactions).

    provider

  6. resolved

    This incident has been resolved.

    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-8139e7909c

Is RevenueCat still down?

No, this incident was resolved 2026-05-08 13:27 UTC. For RevenueCat's live state, see https://down.guide/revenuecat.

How long did it last?

12h 36m, from 2026-05-08 00:51 UTC to 2026-05-08 13:27 UTC, by the times RevenueCat posted.

What was affected?

RevenueCat named API Uptime.

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.