Skip to main content
RevenueCat

Increased API errors

Degraded Lasted 7h 48m · started · RevenueCat's page

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

Summary

RevenueCat says it is investigating elevated API errors, which were reported at 00:13 UTC on 2026-11-10. At 00:24 UTC it said the API had recovered and it is in contact with its main cloud provider to determine the root cause, and it is now monitoring.

Written by anthropic/claude-haiku-5.5 from RevenueCat's own updates.

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 7h 48m it lasted.

    Anything that failed between 2026-11-10 00:13 UTC and 2026-11-10 08:01 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 API errors

    provider

  2. monitoring

    API is recovered, and we're in contact with our main cloud provider to determine the root cause of what seems like a problem on their end. We'll provide more updates soon.

    provider

  3. resolved

    We traced the root cause of the elevated error rate back to an issue with how our backend processed certain media assets. A spike of uploads caused our servers to be temporarily overloaded processing those assets. This issue has been fixed.

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

Is RevenueCat still down?

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

How long did it last?

7h 48m, from 2026-11-10 00:13 UTC to 2026-11-10 08:01 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.