[jbredeche]

Looks like github status is on heroku. It's loading fine for me:

  > host status.github.com
  status.github.com is an alias for appid129905herokucom-760859479.us-east-1.elb.amazonaws.com.
  appid129905herokucom-760859479.us-east-1.elb.amazonaws.com has address 50.19.101.240
  appid129905herokucom-760859479.us-east-1.elb.amazonaws.com has address 50.19.101.216
  appid129905herokucom-760859479.us-east-1.elb.amazonaws.com has address 107.22.241.165

[NelsonMinar]

Ah, my mistake. Some HN story linked to https://github.com/status which was down when I was posting the Twitter status.

[danhunter]

Yep after the last major outage they switched to Heroku

[bgentry]

They were already running their status site on Heroku prior to the last major service outage.

[adgar2]

This is correct. They needed ~90 dynos to keep up with about 500 qps on their status page in the last outage.

Source: http://news.ycombinator.net/item?id=4524489

[gojomo]

Should probably throw a Fastly or CloudFlare cache in front of a single dyno.

[adgar2]

That would suggest people in charge know what they're doing.