RevenueCat reported this critical-impact incident on its official status page on Apr 18, 2026, 20:42 UTC. It was resolved after 28 min.
Right now RevenueCat is operational. Live RevenueCat status →
The underlying infrastructure issue has been addressed, and RevenueCat services are now operating normally again. Temporary mitigations have been removed as full service has been restored. We are continuing to monitor the system closely to ensure stability.
We are currently experiencing an incident affecting parts of RevenueCat’s web infrastructure. To reduce impact for customers and their users, mitigations have been activated: What should continue to work normally: apps should continue to load paywalls using cached product data, users should still be able to complete purchases, and users who purchase during this period should continue to receive access to the content or features they bought What will not work normally during this incident: some real-time and customization features may be degraded while Fortress is active. This includes Offering experiments and customer-specific Offering customization, which may not be applied during the incident. Webhooks and some third-party integration events may also be delayed rather than delivered in real time What happens after recovery: once normal service is restored, we will replay queued requests so purchase records, entitlement confirmation, webhooks, and downstream events can be reconcile
We have noticed a degradation of service and are investigating the issue.
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.
Overlapping incidents aren't necessarily related.
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