* You could have gotten a lousy route due to poor traffic management or a network issue by your ISP, the transit providers, or a CDN
* You could have been given an overloaded server or POP by a CDN's DNS
* Your ISP could have a netflix or third party caching appliance, and it could be overloaded
* Your ISP could be under-backhauled, under-peered, or under-transited in any points along your route
* Your ISP's transit provider(s) could be under-peered, under-backhauled, or under-transited if they are not a tier-1 network. See also poor traffic management and network issues.
* Any party along the way to the CDN and to the origin could be under-peered, under-backhauled, or under-transited. See also poor traffic management and network issues.
Using a VPN proves very little. Various BGP and DNS tricks are used in the bullets above, and a VPN can drastically change the parameters of all of them.
sure, all of that is possible. but honestly how likely is it that some or all of those things are the case on the direct path from netflix/youtube through the ISP in question to so many people's homes? and yet the problem spot is mysteriously avoided when using a VPN (not any particular VPN, but pretty much any of them, judging by most of the people who have spoken out about this problem recently). the problem so effectively avoided by changing the route from the optimal(ish) path to one that is almost guaranteed to be worse from a network flow standpoint.
sorry, I don't buy any apologizing for comcast/verizon failing to deliver HD video from netflix/youtube yet somehow able to do it under the same network conditions (same time) just this time through an encrypted VPN. if it was an isolated report... maybe. this is far too widespread to be anything but intentional.
Well, under-provisioned backhaul, peering, and/or transit would cause exactly this. And the blame trail could be quite complex. I'm not apologizing, but commentary by almost anyone other than the network architects and peering coordinators of these organizations are pretty baseless speculations.
Disclaimer: I work for a major CDN. Netflix is trying to ween off of us and our competitors, which has contributed to lesser experience. Their model of co-locating gear for free doesn't make much sense to ISPs in the grand scheme of things.
* You could have gotten a lousy route due to poor traffic management or a network issue by your ISP, the transit providers, or a CDN
* You could have been given an overloaded server or POP by a CDN's DNS
* Your ISP could have a netflix or third party caching appliance, and it could be overloaded
* Your ISP could be under-backhauled, under-peered, or under-transited in any points along your route
* Your ISP's transit provider(s) could be under-peered, under-backhauled, or under-transited if they are not a tier-1 network. See also poor traffic management and network issues.
* Any party along the way to the CDN and to the origin could be under-peered, under-backhauled, or under-transited. See also poor traffic management and network issues.
Using a VPN proves very little. Various BGP and DNS tricks are used in the bullets above, and a VPN can drastically change the parameters of all of them.