Good plan. When a site is DDoSed, encourage thousands of HN viewers to check it out :P
Going to go out on a limb here and say that status.github.com is probably hosted somewhere other than github.com
GitHub is getting DDoSed again
51–60 of 75 posts
Re: GitHub is getting DDoSed again
#52Re: GitHub is getting DDoSed again
#53Earlier quoted context omitted.
I often have to wonder if the DDoS gods roll a dice and pick someone to screw each day. We have had many DDoS attacks and never once had any indication as to why. A few days ago we had a 30 Gbit DDoS. Our server host just blackholed any IP that was touched by it. They kept moving it around to target different bits of our infrastructure (unlike previous attacks that just targeted our website). We lost 6 servers, but t…
If your nickname here can somehow be linked to the company you're working for ( e.g. by checking previous messages you posted to HN or on another board) I think it's not very smart to write what you just wrote. Now the bad guys knows that they should just have tried a bit longer. Now maybe that because you were DROP'ing / blacklisting IPs maybe they just ran out of zombies but still... If I was the attacker and read…
They know that anyway. The longer and more severe an attack is, the more damage it's likely to do. A host may be able to sustain 30Gbps for a minute or two, but not for 5 minutes. If 5 out of 10 servers are being attacked, you can probably handle traffic at 50% capacity for a while, but not forever.
Re: GitHub is getting DDoSed again
#54Still not working, trying to load the page of a private repo, keeps loading and loading.
Re: GitHub is getting DDoSed again
#55It may be time for GitHub to build out multiple availability data centers and use BGP as an anycast tool. We do this. I have public facing IPv4 space that is announced from multiple facilities. Having an IP address hosted from multiple facilities is a powerful tool. This allows providers to hit our datacenter through the least amount of ASN routes. We original did this to minimize latency and create faster regional transaction processing. As an added benefit - DDoS traffic also gets routed to the nearest facility "load balancing" a DDoS so that it only affects a single facility or it splits up the 10gbps of traffic among many facilities if it is coming from many sources. O'Reilly's BGP book has a great chapter on "Anycast."
From the sounds of it their architecture may not support this. If they had a SAN solution capable of replication to multiple data centers like HP LeftHand's product or a multiple master DRBD configuration they may be able to host github from multiple active datacenters and announce the block equally so that providers route traffic to them because their ASN is closest.
Who knows, maybe they do all of this?
Re: GitHub is getting DDoSed again
#56Reading status.github.com over the last few weeks, I found it interesting how often little things were broken at Github. It's like every few days, a small part of the site is unavailable or the sysadmins are investigating this or that connectivity issue. I guess when you're as big as Github, keeping your site live and operational is completely nontrivial.
Re: GitHub is getting DDoSed again
#57Earlier quoted context omitted.
> "I'm seeing "the chinese" & "hacking" used too much together without proof more often than not." Get used to it, you're going to be seeing it for what is likely a few decades at least. We need an enemy. The Chinese are the new Red Army; something to blame Western problems on.
> something to blame Western problems on. That sounds really ignorant. DDoS is not a situation of east versus west.
Well, it kind of is a lot of the time, just not in the way the other commenter was thinking. The majority of DDoS traffic I have seen is from Russian, Turkish, Ukraine and Chinese IP address spaces. Basically I think a lot of 'eastern' countries have a lot of people on the internet but not a lot of security. I imagine high rates of pirated windows (and thus lesser counts of security updates) contributes in some of the places.
Re: GitHub is getting DDoSed again
#58Reading status.github.com over the last few weeks, I found it interesting how often little things were broken at Github. It's like every few days, a small part of the site is unavailable or the sysadmins are investigating this or that connectivity issue. I guess when you're as big as Github, keeping your site live and operational is completely nontrivial.
I'm sure other services have similar downtimes and issues, but they just don't give you visibility into their operation. Most companies won't let you know there is a problem unless you figure it out.
Re: GitHub is getting DDoSed again
#59This happened back in October a couple of days in a row. Who the heck is targeting Github and why? I wonder if these attacks are related to the Chinese hacking attacks that have been publicised lately?
Any service hosting 3rd party content on even a moderate scale (say a few hundred various users) is likely to get DDoS-ed and never find out exactly why.
I had a single IP on a customers 10M-bit fiber line get DDoSed for what seemed like no apparent reason. We had the ISP blackhole just that IP and the issue went away, but it was a real WTF on why it happened, and no it wasn't some ones accidental DNS mistake.
Re: GitHub is getting DDoSed again
#60There are people who suggest that a DDoS is just a 'digital sit in', a legitimate way for someone to air a grievance, if they think the targets (or world) haven't paid them enough attention.
This view makes DDoS seem more normal or even romantic/heroic, and spreads the tools/know-how more widely. So, pulling off a DDoS becomes a more plausible and attractive aspiration, for a larger set of surly people with marginal reasoning skills and destructive impulses.
The DDoS tactic should be rejected as dishonorable censorship and vandalism, no matter the cause under which it is launched.