RevenueCat outage: Rico is having issues

Affected components

• AI features

1. resolvedAug 6, 2026, 18:14 UTC

   Rico continues recovered and stable, we consider the incident resolved.

2. monitoringAug 6, 2026, 17:16 UTC

   Our upstream AI inference provider has recovered, and Rico is now operating normally. We're continuing to monitor closely to confirm full stability before marking this resolved. We will provide a final update shortly.

3. identifiedAug 6, 2026, 17:06 UTC

   We've identified the issue: an outage with one of our upstream AI inference providers is causing Rico to fail. This is an external dependency issue, and we are actively monitoring the provider's status and working on mitigation options. We will post another update as soon as we have more information.

4. investigatingAug 6, 2026, 17:04 UTC

   We are currently investigating a complete outage affecting Rico. All requests to the service are failing at this time. We will provide an update as soon as we have more information.

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.

• GitHub: Incident with ActionsCritical · Aug 6, 2026, 15:22 UTC
• Elasticsearch: Elasticsearch 9.5.0 contains a query-correctness defectMajor · Aug 5, 2026, 22:59 UTC
• Elasticsearch: GCP asia-south1 high latencyMajor · Aug 6, 2026, 17:41 UTC
• HashiCorp Vault: HCP Terraform is unable to communicate with VCS endpoints using certain IP addresses.Minor · Aug 5, 2026, 19:08 UTC
• Snyk: SNYK-US-01 Test Service DegradationMinor · Aug 5, 2026, 19:26 UTC
• Vercel: Delays delivering log drainsMinor · Aug 6, 2026, 16:37 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