Welcome to the Cox Community
Our community is a collaborative place to learn about Cox products and services. Jump into the conversation today!
Messages
Selected Messages
New Contributor
•
Connection to XO in San Diego
I use to have a solid and fast connection to XO in San Diego. Something has changed in the last month or so and the connection now goes via San Jose over to Level 3 and then back down to XO. My latency has consequentially gone from <20ms to over 50+. I would like to know if the change in connection to XO is a temporary thing or if that is a permanent change in Cox's peering arrangements. I am a Cox San Diego customer. Please let me know the answer so I can plan accordingly.
MichaelJ
Moderator
•
0
0
Richard_Tomson_
New Contributor
•
Your Results
Start
Net
Speed
Speed
Latency
Address
Cox Market
This only tests inside of COX, the issue is with the interconnections. Something changed on the handoffs, in particular with XO. Were there any changes in the last few months that removed connections in San Diego? Also I don't know how the system is programmed on the traffic shaping but I can NEVER get 16Mbps up ever. I just tried to upload a 700MB file and it capped at 5Mbps. That I can live with, but please let me know about the XO handoff and what changed. Thanks, Rich.
0
0
Health_Edge
+5 more
Valued Contributor III
•
Can you post a tracert to show this change? Routing is dictated by a lot of things and can't be changed for a single user.
0
0
Richard_Tomson_
New Contributor
•
So you can see, we are going to Cox SD -> Cox San Jose and then via Level 3. I would still like to know what happened to
the direct connect to XO. And yes having helped start fund and operate 3 Internet Service Providers in
the last 30 years I fully understand routing can't be changed just for me. I would just like to know what did change
and why the previous connection no longer exists. Reverse traceroute shows the same path via San Jose.
traceroute to 216.120.34.2 (216.120.34.2), 30 hops max, 60 byte packets
1 rat-3560g-1.corp.ratmotor.com (10.254.253.1) [AS65534] 1.174 ms 1.413 ms 1.686 ms
2 * * *
3 ocnscmtk03-gex030000.sd.sd.cox.net (68.6.11.210) [AS22773] 13.340 ms 13.371 ms 13.347 ms
4 * * *
5 fed1dsrj02-xe130.0.rd.sd.cox.net (68.6.8.4) [AS22773] 15.248 ms 15.224 ms 15.185 ms
6 sanjbprj01-ae0.0.rd.sj.cox.net (68.1.5.184) [AS22773] 28.039 ms 26.838 ms 27.790 ms
7 xe-8-2-1.edge1.SanJose3.Level3.net (4.53.209.85) [AS3356] 32.358 ms xe-8-2-2.edge1.SanJose3.Level3.net (4.53.209.81) [AS3356] 38.748 ms xe-11-2-3.edge1.SanJose3.Level3.net (4.53.208.5) [AS3356] 54.072 ms
8 ae-43-90.car3.SanJose1.Level3.net (4.69.152.197) [AS3356] 28.702 ms ae-13-60.car3.SanJose1.Level3.net (4.69.152.5) [AS3356] 28.673 ms ae-33-80.car3.SanJose1.Level3.net (4.69.152.133) [AS3356] 34.048 ms
9 XO-COMMUNIC.car3.SanJose1.Level3.net (4.71.112.78) [AS3356] 27.035 ms 27.606 ms 24.362 ms
10 207.88.14.233.ptr.us.xo.net (207.88.14.233) [AS2828] 42.373 ms 41.998 ms 41.966 ms
11 ae0d0.mcr1.sandiego-ca.us.xo.net (216.156.0.122) [AS2828] 44.967 ms 44.395 ms 44.488 ms
12 ae1d0.mcr2.sandiego-ca.us.xo.net (216.156.1.62) [AS2828] 37.549 ms 35.760 ms 35.508 ms
13 216.55.27.154 (216.55.27.154) [AS2828] 36.391 ms 36.098 ms 40.089 ms
0
0
Health_Edge
+5 more
Valued Contributor III
•
Maybe a Moderator might be able to say, but I some how doubt it. You would need to get on contact with one of the local engineers.
Is this a normal cable modem connection or something Cox Business? The first hop confuses me.
0
0
Richard_Tomson_
New Contributor
•
Maybe one will chime in if they know what happened with the connection. The first hop is internal to my
network so you can ignore that and the second hop is hitting my firewall which will not respond so it can
be ignored also. Running through the historical BGP table entries to see if I can pinpoint the day of the change.
0
0
EdwardH
Valued Contributor
•
---
0
0