Santa Barbara, CA - Significant packet loss in route to Netflix
Over the last couple months, Netflix streaming has been a mediocre experience, at best, despite an otherwise consistently stellar internet connection (averaging 300–340 mbps downstream & 30 mbps upst...
Tonight, I ran a few more packet loss tests using a destination of fast.com, and they were very consistent with the previous night's.
However, I decided to attempt a different, perhaps more valid approach, and installed Wireshark to assist with identifying the specific Netflix destination IP involved with my particular streaming session—in this case, the destination IP was 220.127.116.11. So I then tested that IP for packet loss. Here are some of those results, which, if I interpret them correctly, seem to suggest or confirm that the issue is internal to Netflix.
A couple more tests, both from tonight, and performed back to back. Depending on which server I was connected to, the results were drastically different from one another. The same IP that previously exhibited packet loss (18.104.22.168) reappeared tonight, this time with absolutely horrendous performance.