Elevated Google Play API Error Rate

What to do

• Check whether you use RevenueCat Google Play Store Receipt Server. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 4h 9m it lasted.

  Anything that failed between 2026-05-29 15:45 UTC and 2026-05-29 19:55 UTC may need a replay.

• Subscribe to RevenueCat's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=revenuecat works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from RevenueCat 3

1. investigatingMay 29, 2026, 3:45 PM UTC

   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.

   provider

2. monitoringMay 29, 2026, 7:38 PM UTC

   Google Play API started returning some new, undocumented error responses for a subset of subscriptions over the last few hours. Our investigation revealed that the vast majority of them are associated with purchases that expired a long time ago. This means that no new purchases are being blocked, but API requests were still impacted by these unexpected errors. We have implemented suppression for these errors when we can programmatically confirm that they refer to long-expired purchases. This has reduced the errors returned by the RevenueCat receipts endpoint by almost 100%, so the issue is now mitigated. We have informed Google about these new unexpected errors and expect them to work on a permanent fix.

   provider

3. resolvedMay 29, 2026, 7:55 PM UTC

   Our mitigations have eliminated the impact on RevenueCat clients. We will continue tracking the situation and following up with Google on a permanent fix.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.