4 ms·
1) I don't think he meant that it was being served off of AWS, just that was his VPN example. Any in the US should do. 2) VPNs add latency and are still limit
by jimktrains2 13y ago
1) I don't think he meant that it was being served off of AWS, just that was his VPN example. Any in the US should do.
2) VPNs add latency and are still limited by the bandwidth of your connection. Given that Netflix has a decent CDN, in theory your VPN-box shouldn't have all that much better a path to a Netflix server than you do. So, assuming that the paths to netflix are mostly equal, a fast VPN-Netflix experience vs a crappy local connection one would imply the ISP is to blame (for whatever reason malicious or not).
- diminoten 13y agoThe whole point is that Netflix's CDNs aren't "decent". That is, they're probably "decent" (quite good, I'd even imagine), but the load is so high so as to cause traffic problems anyway. The question was "how can I tell if it's Netflix or if it's my ISP?" and the answer is, "You can't."
- Dylan16807 13y agoIf they're actually overloaded, as opposed to there being peering failures to the consumer ISPs, why would there be a difference between VPN and not-VPN?
- diminoten 13y agoTo answer both you and your sibling comment - there would be a difference in performance, depending on which CDN is delivered to you. I don't know of a way to request a specific CDN from Netflix, and if the one that's the closest to you is having perf issues, that doesn't mean the one closest to your VPN will have the same perf issues.
- jimktrains2 13y agoI was discussing paths to the CDN, not the performance of the CDN's servers themselves. If the servers are the bottleneck, and not the network, shouldn't performance be roughly the same (or worse over) the VPN verses the local connection?