Re:New phenomenon breaks inbound TCP policing
by colanderman on Monday June 06, 2016 @11:17PM
(#11852147)
I'm not convinced either way. Windows Update is the one opening the dozens of connections (it has to if it's behind a firewall), not Akamai; Akamai's just serving the data. But Windows Update is possibly just calling out to an Akamai library that opens the dozens of connections on its behalf.
If there are also congestion-algorithm shenanigans like the forum post suggests, then Akamai is definitely at fault. But the issue I see is that of connection hogging.
Re:New phenomenon breaks inbound TCP policing
by kev009 on Tuesday June 07, 2016 @06:27AM
(#11853519)
Even if it is isolated to the servers distributing MS's updates, I'm having trouble seeing how this could even be MS's fault-- it's the server side (owned and operated by Akamai) that's misbehaving here.