I think it's probably my fault. Github seems to go down every time I start poking around in someone else's projects.
Github: Major Service Outage
31–40 of 80 posts
Re: Github: Major Service Outage
#32Earlier quoted context omitted.
They were already running their status site on Heroku prior to the last major service outage.
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
Re: Github: Major Service Outage
#33It would limit the potential damage these attacks could cause, given the reliance dev teams have on pushing code to a central repo. Taking down a site like Github has a fairly clear effect on the productivity of a lot of their users.
Re: Github: Major Service Outage
#34Secondly, I kind of like when big sites go down when I'm not in desperate need because it means a really nice aftermath write up is on the way. Can't wait to hear more about this one.
Re: Github: Major Service Outage
#35Re: Github: Major Service Outage
#36They said they're under a DDoS attack https://twitter.com/github/statuses/259029493669310464
Re: Github: Major Service Outage
#37Re: Github: Major Service Outage
#38Re: Github: Major Service Outage
#39Re: Github: Major Service Outage
#40Nothing against Github but this probably highlights the real benefit of DVCS: setting up multiple remotes for your repo. Manage it probably and when one service goes down, fall back to Bitbucket or another service. It would limit the potential damage these attacks could cause, given the reliance dev teams have on pushing code to a central repo. Taking down a site like Github has a fairly clear effect on the productiv…