News for hackers. Stuff that matters.

A comment on Github: Major Service Outage. Parent comment

Re:Github: Major Service Outage by jbredeche on Thursday October 18, 2012 @04:40PM (#4670975)
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
[ Parent | on HN ]
Re:Github: Major Service Outage by NelsonMinar on Thursday October 18, 2012 @04:41PM (#4670988)
Ah, my mistake. Some HN story linked to https://github.com/status which was down when I was posting the Twitter status.
[ Parent | on HN ]
Re:Github: Major Service Outage by danhunter on Thursday October 18, 2012 @04:40PM (#4670979)
Yep after the last major outage they switched to Heroku
[ Parent | on HN ]
Re:Github: Major Service Outage by bgentry on Thursday October 18, 2012 @04:44PM (#4671010)
They were already running their status site on Heroku prior to the last major service outage.
[ Parent | on HN ]
Re:Github: Major Service Outage by adgar2 on Thursday October 18, 2012 @04:51PM (#4671040)
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

[ Parent | on HN ]
Re:Github: Major Service Outage by gojomo on Thursday October 18, 2012 @05:00PM (#4671089)
Should probably throw a Fastly or CloudFlare cache in front of a single dyno.
[ Parent | on HN ]
Re:Github: Major Service Outage by adgar2 on Thursday October 18, 2012 @11:59PM (#4672211)
That would suggest people in charge know what they're doing.
[ Parent | on HN ]