| [NV] Packet routing issue Just had Cox HSI based out of Las Vegas installed a month ago and service has been acceptable. I use it for general browsing, gaming and streaming media. I've been noticing a higher latency than I would consider normal for certain west coast gaming servers I connect to.
Tracing route to jennyfur.pelican.org [76.74.236.91]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms cmxp.lv.cox.net [192.168.2.1]
2 8 ms 9 ms 8 ms 10.80.0.1
3 9 ms 11 ms 7 ms 24-234-16-221.ptp.lvcm.net [24.234.16.221]
4 13 ms 10 ms 10 ms 24-234-6-125.ptp.lvcm.net [24.234.6.125]
5 15 ms 8 ms 12 ms 24-234-6-254.ptp.lvcm.net [24.234.6.254]
6 * 39 ms 44 ms 68.1.5.140
7 40 ms 45 ms 40 ms 10ge.ten1-3.dal-eqx-cor-1.peer1.net [206.223.118.30]
8 55 ms 54 ms 61 ms 10ge.ten1-2.la-600w-cor-2.peer1.net [216.187.124.121]
9 55 ms 61 ms 55 ms 10ge.xe-0-3-0.lax-600w-sbcor-2.peer1.net [216.187.88.46]
10 73 ms 48 ms 53 ms 10ge.xe-0-0-2.lax-600w-sbdis-1.peer1.net [216.187.88.138]
11 54 ms 47 ms 48 ms jennyfur.pelican.org [76.74.236.91]
Trace complete.
Mind you, that server is located in Los Angeles, CA. I'm in Las Vegas, NV. My packets seem to be going from NV to AZ to TX and THEN to CA. Seems a little too roundabout.
Here's a link to someone with the same issue:
»Re: [CA] COX HSI - High Latency - Bad routing help - San Diego
"Cox is handing off to Peer1 in Dallas equinix for me, then back to LA. That would mean Peer1 has proper routes to cox, but cox's outbound to them is messed up."
How can this be resolved? |
|
| i have noticed packet loss on that equinix hop when i run line quality ping test's on this site |
|
| reply to Steve924
said by Steve924 :Just had Cox HSI based out of Las Vegas installed a month ago and service has been acceptable. I use it for general browsing, gaming and streaming media. I've been noticing a higher latency than I would consider normal for certain west coast gaming servers I connect to.
Tracing route to jennyfur.pelican.org [76.74.236.91]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms cmxp.lv.cox.net [192.168.2.1]
2 8 ms 9 ms 8 ms 10.80.0.1
3 9 ms 11 ms 7 ms 24-234-16-221.ptp.lvcm.net [24.234.16.221]
4 13 ms 10 ms 10 ms 24-234-6-125.ptp.lvcm.net [24.234.6.125]
5 15 ms 8 ms 12 ms 24-234-6-254.ptp.lvcm.net [24.234.6.254]
6 * 39 ms 44 ms 68.1.5.140
7 40 ms 45 ms 40 ms 10ge.ten1-3.dal-eqx-cor-1.peer1.net [206.223.118.30]
8 55 ms 54 ms 61 ms 10ge.ten1-2.la-600w-cor-2.peer1.net [216.187.124.121]
9 55 ms 61 ms 55 ms 10ge.xe-0-3-0.lax-600w-sbcor-2.peer1.net [216.187.88.46]
10 73 ms 48 ms 53 ms 10ge.xe-0-0-2.lax-600w-sbdis-1.peer1.net [216.187.88.138]
11 54 ms 47 ms 48 ms jennyfur.pelican.org [76.74.236.91]
Trace complete.
Mind you, that server is located in Los Angeles, CA. I'm in Las Vegas, NV. My packets seem to be going from NV to AZ to TX and THEN to CA. Seems a little too roundabout.
Here's a link to someone with the same issue:
»Re: [CA] COX HSI - High Latency - Bad routing help - San Diego
"Cox is handing off to Peer1 in Dallas equinix for me, then back to LA. That would mean Peer1 has proper routes to cox, but cox's outbound to them is messed up."
How can this be resolved?
Issue is with Peer 1, and not cox. Peer1's outbound routing is very erratic. I believe it peers with Cox at Sanjose/Palo Alto instead of Los Angeles. |
|
