Forum Discussion
We believe the issue impacting Netflix should now be resolved. Please let us know if you continue to have issues.
Brian
Cox Support Forum Moderator
Hello Brian,
Thank you for the update. Unfortunately, as of tonight, I cannot say my issue is resolved. I spent some time starting/stopping several separate streaming sessions, then traced each corresponding Netflix IP addresses—all within the span of just a few minutes. Qualitatively, my observations were proportionate with the data seen below. I either experienced a flawless experience (immediate streaming at approximately max bitrate), or suffered an experience identical to what I described in my original post.
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 14ms 0/ 100 = 0% 0/ 100 = 0% ip68-4-11-98.oc.oc.cox.net [68.4.11.98]
0/ 100 = 0% |
5 18ms 0/ 100 = 0% 0/ 100 = 0% 68.1.1.61
0/ 100 = 0% |
6 16ms 0/ 100 = 0% 0/ 100 = 0% 23.246.24.10
0/ 100 = 0% |
7 16ms 0/ 100 = 0% 0/ 100 = 0% ipv4_1.cxl0.c046.lax008.ix.nflxvideo.net [23.246.24.175]
Test #2
1 0ms 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.6
0/ 100 = 0% |
4 15ms 0/ 100 = 0% 0/ 100 = 0% ip68-4-11-96.oc.oc.cox.net [68.4.11.96]
0/ 100 = 0% |
5 17ms 0/ 100 = 0% 0/ 100 = 0% 68.1.1.167
1/ 100 = 1% |
6 16ms 1/ 100 = 1% 0/ 100 = 0% 23.246.25.10
7/ 100 = 7% |
7 31ms 8/ 100 = 8% 0/ 100 = 0% ipv4_1.cxl0.c077.lax008.ix.nflxvideo.net [23.246.25.156]
For reference, a contemporaneous speed test, with the following results, was also performed.
- BrianM7 years agoModeratorThank you for the trace route, I am forwarding this to our network operations team to further review.
Brian
Cox Support Forum Moderator- chmod7777 years agoNew Contributor III
Brian, I am still having consistent issues during primetime as well. A test to fast.com just resulted in only 200 Kbps download while a speedtest within the Cox network is at the correct speed (120+ Mbps). It certainly seems like a peering issue. I am having issues with other sites besides just Netflix, even browsing popular sites like eBay/Craigslist are slow to load. I am in Aliso Viejo (92656).
Here is a traceroute to Netflix:
Tracing route to ipv4_1.cxl0.c095.lax008.ix.nflxvideo.net [23.246.25.174]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 9 ms 9 ms 7 ms 10.82.8.1
3 71 ms 9 ms 9 ms 100.120.104.160
4 8 ms 7 ms 8 ms 100.120.104.12
5 10 ms 9 ms 19 ms 68.1.1.167
6 126 ms 78 ms 22 ms 23.246.25.10
7 * 25 ms 26 ms ipv4_1.cxl0.c095.lax008.ix.nflxvideo.net [23.246.25.174]
Trace complete.And a traceroute to Craigslist, another site that loads very slowly during primetime, despite not being particularly bandwidth intensive, just waiting for images to load takes a while:
Tracing route to cities.g.craigslist.org [208.82.237.2]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 9 ms 7 ms 9 ms 10.82.8.1
3 13 ms 17 ms 8 ms 100.120.104.162
4 11 ms 10 ms 8 ms 100.120.104.14
5 13 ms 11 ms 11 ms 68.1.1.61
6 12 ms 11 ms 121 ms ae20.mpr1.lax12.us.zip.zayo.com [64.125.13.97]
7 76 ms 76 ms 75 ms ae14.cs2.lax112.us.eth.zayo.com [64.125.27.38]
8 178 ms 78 ms 130 ms ae3.cs2.dfw2.us.eth.zayo.com [64.125.29.20]
9 75 ms 75 ms 75 ms ae5.cs2.iah1.us.eth.zayo.com [64.125.28.102]
10 74 ms 101 ms 83 ms ae3.cs2.dca2.us.eth.zayo.com [64.125.29.44]
11 165 ms 130 ms 74 ms ae27.cr2.dca2.us.zip.zayo.com [64.125.30.249]
12 76 ms 77 ms 77 ms ae15.er5.iad10.us.zip.zayo.com [64.125.31.42]
13 86 ms 75 ms 124 ms 208.184.77.102.IPYX-082122-ZYO.zip.zayo.com [208.184.77.102]
14 110 ms 112 ms 81 ms cities.craigslist.org [208.82.237.2]I would appreciate any followup from the network ops team as well if possible.
Thank you in advance for your help and please let me know if there's any other info I can provide that may be of assistance in investigating the issue.
- simplegreen7 years agoNew Contributor II
I appreciate the ongoing investigation. In the meantime, I have another possibly useful trace route, along with a speed test via fast.com, both performed within minutes of each other:
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 20ms 0/ 100 = 0% 0/ 100 = 0% 68.1.1.63
1/ 100 = 1% |
6 16ms 1/ 100 = 1% 0/ 100 = 0% 23.246.25.10
20/ 100 = 20% |
7 31ms 21/ 100 = 21% 0/ 100 = 0% ipv4_1.cxl0.c095.lax008.ix.nflxvideo.net [23.246.25.174]Downstream: 400 Mbps
Latency—
Unloaded: 17 ms
Loaded: 33 ms
Upstream: 29 Mbps
Client: Carpinteria, US Cox
Server(s) Los Angeles, US - DavidA27 years agoFormer ModeratorThank you for providing the additional trace route. I will get this sent over to our network operations team.
David
Cox Support Forum Moderator
Related Content
- 9 months ago