3 ms·
Cloud giants sound alarm on record-breaking DDoS attacks
- uticus 3y agoFrom Oct 10
- throwaway290 3y agoSurely there is some pattern for these attacks? Where are they coming from?
- colpabar 3y ago[flagged]
- 2OEH8eoCRo0 3y agoI'd like to know this as well. Where are they coming from and who is being targeted?
- anvil-on-my-toe 3y ago> Google...peaked at 398 million requests per second...surpassing the 2022 record of 46 million requests per second.
- sva_ 3y agoMaybe they shouldn't report those numbers because at this point it seems like a dick measurement contest among botnet owners.
- Lyrex 3y agoI think even if it was then it's likely better to have the attackers show their hands by attacking (comparatively) irrelevant targets. I would assume that there are insights to be gained to even more effectively mitigate potential future attacks by this.
- JohnMakin 3y agoCloudflare has already mitigated this, and according to them, it affected less than 1% of their customers' traffic: https://blog.cloudflare.com/technical-breakdown-http2-rapid-reset-ddos-attack/ https://blog.cloudflare.com/technical-breakdown-http2-rapid-...
- HumblyTossed 3y agoSo, how much does this, if at all, slow overall internet traffic. I am talking in terms of just bits getting from one place to another over the tubes and not, I can't get to google because it's dealing with 400M rps.
- supertrope 3y agohttps://arstechnica.com/information-technology/2013/04/can-a-ddos-break-the-internet-sure-just-not-all-of-it/ https://arstechnica.com/information-technology/2013/04/can-a...
- amluto 3y agoI find it surprising that so many CDNs were vulnerable. They are literally services that operate open front ends that accept unauthenticated requests and issue (expensive) backend requests based on the front end requests. Wouldn’t counting the number of requests issued and the number in flight per outside IP, network, etc be a basic part of the process? Sure, HTTP 1.1 makes it extremely awkward to have lots of backend requests in flight per front end connection. But HTTP 2.0 makes a factor of 100 variation in the backend / frontend ratio trivial, and that’s a big number already. Calling this critical vulnerability in the protocol seems like an odd way to phrase what I see as an accounting failure in the overall system that apparently affected everyone. If I were implementing such a system, I wouldn’t have wanted to ignore the difference between an HTTP 1.0/1.1 connection with a single backend request and a 2.0 connection with 100, and catching the case where a 2.0 connection had 100 live backend requests and a couple thousand more orphaned requests seems like a natural result of accounting the requests correctly in the first place.
- notfish 3y agoWhy does this title read like the hook to a dnd session