Live  /  RevenueCat  /  Incident

RevenueCat: Delays in Google purchase events

RevenueCat · revenuecat.comMinor incidentResolved2026-10-29 14:35 UTC
Public — what happened

Summary

RevenueCat said that starting at 11:59 UTC on 2026-10-29, fewer notifications than usual were arriving from Google, which delayed some events such as renewals and cancellations. It said first-time purchases were not affected because they mostly come in through a different route. By 12:36 UTC the company said it had confirmed the problem was with Google Play's server-to-server notifications and had reported it to Google. RevenueCat said notification volume returned to normal by 13:47 UTC, and the incident was marked resolved at 14:35 UTC.

Affected

Event Dispatching

As listed on RevenueCat’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach RevenueCat against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for RevenueCat: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the RevenueCat report →

More from RevenueCat

Covered in The Squid’s Ink, Week 45, 2026, our weekly internet health report.

The full archive is on the RevenueCat status & history page.

Related: RevenueCat status & history. SquidGrid is not affiliated with RevenueCat.