Skip to main content
RevenueCat

Delays in Google purchase events

Degraded Lasted 2h 36m · started · RevenueCat's page

Level
confirmed
Worst impact
Degraded
Components
Event Dispatching
Down Index
21of 100

What to do

  • Check whether you use RevenueCat Event Dispatching. 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 2h 36m it lasted.

    Anything that failed between 2026-10-29 11:59 UTC and 2026-10-29 14:35 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 4

  1. investigating

    We've noticed a drop in the rate of incoming notifications from Google. This affects our ability to detect events such as renewals and cancellations in a timely manner, resulting in delays for some of these events. New initial purchase events are not affected, since these are mostly ingested through SDK requests rather than server-to-server notifications. We're investigating the issue, which currently appears to be on Google's side. We'll update this page as we learn more.

    provider

  2. identified

    We've confirmed that the issue is caused by a problem with Google Play's server-to-server notifications. We've reported the issue to Google and are continuing to monitor the situation.

    provider

  3. monitoring

    The rate of incoming Google notifications has returned to normal, and Google events should now be delivered on time. We'll continue monitoring the situation before resolving the incident.

    provider

  4. resolved

    This incident has been resolved.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

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

Questions about DWN-f3680a0677

Is RevenueCat still down?

No, this incident was resolved 2026-10-29 14:35 UTC. For RevenueCat's live state, see https://down.guide/revenuecat.

How long did it last?

2h 36m, from 2026-10-29 11:59 UTC to 2026-10-29 14:35 UTC, by the times RevenueCat posted.

What was affected?

RevenueCat named Event Dispatching.

What caused it?

RevenueCat hasn't published a root cause. If it does, it shows here.

Where does this come from?

RevenueCat's official status page, https://status.revenuecat.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.