RevenueCat Outage History

44 incidents recorded over the last 365 days, 43 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live RevenueCat status100.00% uptime history

Every Recorded RevenueCat Incident

RevenueCat incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 29, 2026Intermittent issues in Rico chatsUnderlying issues have been resolved51 minResolved
Oct 29, 2026Delays in Google purchase eventsThis incident has been resolved.2h 35mResolved
Oct 21, 2026Apple partial outage for App Store Server API - SandboxThe incident has been resolved. Apple Sandbox App Store API is correctly processing requests.3h 21mResolved
Oct 15, 2026Routine Database MaintenanceMaintenance has concluded.1h 30mScheduled
Sep 16, 2026Drop in Google Play Store pub-sub notificationsThis incident has been resolved.1h 49mResolved
Sep 1, 2026Apple partial outage: intermittent errors while processing purchasesThe issue has been resolved. We’re now making sure that any purchases affected by the outage are reprocessed.26 minResolved
Aug 10, 2026Elevated error rates on RevenueCat APIsError rates and latency have returned back to normal.1h 22mResolved
Aug 7, 2026Webhook delivery is delayedWebhook delivery latency is still on normal levels and the system is stable. We consider the incident resolved.3h 7mResolved
Aug 6, 2026Rico is having issuesRico continues recovered and stable, we consider the incident resolved.1h 10mResolved
Aug 6, 2026App Store Connect undergoing maintenance by AppleApple has completed their maintenance.48h 49mResolved
Jul 27, 2026Newly created apps error with "The key is not valid or is not compatible with the Bundle ID of your app"The issue appears to have been resolved on Apple's side. We're seeing keys being correctly validated now.92h 15mResolved
Jul 26, 2026Problems connecting to Apple servicesAll the impacted purchases have been replayed.10h 44mResolved
Jul 16, 2026App Store Connect degraded performanceApp Store Connect issues are now resolved.7h 53mResolved
Jul 16, 2026Cannot connect new Stripe accounts without creating a Stripe Project through the CLIThe issue has been resolved by Stripe and it's now possible to install again the RevenueCat Stripe app through the Stripe Marketplace page.1h 34mResolved
Jul 16, 2026Some users unable to login via single-sign-on (SSO)This incident has been resolved.1h 34mResolved
Jul 7, 2026Delays in Play Store subscriptions renewalsThis incident has been resolved.2h 51mResolved
Jul 7, 2026Apple Store Kit 2 elevated error ratesThis incident has been resolved.3h 41mResolved
Jun 23, 2026App Store Connect outageApp Store Connect issues are now resolved.4h 19mResolved
Jun 22, 2026Paywall Charts: Conversions not being attributedThis incident has been resolved.20h 10mResolved
Jun 21, 2026Delays in receipt refresh processingThis incident has been resolved.2h 23mResolved
Jun 16, 2026Rico unavailableThis incident has been resolved.42 minResolved
Jun 12, 2026Automatic paywall translations unavailableThis incident has been resolved. Automatic translations in the Paywall editor are working again. Customers should now be able to generate new paywall translations from the dashboard as expected.1h 43mResolved
May 29, 2026Elevated Google Play API Error RateOur mitigations have eliminated the impact on RevenueCat clients. We will continue tracking the situation and following up with Google on a permanent fix.4h 9mResolved
May 25, 2026Increased error rate when fetching subscriber informationThis incident has been resolved.1h 31mResolved
May 12, 2026Delayed Charts v3 DataWe identified and resolved the issue. Charts v3 data is now up-to-date.3h 23mResolved
May 8, 2026Increased API error rates due to reduced service capacity.This incident has been resolved.12h 35mResolved
Apr 28, 2026Elevated error ratesAll systems are now operating normally. Event delivery has fully caught up, and performance has returned to expected levels.54 minResolved
Apr 22, 2026Increased rate-limit errors on API V2 endpointsThe incident has been resolved.33 minResolved
Apr 18, 2026Degradation of serviceThe 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…28 minResolved
Apr 17, 2026Degraded API PerformanceEarlier today, around 7:20 AM UTC, we had slightly elevated error rates on our API for about 5 minutes due to database maintenance. The RevenueCat SDK will handle this gracefully, but API users may have noticed a…-87 minResolved
Apr 10, 2026Scheduled Data Exports delayed for GCPThis incident has been resolved.2h 53mResolved
Mar 31, 2026ARR/MRR charts are incorrect for some usersThis incident has been resolved.5h 44mResolved
Mar 16, 2026Ongoing issue dispatching events to webhooks with certain integrationsThe issue has been resolved and all failed webhook events have been dispatched.1h 15mResolved
Mar 6, 2026Elevated Error Rates.From 6:10 to 6:25 UTC, we had slightly higher API error rates due to a database infrastructure issue. The incident has been resolved. App using the RevenueCat SDK were not impacted.0 minResolved
Feb 19, 2026Dashboard: Charts V3 Beta availability issuesCharts V3 Beta is now available again for all users. The underlying infrastructure issue has been resolved. Data processing jobs are still being re-enabled and any data gaps will be backfilled automatically.2h 35mResolved
Feb 10, 2026Increased error rate on our APIThis incident has been resolved.3h 50mResolved
Feb 9, 2026Experiments data delayedAll experiment pipeline jobs have finish successfully and the data is now up to date. We are sorry for the inconveniences this may have caused you.2h 50mResolved
Feb 9, 2026Delayed Webhook DeliveryFrom ~4:30 UTC to ~5:30 UTC webhook delivery time regressed to up to a few minutes delay (from the usual second or two). The underlying issue has been fixed and delivery time is back down to normal latency.-97 minResolved
Feb 5, 2026Delayed experiment resultsThe incident has resolved, and the experimental results are up to date.3h 59mResolved
Jan 27, 2026Charts data freshness indicators showing outdated timestampsThis incident has been resolved.18 minResolved
Jan 24, 2026Small sample of delayed or Inaccurate Data in Charts, Experiments, and Data Exports for ~.2% of developersThis incident has been resolved.14h 24mResolved
Jan 14, 2026Error spike in APIAll fortress receipts have been replayed.54 minResolved
Dec 11, 2025Delayed Data in Charts, Experiments, Data Exports and Customer ListsExperiment results are now also updated and all data is fully up to date. Some scheduled data exports contained missing data, but they will repopulate automatically during the next export cycle.8h 33mResolved
Nov 6, 2025Revenuecat Companion App push notification issuesPush notifications to the RevenueCat app are now being delivered in time. Notifications affected by the issue have also been delivered.1h 36mResolved

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next RevenueCat incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

How to Read This RevenueCat Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before RevenueCat acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single RevenueCat outage in this window ran 3d 20h, against a mean recovery of 6h 50m. If you depend on RevenueCat in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.