RevenueCat reported this major-impact incident on its official status page on Feb 10, 2026, 20:45 UTC. It was resolved after 3h 50m.
Right now RevenueCat is operational. Live RevenueCat status →
This incident has been resolved.
The primary DNS servers have recovered and updates have propagated to most DNS providers. Note that some ISPs and network setups might cache DNS entries longer, so errors might persist and might take longer to resolve for some users.
We purged the DNS cache and are starting to see improving dashboard error rates. There is still a long tail of errors we are monitoring.
We are continuing to monitor for any further issues.
We’ve recovered the SDK API, and purchases from your app are now being processed successfully. Some dashboard functionality and paywall assets may still be unavailable. Our team is continuing to work on mitigating the CloudFront issues, and we’ll share further updates as progress is made.
We’ve recovered the SDK API, and purchases from your app are now being processed successfully. Some dashboard functionality may still be unreliable. Our team is continuing to work on mitigating the CloudFront issues, and we’ll share further updates as progress is made.
We believe we have identified an issue with Cloudfront, and we have applied an emergency mitigation. We're seeing recovery on SDK APIs.
We're currently investigating an increased error rate on some of our APIs.
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