Investigating - We are observing elevated error rates from the Google Play API. This might prevent some user's entitlements from being granted after purchase. We're working on a mitigation to unlock these customers.
May 29, 2026 - 15:45 UTC
API Uptime
Operational
90 days ago
99.97
% uptime
Today
App Store Receipt Servers
Operational
90 days ago
100.0
% uptime
Today
Apple Receipt Server
Operational
Google Play Store Receipt Server
Operational
Stripe Receipt Server
Operational
Apple Sandbox Receipt Server
Operational
90 days ago
100.0
% uptime
Today
Paddle Receipt Server
Operational
90 days ago
100.0
% uptime
Today
Dashboard
Operational
90 days ago
100.0
% uptime
Today
Overview
Operational
90 days ago
100.0
% uptime
Today
Charts
Operational
90 days ago
100.0
% uptime
Today
Collaborators
Operational
90 days ago
100.0
% uptime
Today
Customer Lists
Operational
90 days ago
100.0
% uptime
Today
Experiments
Operational
90 days ago
100.0
% uptime
Today
Login
Operational
90 days ago
100.0
% uptime
Today
Paywalls Editor
Operational
90 days ago
100.0
% uptime
Today
Scheduled Data Exports
Operational
90 days ago
100.0
% uptime
Today
Event Dispatching
Operational
90 days ago
100.0
% uptime
Today
Documentation
Operational
90 days ago
100.0
% uptime
Today
App Store Connect API
Operational
90 days ago
100.0
% uptime
Today
RevenueCat Companion App
Operational
90 days ago
100.0
% uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Related
No incidents or maintenance related to this downtime.
Past Incidents
May 29, 2026
Unresolved incident: Elevated Google Play API Error Rate.
Resolved -
This incident has been resolved.
May 25, 17:29 UTC
Monitoring -
A fix has been implemented and error rate is going down. We'll keep monitoring.
May 25, 16:23 UTC
Identified -
We are experiencing an increased error rate when fetching subscriber information coming from an incorrect cache. We are currently working on a fix.
May 25, 15:57 UTC