dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
145
share rss forum feed

kokkatc

join:2012-12-20
reply to kokkatc

Re: [CA] COX HSI - High Latency - Bad routing help - San Diego

Couple traceroute examples.

San Diego to Los Angeles Server:

Tracing route to jennyfur.pelican.org [76.74.236.91]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 1.0.16.172.in-addr.arpa [172.16.0.1]
2 8 ms 8 ms 8 ms 1.0.133.10.in-addr.arpa [10.133.0.1]
3 8 ms 8 ms 8 ms ip68-6-12-132.sd.sd.cox.net [68.6.12.132]
4 9 ms 8 ms 9 ms 202.11.6.68.in-addr.arpa [68.6.11.202]
5 12 ms 9 ms 8 ms fed1dsrj01-xe130.0.rd.sd.cox.net [68.6.8.0]
6 * * 39 ms 68.1.5.140
7 39 ms 40 ms 38 ms 10ge.ten1-3.dal-eqx-cor-1.peer1.net [206.223.118
.30]
8 45 ms 44 ms 44 ms 10ge.ten1-2.la-600w-cor-2.peer1.net [216.187.124
.121]
9 47 ms 44 ms 48 ms 10ge.xe-0-3-0.lax-600w-sbcor-2.peer1.net [216.18
7.88.46]
10 48 ms 45 ms 46 ms 10ge.xe-0-0-2.lax-600w-sbdis-1.peer1.net [216.18
7.88.138]
11 44 ms 45 ms 44 ms jennyfur.pelican.org [76.74.236.91]

Trace complete.

-------------------

San Diego to San Diego Server (15 miles away)

Tracing route to jennyfur.pelican.org [76.74.236.91]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 1.0.16.172.in-addr.arpa [172.16.0.1]
2 8 ms 8 ms 8 ms 1.0.133.10.in-addr.arpa [10.133.0.1]
3 8 ms 8 ms 8 ms ip68-6-12-132.sd.sd.cox.net [68.6.12.132]
4 9 ms 8 ms 9 ms 202.11.6.68.in-addr.arpa [68.6.11.202]
5 12 ms 9 ms 8 ms fed1dsrj01-xe130.0.rd.sd.cox.net [68.6.8.0]
6 * * 39 ms 68.1.5.140
7 39 ms 40 ms 38 ms 10ge.ten1-3.dal-eqx-cor-1.peer1.net [206.223.118
.30]
8 45 ms 44 ms 44 ms 10ge.ten1-2.la-600w-cor-2.peer1.net [216.187.124
.121]
9 47 ms 44 ms 48 ms 10ge.xe-0-3-0.lax-600w-sbcor-2.peer1.net [216.18
7.88.46]
10 48 ms 45 ms 46 ms 10ge.xe-0-0-2.lax-600w-sbdis-1.peer1.net [216.18
7.88.138]
11 44 ms 45 ms 44 ms jennyfur.pelican.org [76.74.236.91]

Trace complete.

------------------

I generally ping better or the same to Texas servers than I do to California servers. It's quite frustrating.

nickphx

join:2009-10-29
Phoenix, AZ
If you look at that second traceroute, COX handed it off to PEER1 in San Diego at hop 7... So that "poor routing" is on PEER1, not COX.

Those two traceroutes are to the same IP address...

Ameth

join:2011-07-20
said by nickphx:

Those two traceroutes are to the same IP address...

I noticed that too. Each location should have a different IP.

cookiesowns

join:2010-08-31
Irvine, CA
reply to kokkatc
Those two traceroutes are to the same end point..

The issue is with peer1 btw. As far as I know peer1 has peering with cox, or uses similar peering fabric to certain areas.

The traceroute you provided shows that your CMTS hands off to equinix peer1 in Dallas, then hauls the traffic back to 600west LA.

I'm not sure on the return path, but from what I can tell based on the latency, Peer1 is taking a scenic route to PaloAlto where cox commonly peers in California with peer1 ( known issue ) and back to your sandiego CMTS.

For me in LA, I commonly see this issue with peer1. Had several colod machines / ventrilo servers that would take a scenic route to my home connection here in OC. It would either loop around LA to PA then back to LA, or even loop to LA - Dal then back to LA. I've even seen a wierder one such as LA - PA - Dal - LA with peer1 once. I suggest you contact their NOC ( peer 1 ) and push them to resolve this.

Oh wow, my memory served me wrong. 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.

kokkatc

join:2012-12-20
Sorry about the late response.

Thanks for the INFO. I do have one question....

To my knowledge by NOC, you mean Networking Operations Center. How do I go about contacting the suspect NOC (peer1) to discuss the matter? Finding someone at Cox who even understands the basics of routing is tough to find, and I'm just a novice in networking.

Thanks again.