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 23.246.25.150. 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.
Test #1
1 0ms 0/ 100 = 0% 0/ 100 = 0% router.asus.com [192.168.1.1]
0/ 100 = 0% |
2 10ms 0/ 100 = 0% 0/ 100 = 0% 10.6.16.1
0/ 100 = 0% |
3 10ms 0/ 100 = 0% 0/ 100 = 0% 68.4.15.10
0/ 100 = 0% |
4 28ms 0/ 100 = 0% 0/ 100 = 0% ip68-4-11-98.oc.oc.cox.net [68.4.11.98]
0/ 100 = 0% |
5 24ms 0/ 100 = 0% 0/ 100 = 0% 68.1.1.63
1/ 100 = 1% |
6 31ms 1/ 100 = 1% 0/ 100 = 0% 23.246.25.10
5/ 100 = 5% |
7 31ms 6/ 100 = 6% 0/ 100 = 0% ipv4_1.cxl0.c071.lax008.ix.nflxvideo.net [23.246.25.150]
Test #2
1 1ms 0/ 100 = 0% 0/ 100 = 0% router.asus.com [192.168.1.1]
0/ 100 = 0% |
2 9ms 0/ 100 = 0% 0/ 100 = 0% 10.6.16.1
0/ 100 = 0% |
3 10ms 0/ 100 = 0% 0/ 100 = 0% 68.4.15.10
0/ 100 = 0% |
4 28ms 0/ 100 = 0% 0/ 100 = 0% ip68-4-11-98.oc.oc.cox.net [68.4.11.98]
0/ 100 = 0% |
5 24ms 0/ 100 = 0% 0/ 100 = 0% 68.1.1.63
3/ 100 = 3% |
6 29ms 3/ 100 = 3% 0/ 100 = 0% 23.246.25.10
0/ 100 = 0% |
7 29ms 3/ 100 = 3% 0/ 100 = 0% ipv4_1.cxl0.c071.lax008.ix.nflxvideo.net [23.246.25.150]
Test #3
1 1ms 0/ 100 = 0% 0/ 100 = 0% router.asus.com [192.168.1.1]
0/ 100 = 0% |
2 9ms 0/ 100 = 0% 0/ 100 = 0% 10.6.16.1
0/ 100 = 0% |
3 10ms 0/ 100 = 0% 0/ 100 = 0% 68.4.15.10
0/ 100 = 0% |
4 28ms 0/ 100 = 0% 0/ 100 = 0% ip68-4-11-98.oc.oc.cox.net [68.4.11.98]
0/ 100 = 0% |
5 25ms 0/ 100 = 0% 0/ 100 = 0% 68.1.1.63
2/ 100 = 2% |
6 28ms 2/ 100 = 2% 0/ 100 = 0% 23.246.25.10
2/ 100 = 2% |
7 28ms 4/ 100 = 4% 0/ 100 = 0% ipv4_1.cxl0.c071.lax008.ix.nflxvideo.net [23.246.25.150]
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 (23.246.25.150) reappeared tonight, this time with absolutely horrendous performance.
Test #1
1 0ms 0/ 100 = 0% 0/ 100 = 0% router.asus.com [192.168.1.1]
0/ 100 = 0% |
2 10ms 0/ 100 = 0% 0/ 100 = 0% 10.6.16.1
0/ 100 = 0% |
3 11ms 0/ 100 = 0% 0/ 100 = 0% 68.4.15.10
0/ 100 = 0% |
4 15ms 0/ 100 = 0% 0/ 100 = 0% ip68-4-11-98.oc.oc.cox.net [68.4.11.98]
0/ 100 = 0% |
5 28ms 0/ 100 = 0% 0/ 100 = 0% 68.1.1.63
15/ 100 = 15% |
6 32ms 20/ 100 = 20% 5/ 100 = 5% 23.246.25.10
0/ 100 = 0% |
7 32ms 15/ 100 = 15% 0/ 100 = 0% ipv4_1.cxl0.c071.lax008.ix.nflxvideo.net [23.246.25.150]
Test #2
1 0ms 0/ 100 = 0% 0/ 100 = 0% router.asus.com [192.168.1.1]
0/ 100 = 0% |
2 12ms 0/ 100 = 0% 0/ 100 = 0% 10.6.16.1
0/ 100 = 0% |
3 12ms 0/ 100 = 0% 0/ 100 = 0% 68.4.15.6
0/ 100 = 0% |
4 16ms 0/ 100 = 0% 0/ 100 = 0% ip68-4-11-96.oc.oc.cox.net [68.4.11.96]
0/ 100 = 0% |
5 19ms 0/ 100 = 0% 0/ 100 = 0% 68.1.1.171
0/ 100 = 0% |
6 19ms 0/ 100 = 0% 0/ 100 = 0% xe-5-0-0.edge2.LosAngeles9.Level3.net [4.53.230.81]
0/ 100 = 0% |
7 19ms 0/ 100 = 0% 0/ 100 = 0% ae-2-3614.ear4.LosAngeles1.Level3.net [4.69.211.214]
0/ 100 = 0% |
8 --- 100/ 100 =100% 100/ 100 =100% Netflix-level3-100G.LosAngeles1.Level3.net [4.68.73.26]
0/ 100 = 0% |
9 21ms 0/ 100 = 0% 0/ 100 = 0% ipv4_1.lagg0.c010.lax004.ix.nflxvideo.net [198.38.96.139]
