- Level
- confirmed
- Worst impact
- Degraded
- Components
- Charts
- Down Index
- 16of 100
What to do
Check whether you use RevenueCat Charts. 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 18m it lasted.
Anything that failed between 2026-01-27 20:08 UTC and 2026-01-27 20:27 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
We identified an issue where Charts data freshness indicators are displaying outdated timestamps. The underlying chart data is being updated correctly, but the freshness timestamps shown in the UI are not reflecting the latest refresh times. A fix has been deployed and we are monitoring the rollout.
provider
- 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-566da6eba5
Is RevenueCat still down?
No, this incident was resolved 2026-01-27 20:27 UTC. For RevenueCat's live state, see https://down.guide/revenuecat.
How long did it last?
18m, from 2026-01-27 20:08 UTC to 2026-01-27 20:27 UTC, by the times RevenueCat posted.
What was affected?
RevenueCat named Charts.
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.