RevenueCat: Degraded performace across dashboard and APIs
Heroku outage, Mar 16, 2020 · 8 vendors, 9 incidents
RevenueCat’s incident blames Heroku as the cause. (hop 1, posted +3 h 40 min vs the first vendor naming Heroku)
“…Degraded performace across dashboard and APIs Heroku has moved this issue to resolved, so we are too. They don't seem to have a root cause ye but we don't believe there is anything to do on our end. W…”
Swipe sideways to see the whole diagram.
Mermaid source
flowchart LR
root["Heroku<br/>own incident not archived"]:::inferred
h1["Within an hour<br/>4 vendors, 4 blamed Heroku<br/>RevenueCat, Substack, Bitrise, crates.io"]:::blames
root --> h1
h4["1 to 4 hours later<br/>1 vendor, 1 blamed Heroku<br/>RevenueCat"]:::blames
root --> h4
me["RevenueCat (this incident)<br/>posted +3 h 40 min"]:::me
h4 --- meFull event: timeline, evidence and all vendors →
Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.
Timeline of updates
- resolved
Heroku has moved this issue to resolved, so we are too. They don't seem to have a root cause ye but we don't believe there is anything to do on our end. We haven't seen any degradations since yesterday and things appear to be back to normal.
From RevenueCat’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Impact, status and times are the vendor’s own, as last archived. View on status.revenuecat.com (opens in new tab).