New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
cloudflare getting 400 gbps DDOs
support123
Member
Is that the reason LET was down few hours ago that cloudflare was getting DDOS ?
Comments
LET seemed down for me too. If they did receive a 400Gbps DDoS, I don't know if they did, but yeah, a 400Gbps attack could impact other CloudFlare customers, ie if the attack was not targeted at LET.
http://blog.cloudflare.com/technical-details-behind-a-400gbps-ntp-amplification-ddos-attack
It seemed to be on monday Hope no any new ddos crossing 500 gbps this time
Why someone will target LET with 400Gbps, what is to be earned from this stupid attack?
i remember years ago when we had like 10/20MB maximum internet connection and now the attacks are 400Gbps, i don't whant to know what will be in 5-10 years from now, ddos attacks with 100000Gbps
LET was obviously not the target.They not disclosing the attacked site info due to privacy reasons
If every host could check all IP ranges they use for detected open resolvers that would be a good start: http://openntpproject.org/
I had one as it happens on a server I use myself, sometimes you just miss little things like that.
Looks nice little handy tool @AnthonySmith
Wonder what is the reason behind this.
Could be Spamhaus
Oh wait, just checked they haven't been down for more than a week
https://www.cloudflare.com/system-status
on 10 and 11 performance degradation many locations
I actually meant the uptime of Spamhaus.
Not sure if they were targeted this time
We've seen a few network drops in our Italy and NYC locations. Caused my this attack.
I read in another thread that LET was down due to some HAProxy error.@jbiloh
Cluster error .. uhhm.please upload lots of images
The outage this morning was an HAProxy issue which has been resolved. We don't expect further issues.