Connectivity
Back to Top

Poor routing between Comcast and XO Communications

SOLVED
Highlighted
hsskc
Visitor

Poor routing between Comcast and XO Communications

I recently got Comcast internet service at a remote location and I have set up a site-to-site VPN connection between that office and the main office. Both offices are in the same city (Bellevue, WA) but I am seeing very poor routing between that site and the main site. Our main site has XO Communications as the ISP.

 

When doing a trace route from the remote site to the main site it takes over 17 hops and goes all the way down to San Jose, CA and back. This seems terribly inefficient to me. I contacted XO and they said all looks good on their end and to contact Comcast or the intermediary peer between the two companies (TATA Communications) so I am continuing on here with asking Comcast if they can do anything. Also, I am consistently averaging around 4% packet loss between the sites.

 

Here is a trace from the server at the remote site to the gateway router at the main site:

 

Tracing route to 64.221.112.185.ptr.us.xo.net [64.221.112.185] over a maximum of 30 hops:

 1    <1 ms    <1 ms    <1 ms  64.221.112.185.ptr.us.xo.net [64.221.112.185]

  2     1 ms    <1 ms     1 ms  74-93-110-94-seattle.hfc.comcastbusiness.net [74.93.110.94]

  3     9 ms    10 ms     8 ms  73.105.112.1

  4     8 ms     7 ms     7 ms  te-0-0-0-14-ur05.bellevue.wa.seattle.comcast.net [68.85.144.209]

  5    12 ms     7 ms    15 ms  be-1-ur06.bellevue.wa.seattle.comcast.net [69.139.164.122]

  6    11 ms     8 ms     9 ms  ae-18-0-ar03.seattle.wa.seattle.comcast.net [69.139.164.117]

  7    19 ms    23 ms    11 ms  he-1-6-0-0-11-cr01.seattle.wa.ibone.comcast.net[68.86.92.33]

  8    12 ms     9 ms    15 ms  pos-0-0-0-0-pe01.seattle.wa.ibone.comcast.net [68.86.86.138]

  9     9 ms     9 ms     9 ms  ix-0-3-1-0.tcore1.00s-seattle.as6453.net [66.110.64.1]

 10    29 ms    29 ms    29 ms  if-14-2.tcore1.pdi-paloalto.as6453.net [64.86.123.22]

 11    30 ms    32 ms    39 ms  if-2-2.tcore2.pdi-paloalto.as6453.net [66.198.127.2]

 12    35 ms    29 ms    39 ms  if-2-0-0.core3.sqn-sanjose.as6453.net [66.198.144.46]

 13    63 ms    53 ms    54 ms  vlan1105.icore1.sqn-sanjose.as6453.net [66.198.97.42]

 14    54 ms    53 ms    53 ms  ix-10-12.icore1.sqn-sanjose.as6453.net [209.58.116.46]

 15    58 ms    71 ms    57 ms  207.88.14.225.ptr.us.xo.net [207.88.14.225]

 16    73 ms    89 ms    96 ms  ae0d0.mcr2.seattle-wa.us.xo.net [216.156.0.198]

 17    76 ms    78 ms    81 ms  ge13-0.clr1.seattle-wa.us.xo.net [207.88.83.150]

 18   137 ms    77 ms    79 ms  64.221.112.185.ptr.us.xo.net [64.221.112.185]

 

And here is a trace between a server at the main site and the gateway router at the remote site:

Tracing route to 74-93-110-94-seattle.hfc.comcastbusiness.net [74.93.110.94]over a maximum of 30 hops:

1    <1 ms    <1 ms    <1 ms  internal.local [192.168.1.1]

  2     *        1 ms     1 ms  64.221.112.185.ptr.us.xo.net [64.221.112.185]

  3     7 ms     6 ms     8 ms  64.221.118.5.ptr.us.xo.net [64.221.118.5]

  4     5 ms     5 ms     5 ms  207.88.83.149.ptr.us.xo.net [207.88.83.149]

  5    26 ms    27 ms    27 ms  vb1811.rar3.sanjose-ca.us.xo.net [216.156.0.197]

  6    23 ms    23 ms    23 ms  207.88.14.226.ptr.us.xo.net [207.88.14.226]

  7    31 ms    52 ms    36 ms  if-10-12.icore1.sqn-sanjose.as6453.net [209.58.116.45]

  8    35 ms    34 ms    35 ms  vlan3260.icore2.sqn-sanjose.as6453.net [64.86.142.1]

  9    43 ms    34 ms    34 ms  if-17-2170.tcore2.lvw-losangeles.as6453.net [64.86.252.141]

 10    50 ms    51 ms    51 ms  64.86.252.18

 11    54 ms    59 ms    59 ms  he-0-12-0-0-cr01.sacramento.ca.ibone.comcast.net [68.86.86.5]

 12    68 ms    68 ms    68 ms  so-4-1-0-0-ar03.burien.wa.seattle.comcast.net [68.86.91.130]

 13    70 ms    69 ms    70 ms  be-18-ur05.bellevue.wa.seattle.comcast.net [69.139.164.114]

 14    70 ms    70 ms    70 ms  te-1-0-0-ten15.bellevue.wa.seattle.comcast.net [68.85.144.210]

 15    89 ms    77 ms    77 ms  74-93-110-94-seattle.hfc.comcastbusiness.net [74.93.110.94]

Accepted Solution

Re: Poor routing between Comcast and XO Communications

Welcome Hsskc.  I have referred you case to Comcast Network Operations.  I will update you with their response.

 

Thank You

 

View solution in context
Community Manager
Community Manager

Re: Poor routing between Comcast and XO Communications

Welcome Hsskc.  I have referred you case to Comcast Network Operations.  I will update you with their response.

 

Thank You

 

Discussion stats
  • 1 reply
  • 2338 views
  • 0 kudos
  • 2 in conversation