Live data from Hacker News

Github: Major Service Outage

status.github.com

41–50 of 80 posts

Re: Github: Major Service Outage

#43
post #36

They said they're under a DDoS attack https://twitter.com/github/statuses/259029493669310464

Who DDOS'es twitter? Mercurial committers? the Bitbucket people?

I heard once about a tire shop that drummed up business by strewing nails along the highway around it. Somewhere outside America; India or Thailand or somewhere else. Anyway, that kind of business practice wouldn't get you far in the Western world, so it seems unlikely.

OTOH, if I had a botnet and I wanted to see how powerfully it could DDOS without drawing a lot of mainstream media attention, github might be good for target practice. They have better infrastructure than most, and they always do detailed write-ups afterwards.

Re: Github: Major Service Outage

#49

Nothing 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…

It'd be glorious if one service (say GitHub) had multiple remote links that dynamically switched for you when service faced an outage.

If it's one service though there is still always a single point of failure outside of your control. If you want true redundancy you need to use multiple versions with no interconnections and develop your own solution to mitigate partial failure, of course your own solution is also a single point of failure, but at least it's under your control.

That said, Github has never been down long enough for me to justify a fallback procedure and policy for my team. The complexity of the solution outweighs the benefit. We'll cross that bridge when we come to it.

Post reply on HN