
RevenueCat Status
Real-time updates of RevenueCat issues and outages
RevenueCat status is Operational
AI features
RevenueCat Event Dispatching
Lior Grossman
Maker of StatusSight
I built StatusSight. Here's what I'm building next with AI.
In Lior Builds, my free newsletter, I share one story from a product I built with AI, plus short notes on the tools and models worth using: what worked, what did not, and the numbers behind it. Every week or two.
Active Incidents
No active incidents
Recently Resolved Incidents
We're seeing intermittent failures in Rico chats - we're currently investigating the issue.
We've noticed a drop in the rate of incoming notifications from Google. This affects our ability to detect events such as renewals and cancellations in a timely manner, resulting in delays for some of these events.
New initial purchase events are not affected, since these are mostly ingested through SDK requests rather than server-to-server notifications.
We're investigating the issue, which currently appears to be on Google's side. We'll update this page as we learn more.
RevenueCat Outage Survival Guide
You're checking on RevenueCat - but is your own site converting?
Outages aren't the only thing that costs you visitors.
Get a visual audit that shows exactly where your site loses conversions.
Free, takes 2 minutes.
RevenueCat Components
RevenueCat API Uptime
RevenueCat App Store Receipt Servers
Apple Receipt Server
Google Play Store Receipt Server
Stripe Receipt Server
Apple Sandbox Receipt Server
Paddle Receipt Server
RevenueCat Dashboard
Overview
Charts
Collaborators
Customer Lists
Experiments
Login
Paywalls Editor
AI features
We're seeing intermittent failures in Rico chats - we're currently investigating the issue.
RevenueCat Scheduled Data Exports
RevenueCat Event Dispatching
We've noticed a drop in the rate of incoming notifications from Google. This affects our ability to detect events such as renewals and cancellations in a timely manner, resulting in delays for some of these events.
New initial purchase events are not affected, since these are mostly ingested through SDK requests rather than server-to-server notifications.
We're investigating the issue, which currently appears to be on Google's side. We'll update this page as we learn more.