Connectivity
Back to Top

high latency b/w two comcast business customers

ChrisR
New Member

high latency b/w two comcast business customers

We're seeing a high degree of latency on Comcast's network. Both sides are on Comcast Business internet accounts. The latency seems to start in Colorado, and only get worse as we get closer to our partner near Chicago. See the trace below (traken from our wired gateway).

 

Is this pretty standard for Comcast's backbones?

 

$ traceroute 96.92.221.14

traceroute to 96.92.221.14 (96.92.221.14), 30 hops max, 38 byte packets

1  50-255-11-206-static.hfc.comcastbusiness.net (50.255.11.206)  0.787 ms  0.624 ms  1.152 ms

2  96.120.89.133 (96.120.89.133)  11.080 ms  8.546 ms  9.626 ms

3  be-10002-sur03.novato.ca.sfba.comcast.net (68.86.142.33)  9.582 ms  10.248 ms  8.980 ms

4  be-17-ar01.sfsutro.ca.sfba.comcast.net (68.85.86.225)  9.890 ms  10.499 ms  9.631 ms

5  hu-0-18-0-6-ar01.santaclara.ca.sfba.comcast.net (68.85.154.117)  12.265 ms  hu-0-18-0-3-ar01.santaclara.ca.sfba.comcast.net (68.85.154.53)  12.340 ms  hu-0-18-0-6-ar01.santaclara.ca.sfba.comcast.net (68.85.154.117)  12.468 ms

6  be-33651-cr02.sunnyvale.ca.ibone.comcast.net (68.86.90.93)  13.367 ms  14.136 ms  14.156 ms

7  be-11021-cr02.1601milehigh.co.ibone.comcast.net (68.86.86.66)  42.675 ms  41.581 ms  48.914 ms

8  be-11721-cr02.denver.co.ibone.comcast.net (68.86.86.77)  39.660 ms  44.148 ms  42.798 ms

9  be-10517-cr02.350ecermak.il.ibone.comcast.net (68.86.85.169)  62.993 ms  62.920 ms  62.262 ms

10  be-7922-ar01.area4.il.chicago.comcast.net (68.86.91.166)  62.276 ms  63.991 ms  66.369 ms

11  68.87.211.122 (68.87.211.122)  62.832 ms  66.973 ms  71.097 ms

12  te-7-0-acr11.rollingmdws.il.chicago.comcast.net (162.151.91.102)  66.776 ms  te-7-1-acr11.rollingmdws.il.chicago.comcast.net (162.151.91.82)  65.719 ms  te-7-0-acr11.rollingmdws.il.chicago.comcast.net (162.151.91.102)  65.856 ms

Tags (1)
1 REPLY
Trusted Forum Contributor

Re: high latency b/w two comcast business customers

The data you present is inconclusive since the trace did not reach the target (96.92.221.14). Show the complete trace, please.

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