RevenueCat incident: Elevated error rates

Affected components

• API Uptime
• Event Dispatching

1. resolvedApr 28, 2026, 22:54 UTC

   All systems are now operating normally. Event delivery has fully caught up, and performance has returned to expected levels.

2. monitoringApr 28, 2026, 22:32 UTC

   A fix has been implemented to address database deadlocks that were degrading API performance. The system is now stable and performance has recovered. We are still observing some delays in webhook delivery, but these are improving and we expect them to fully recover shortly.

3. investigatingApr 28, 2026, 21:59 UTC

   We're currently investigating an increased error rate on some of our APIs

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.

• Snyk: Snyk recurring tests showing slow performanceMinor · Apr 21, 2026, 18:58 UTC
• GitHub: Incomplete pull request results in repositoriesMinor · Apr 28, 2026, 14:17 UTC
• Akamai: Intermittent Edge Delivery Delays in Chennai, IN (MAA) RegionMinor · Apr 28, 2026, 16:42 UTC
• Linode: Service Issue - Connectivity Issues - Chennai (IN-MAA)Minor · Apr 28, 2026, 17:17 UTC
• Inngest: Increased function execution latencyMinor · Apr 28, 2026, 19:11 UTC
• npm: npm website degraded serviceMinor · Apr 28, 2026, 19:55 UTC

How often does RevenueCat have incidents?

RevenueCat reported 10 incidents in the last 90 days, 5 of them major or critical. A typical incident lasted 2h 20m. See RevenueCat's uptime and incident history