Statuspage: Metastatuspage
Heroku outage, Mar 16, 2020 · 8 vendors, 9 incidents
Statuspage’s incident started in the same window without naming Heroku (timing only, not evidence of a link). (timing only, posted −24 min vs the first vendor naming Heroku)
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["Statuspage (this incident)<br/>posted −24 min"]:::me
root -.->|"same window"| 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
From approximately 9:15 AM - 9:30 AM PDT, Metastatuspage was down due to routing issues on our hosting service. There was a reoccurrence of the issue from 12:45 PM - 1:00 PM PDT. Service has since resumed.
From Statuspage’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 metastatuspage.com (opens in new tab).