RevenueCat incident: Increased API error rates due to reduced service capacity.

Affected components

• API Uptime

1. resolvedMay 8, 2026, 13:27 UTC

   This incident has been resolved.

2. monitoringMay 8, 2026, 10:03 UTC

   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).

3. monitoringMay 8, 2026, 01:22 UTC

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

4. identifiedMay 8, 2026, 01:15 UTC

   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.

5. investigatingMay 8, 2026, 00:52 UTC

   We are continuing to investigate this issue.

6. investigatingMay 8, 2026, 00:51 UTC

   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.

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.

• ReadMe: Issues Creating New ChangelogsCritical · May 7, 2026, 23:43 UTC
• Datadog: Delayed Monitors NotificationsCritical · May 8, 2026, 00:06 UTC
• Upstash: QStash US Region Service DisruptionCritical · May 8, 2026, 09:46 UTC
• Convex: Intermittent Impact from AWS OutageMajor · May 8, 2026, 00:16 UTC
• Confluent Cloud: Elevated error rates and latency on produce and consume operations on AWS us-east-1 AZ4Major · May 8, 2026, 01:14 UTC
• Intercom: Investigating: Compromised version of intercom-client npm package and intercom-phpMinor · Apr 30, 2026, 16:58 UTC
• Snyk: Snyk Recurring Tests DelayedMinor · May 6, 2026, 15:32 UTC
• Bitbucket: Multiple Atlassian services are experiencing issuesMinor · May 8, 2026, 01:31 UTC
• Confluence: Multiple Atlassian services are experiencing issuesMinor · May 8, 2026, 01:31 UTC
• MongoDB Atlas: AWS Availability Zone use1-az4 in US-EAST-1 Region is ImpairedMinor · May 8, 2026, 02:24 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