3 ms·
I think it's pretty common practice to host your status site separately from your site so that connectivity issues at your datacenter don't bring your status si
by jackowayed 16y ago
I think it's pretty common practice to host your status site separately from your site so that connectivity issues at your datacenter don't bring your status site down as well.
Engine Yard has a Wordpress.com blog (and they don't even have it as a subdomain of engineyard.com. I guess in case their DNS goes down). Not only does GitHub use twitter, but they also have status.github.com hosted on EC2. Heroku has a status site on Slicehost.
It just makes sense. Connectivity is a pretty common reason for downtime. Why would you want a point of failure that can bring down your site and your status site?
- jacobian 16y ago> Not only does GitHub use twitter, but they also have status.github.com hosted on EC2. Heroku has a status site on Slicehost. Heh, that's a bit funny: Github's hosted on Rackspace Cloud. They have a status page which is hosted on EC2 via Heroku. Heroku hosts a status page on Slicehost. Slicehost is... wait for it... run by Rackspace out of the same data center as Rackspace Cloud.