RevenueCat logo

Is RevenueCat Down?

SaaSLive status, outages, and incident history

No. RevenueCat is up right now.

Every monitored RevenueCat system is operational as of September 25, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked just nowLive · 60s while moving

Know the moment RevenueCat breaks

RevenueCat is healthy right now. We keep checking (every 60 seconds once it starts moving) and email you the moment that changes.

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

Official RevenueCat status page
How we know: the official RevenueCat status page, PulsAPI's own check (every 60 seconds while one is moving, every 5 to 20 minutes while it is stable), and outage reports from engineers. How PulsAPI monitoring works

RevenueCat Component Status

The main RevenueCat systems on this page. All 19 are operational right now.

19operational
API Uptime
Operational
App Store Connect API
Operational
App Store Receipt Servers » Apple Receipt Server
Operational

16 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking App Store Receipt Servers » Apple Sandbox Receipt Server, App Store Receipt Servers » Google Play Store Receipt Server, App Store Receipt Servers » Paddle Receipt Server, App Store Receipt Servers » Stripe Receipt Server, Dashboard » AI features, Dashboard » Charts, Dashboard » Collaborators, Dashboard » Customer Lists, Dashboard » Experiments, Dashboard » Login, Dashboard » Overview, Dashboard » Paywalls Editor, and 4 more.

See all of them free

Component statuses may change independently during partial outages.

Recent RevenueCat Outages & Incidents

Incident history from the official RevenueCat status page, including resolution updates.

Drop in Google Play Store pub-sub notificationsResolved Sep 16, 2026 · 1h 49mResolved

This incident has been resolved. --- [2026-09-16T16:17:16.870Z] (investigating) We’re observing a drop in the rate of Google Play Pub-Sub notifications, and most purchases are currently failing. You may also notice delays in event delivery. Google has acknowledged the issue and we’re monitoring the situation. --- [2026-09-16T15:55:04.641Z] (investigating) We’re observing a drop of the rate in Google Play pub-sub notifications. You may notice delay in the delivery of events. We are investigating.

Apple partial outage: intermittent errors while processing purchasesResolved Sep 1, 2026 · 26 minResolved

The issue has been resolved. We’re now making sure that any purchases affected by the outage are reprocessed. --- [2026-09-01T13:31:29.825Z] (monitoring) Apple has reported that the issue is now resolved, and we’re also seeing error rates return to normal. We’ll keep monitoring. --- [2026-09-01T13:17:00.110Z] (identified) We’re seeing an increased rate of errors when communicating with Apple’s backend services. This is resulting in some HTTP 522 responses from our receipts endpoint. We’ve enabled mitigations to minimize the impact on RevenueCat customers, and no purchases are currently being blocked as a result. We’ll continue monitoring the issue and update this thread.

Elevated error rates on RevenueCat APIsResolved Aug 10, 2026 · 1h 22mResolved

Error rates and latency have returned back to normal. --- [2026-08-10T18:56:13.120Z] (identified) We have rolled out a fix and are seeing early signs of improvement. --- [2026-08-10T18:37:43.142Z] (investigating) We are currently investigating elevated error rates and latency across multiple of our APIs

RevenueCat Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a RevenueCat incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history49 days observed
Aug 8100.00% average · 3 days with incidentsSep 25

Live RevenueCat Outage Reports

Problems reported by engineers using RevenueCat. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No RevenueCat problems reported yet.

Something wrong with RevenueCat on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About RevenueCat

RevenueCat publishes a public status page at status.revenuecat.com covering 21 components, including API Uptime, Apple Receipt Server and Overview. PulsAPI tracks RevenueCat outages, degraded performance and incident history in real time, alongside the rest of your SaaS stack.

Over the past 30 days, PulsAPI has measured RevenueCat uptime at 100.00%. Response times, incident history, and SLA tracking for RevenueCat are available on the PulsAPI dashboard.

RevenueCat Status FAQ

Is RevenueCat down right now?

The verdict at the top of this page comes from the latest poll of the official RevenueCat status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead.

What should I do if RevenueCat is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until RevenueCat recovers.

How do I check RevenueCat uptime history?

PulsAPI tracks RevenueCat uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 100.00%. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever RevenueCat changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect RevenueCat outages?

PulsAPI reads the official RevenueCat status page. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email within seconds of detection.

Does PulsAPI track individual RevenueCat components?

Yes. PulsAPI monitors 19 individual RevenueCat components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when RevenueCat goes down?

Yes. Create a free account and subscribe to RevenueCat: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with RevenueCat to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot RevenueCat problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor RevenueCat?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so RevenueCat plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track RevenueCat with the rest of your stack

2463+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services