RevenueCat incident
Increased API error rates due to reduced service capacity.
RevenueCat experienced a minor incident on May 8, 2026 affecting API Uptime, lasting 12h 35m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating May 08, 2026, 12:51 AM 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.
- investigating May 08, 2026, 12:52 AM UTC
We are continuing to investigate this issue.
- identified May 08, 2026, 01:15 AM 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.
- monitoring May 08, 2026, 01:22 AM UTC
We are fully recovered now. We'll leave this incident open until our cloud provider confirms a full recovery.
- monitoring May 08, 2026, 10:03 AM 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).
- resolved May 08, 2026, 01:27 PM UTC
This incident has been resolved.