RevenueCat incident: Delayed integration event dispatching

Affected components

• Event Dispatching

1. resolvedSep 26, 2025, 14:16 UTC

   We have caught up on receipts likely to have expirations or renewals and are performing other refreshes at a healthy pace now.

2. identifiedSep 26, 2025, 10:53 UTC

   From 7:30 UTC to 10:30 UTC event dispatching was delayed for expiration, transfer, cancellation and renewal events due to an infrastructure issue. For apps with server-to-server notifications enabled, there shouldn't have been a noticeable delay. For apps without server-to-server notifications, we are catching up on delayed events.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in RevenueCat's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• Vimeo: Degraded Video Analytics data freshnessMinor · Sep 22, 2025, 13:38 UTC

How often does RevenueCat have incidents?

RevenueCat reported 6 incidents in the last 90 days, 3 of them major or critical. A typical incident lasted 1h 36m. See RevenueCat's uptime and incident history