- Level
- confirmed
- Worst impact
- Partial outage
- Components
- API Uptime
- Down Index
- 28of 100
What to do
Check whether you use RevenueCat API Uptime. 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 54m it lasted.
Anything that failed between 2026-01-14 11:00 UTC and 2026-01-14 11:54 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
- investigating
We have detected a spike in errors related to our database and have enabled Fortress to mitigate while we investigate.
provider
- monitoring
We have disabled fortress and the error rate is back to normal. We will be monitoring the systems.
provider
- resolved
All fortress receipts have been replayed.
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-bd493eb4e7
Is RevenueCat still down?
No, this incident was resolved 2026-01-14 11:54 UTC. For RevenueCat's live state, see https://down.guide/revenuecat.
How long did it last?
54m, from 2026-01-14 11:00 UTC to 2026-01-14 11:54 UTC, by the times RevenueCat posted.
What was affected?
RevenueCat named API Uptime.
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.