4 ms·
Heroku should know better and not host their status page on their servers since it becomes unaccessible when most needed. This problem started last night and th
by edouard1234567 15y ago
Heroku should know better and not host their status page on their servers since it becomes unaccessible when most needed. This problem started last night and they detected it this morning, monitoring system FAIL.
- ohgodthecat 15y agoIt appears to be hosted on rackspace (right now at least). But it doesn't look automatic so perhaps the people were not available to update it til this morning.
- imbriaco 15y agoThe Heroku status site is indeed hosted outside of both the Heroku platform and EC2. It has been that way for at least a couple of years that I have direct knowledge of, and probably longer.
- edouard1234567 15y agoThe page wasn't available earlier so something from their stack is probably shared. Maybe the problem was is in how they route the traffic to this status page. Bottom line, this page should stay up and the only way to almost guaranty that is to make sure nothing is shared between heroku's infrastructure and where/how the status page is hosted/served.
- imbriaco 15y agoIt's entirely possible that the status site had an unrelated issue. It happens. That said, I ran their stack until 2 weeks ago, so I can speak authoritatively on this: Nothing from their stack is shared with the status site. Period.
- edouard1234567 15y agoIf that's the case (I trust your authority in this), then maybe the status page went down because of the spike in traffic.