- Level
- confirmed
- Worst impact
- Degraded
- RevenueCat says
- 2025-09-26 07:30 to 10:30 UTC (3h)
- Components
- Event Dispatching
- Down Index
- 21of 100
What to do
Check whether you use RevenueCat Event Dispatching. Check your stack
Drop a package.json, lockfile, Terraform or a list of domains at down.guide to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 3h 23m it lasted.
Anything that failed between 2025-09-26 10:53 UTC and 2025-09-26 14:16 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 2
- identified
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.
provider
- resolved
We have caught up on receipts likely to have expirations or renewals and are performing other refreshes at a healthy pace now.
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-c774f222d5
Is RevenueCat still down?
No, this incident was resolved 2025-09-26 14:16 UTC. For RevenueCat's live state, see https://down.guide/providers/revenuecat.
How long did it last?
3h 23m, from 2025-09-26 10:53 UTC to 2025-09-26 14:16 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.