Skip to main content
RevenueCat

Elevated error rates on RevenueCat APIs

Partial outage Lasted 1h 22m · started · RevenueCat's page

Level
confirmed
Worst impact
Partial outage
Components
API Uptime
Down Index
29of 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 1h 22m it lasted.

    Anything that failed between 2026-08-10 18:37 UTC and 2026-08-10 19:59 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 3

  1. investigating

    We are currently investigating elevated error rates and latency across multiple of our APIs

    provider

  2. identified

    We have rolled out a fix and are seeing early signs of improvement.

    provider

  3. resolved

    Error rates and latency have returned back to normal.

    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-cd25d1a067

Is RevenueCat still down?

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

How long did it last?

1h 22m, from 2026-08-10 18:37 UTC to 2026-08-10 19:59 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.