RevenueCat Status
System status
View historical uptime →Incident overview
Total incidents
14
Active now
0
Resolved
14
Avg. resolution
12h 44m
Recent incidents
View all →Drop in Google Play Store pub-sub notifications
Apple partial outage: intermittent errors while processing purchases
Elevated error rates on RevenueCat APIs
Webhook delivery is delayed
Rico is having issues
App Store Connect undergoing maintenance by Apple
Newly created apps error with "The key is not valid or is not compatible with the Bundle ID of your app"
Problems connecting to Apple services
Apple Store Kit 2 elevated error rates
App Store Connect degraded performance
Frequently asked questions
Is RevenueCat down right now?
RevenueCat is currently operational. DevHelm monitors RevenueCat's official status page continuously and updates this page every 5 minutes.
What is RevenueCat's current uptime?
RevenueCat has a measured 30-day uptime of 100.00%. Over the last 24 hours, uptime is 100.00%, and over 7 days it is 100.00%. These figures are computed from RevenueCat's official status page data.
How many incidents has RevenueCat had recently?
RevenueCat has experienced 14 incidents in the recent monitoring window. Resolved incidents were fixed in an average of 12h 44m. All incidents are currently resolved.
What components does RevenueCat monitor?
DevHelm tracks 19 individual components for RevenueCat, including Overview, Apple Receipt Server, API Uptime, Google Play Store Receipt Server, Charts, and 14 more. Each component has its own status and 90-day uptime history shown above.
How can I get notified about RevenueCat outages?
You can subscribe to RevenueCat's incident feed via Atom/RSS at devhelm.io/status/revenuecat/feed.xml for use in any feed reader. For real-time alerts via Slack, email, PagerDuty, or webhooks, add RevenueCat as a dependency in your DevHelm workspace.
About RevenueCat status monitoring
This page provides real-time operational status for RevenueCat, powered by DevHelm's continuous monitoring infrastructure. We track RevenueCat's official status page and aggregate component-level data into uptime percentages, incident timelines, and historical trends.
RevenueCat status data is refreshed every 5 minutes. We currently track 19 individual components, each with its own operational status and 90-day uptime history.
Uptime percentages represent the proportion of time all monitored components reported operational status. Incident data comes from vendor-published incident timelines and includes status updates, affected components, and resolution times.
Track RevenueCat in your stack
Get alerted when RevenueCat has issues — before your users notice. Set up in 30 seconds.