RevenueCat incident: Increased rate-limit errors on API V2 endpoints

Affected components

• API Uptime

1. resolvedApr 22, 2026, 19:42 UTC

   The incident has been resolved.

2. monitoringApr 22, 2026, 19:24 UTC

   A fix has been implemented and rate-limit errors are back to baseline. We will continue to monitor.

3. identifiedApr 22, 2026, 19:09 UTC

   At 18:27 UTC we noticed an increase in rate-limit errors from our v2 API endpoints for some developers since ~14:00 UTC. We have identified the issue and are implementing a fix.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in RevenueCat's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• Mux: Increased re-buffering and errors for some assets and live streamsMajor · Apr 22, 2026, 18:10 UTC
• Snyk: Snyk recurring tests showing slow performanceMinor · Apr 21, 2026, 18:58 UTC
• Smartsheet: Investigating Workspace panel not opening or closing unexpectedlyMinor · Apr 22, 2026, 16:45 UTC

How often does RevenueCat have incidents?

RevenueCat reported 6 incidents in the last 90 days, 3 of them major or critical. A typical incident lasted 1h 36m. See RevenueCat's uptime and incident history