Live data from Hacker News

DDoS attack on GitHub has stopped? Status is green again.

status.github.com

11–20 of 21 posts

Re: DDoS attack on GitHub has stopped? Status is green again.

#11

I think it's more they're no longer worried about it evolving any more.

They're still hiding behind Prolexic/Akamai. I suspect the attacker is waiting for them to drop that protection.

From a state sponsored attacker I would have expected to see a BGP attack..

Re: DDoS attack on GitHub has stopped? Status is green again.

#12

I think it's more they're no longer worried about it evolving any more.

They're still hiding behind Prolexic/Akamai. I suspect the attacker is waiting for them to drop that protection. From a state sponsored attacker I would have expected to see a BGP attack..

A BGP attack would be a whole new level of "This is war", probably with a bit more consequences.

Re: DDoS attack on GitHub has stopped? Status is green again.

#13
post #10

Earlier quoted context omitted.

Not by a long-shot; this was reported as a big deal (and I'd love to have more insight and data available), but this kind of thing has been going on for many years. Ask your local DNS admin for some war stories. :-)

It also gained notoriety because it seemed like an attempt by a Chinese actor (possibly the PRC) to force Github to take down two repositories that helped to circumvent the Great Firewall. Github itself has weathered DDoS attacks before, but I'm not sure how different this attack was in scale.

https://github.com/blog/1981-large-scale-ddos-attack-on-gith... explicitly states that "We are currently experiencing the largest DDoS (distributed denial of service) attack in github.com's history".

Re: DDoS attack on GitHub has stopped? Status is green again.

#16
post #15
post #5

https://github.com/greatfire and https://github.com/cn-nytimes have both returned to normal as well.

Yea I can't seem to get to those pages either. Update: its working now, but it was definitely not working earlier.

It's working from my end.

Re: DDoS attack on GitHub has stopped? Status is green again.

#17
I'm also unable to access the two repos that were apparently the target of the PRC's ire: https://github.com/cn-nytimes and https://github.com/greatfire

Is this simply a temporary precautionary measure because of the initial JS DDOS, or has GitHub permanently taken those two repos down?

If it's the latter, then I'm really disappointed and it would seem the PRC was able to get what it wanted.

Re: DDoS attack on GitHub has stopped? Status is green again.

#18
post #17

I'm also unable to access the two repos that were apparently the target of the PRC's ire: https://github.com/cn-nytimes and https://github.com/greatfire Is this simply a temporary precautionary measure because of the initial JS DDOS, or has GitHub permanently taken those two repos down? If it's the latter, then I'm really disappointed and it would seem the PRC was able to get what it wanted.

Both repos are still up and accessible from my end (India).

Re: DDoS attack on GitHub has stopped? Status is green again.

#19
post #17

I'm also unable to access the two repos that were apparently the target of the PRC's ire: https://github.com/cn-nytimes and https://github.com/greatfire Is this simply a temporary precautionary measure because of the initial JS DDOS, or has GitHub permanently taken those two repos down? If it's the latter, then I'm really disappointed and it would seem the PRC was able to get what it wanted.

They're there for me (I'm in the US-midwest.)

Re: DDoS attack on GitHub has stopped? Status is green again.

#20
post #17

I'm also unable to access the two repos that were apparently the target of the PRC's ire: https://github.com/cn-nytimes and https://github.com/greatfire Is this simply a temporary precautionary measure because of the initial JS DDOS, or has GitHub permanently taken those two repos down? If it's the latter, then I'm really disappointed and it would seem the PRC was able to get what it wanted.

Interestingly, GitHub seem's to be allowing logged-in users to access those pages, but using a incongnito tab shows unicorns. I'm guessing they've just disabled access for unauthenticated requests.
Post reply on HN