Connectivity
Connectivity and managing Your Comcast Business network
Male IT Specialist Holds Laptop and Discusses Work with Female Server Technician. They're Standing in Data Center, Rack Server Cabinet is Open.
npanno
New Member

Comcast Peering with Century Link (Qwest) Chicago High Latency

What is the story with Comcast peering in Chicago with Century Link (Formerly Qwest) out of 350 Cermak?  I've consistently had enormous latency within the Chicago metro area for the past few days to all my customers that are on Century Link.  I've tried from other ISPs and latency is well under 35ms locally.   I'm getting tired of watching screen redrawing for something that is less than 3 miles away.

 

 

 7    14 ms    16 ms    19 ms  pos-1-5-0-0-pe01.350ecermak.il.ibone.comcast.net [68.86.87.126]
 8   150 ms   158 ms     *     chp-edge-01.inet.qwest.net [216.207.8.189]

0 Kudos
3 REPLIES 3
Community Manager
Community Manager

Re: Comcast Peering with Century Link (Qwest) Chicago High Latency

Welcome npanno.  Our Tier 2 agent tested from the gateway IP associated with this account to IP 216.207.8.189 as well as from the Comcast edge router to IP 216.207.8.189 and could not reproduce the results from your post.  Test result below.

 

Main> tracert 216.207.8.189 0<<<<<<<<<<<<<<<<Comcast gateway
Press Ctrl-C to stop ...
traceroute to 216.207.8.189 (216.207.8.189), 30 hops max, 60 byte packets
1 XXX.XXX.XXX.62 30.000 ms 30.000 ms 30.000 ms
2 68.85.131.205 20.000 ms 20.000 ms 20.000 ms
3 68.87.230.90 20.000 ms 68.87.229.86 20.000 ms 68.87.229.82 20.000 ms
4 68.87.230.93 20.000 ms 68.86.187.197 20.000 ms 10.000 ms
5 68.86.90.53 10.000 ms 10.000 ms 10.000 ms
6 68.86.87.130 10.000 ms 20.000 ms 20.000 ms
7 216.207.8.189 20.000 ms 20.000 ms 20.000 ms

 

RP/0/RP0/CPU0Smiley Tonguee04.350ecermak.il.ibone#traceroute 216.207.8.189<<<<<<<<<Comcast edge router
Type escape sequence to abort.

Tracing the route to 216.207.8.189

1 chp-edge-01.inet.qwest.net (216.207.8.189) 2 msec 0 msec 0 msec
RP/0/RP0/CPU0Smiley Tonguee04.350ecermak.il.ibone#

 

 

Thank You

 

0 Kudos
MDApache6
New Member

Re: Comcast Peering with Century Link (Qwest) Chicago High Latency

We have had the same thing every night for about two weeks now.  It starts around 7 PM and ends between 10:15 and 10:30 PM CT.   Extremely high latency and packet loss between 2% and 9%.
 
I have begged Comcast techs to escalate to Qwest, but they say they can't help me and that I should call Qwest.  I'm not a Qwest customer, but COMCAST IS!  What am I going to tell Qwest when they want my account number?
 
9 17 ms 21 ms 23 ms he-0-11-0-0-pe04.350ecermak.il.ibone.comcast.net [68.86.83.58]
10 131 ms 132 ms 135 ms chp-edge-01.inet.qwest.net  [216.207.8.189]
11 * * * Request timed out.
12 145 ms 141 ms 143 ms 65-124-162-206.dia.static.qwest.net  [65.124.162.206]
13 47 ms 47 ms 49 ms v10.c4500-1.mpls.iphouse.net  [216.250.189.130]
14 * 147 ms 143 ms iphouse.net [209.240.94.1]
 
Comcast should be all over Qwest complaining for their customers!  I am trying to get to a colo facility that is 20 miles away and it is ridiculous!  If Comcast can't fight the battle with  Qwest for their customers then I have to cancel my service; it isn't usable like this.

 

0 Kudos
Trusted Forum Contributor

Re: Comcast Peering with Century Link (Qwest) Chicago High Latency

Sorry to bump an old thread there and no intention of hijacking it, but I've been having similar issues for weeks to Chicago. Pretty much consistent packet loss and high latency. Normally I ping 60s to Chicago and now I'm lucky to be under 100 :/  Near impossible to remotely access our servers there due to this. 

 

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 10.1.10.1 - 0 | 221 | 221 | 0 | 0 | 1 | 0 |
| 96.188.38.1 - 0 | 221 | 221 | 2 | 7 | 14 | 7 |
|te-8-2-ur01.placerville.ca.ccal.comcast.net - 0 | 221 | 221 | 3 | 8 | 144 | 8 |
| 69.139.222.57 - 0 | 221 | 221 | 11 | 16 | 86 | 13 |
|he-1-1-0-0-11-cr01.losangeles.ca.ibone.comcast.net - 0 | 221 | 221 | 15 | 21 | 32 | 19 |
| xe-9-0-3.lax20.ip4.tinet.net - 1 | 218 | 217 | 14 | 26 | 97 | 32 |
| xe-4-2-0.chi12.ip4.tinet.net - 0 | 221 | 221 | 65 | 72 | 136 | 66 |
| internap-gw.ip4.tinet.net - 10 | 163 | 148 | 109 | 112 | 123 | 114 |
| border5.po2-bbnet2.chg.pnap.net - 7 | 174 | 162 | 109 | 115 | 309 | 309 |
| HowToVentrilo.com - 35 | 94 | 62 | 110 | 112 | 117 | 110 |
|________________________________________________|______|______|______|______|______|______|

 

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|border5.te7-3.nuclearfallout-60.chg.pnap.net - 0 | 229 | 229 | 0 | 1 | 44 | 0 |
| core1.te2-1-bbnet1.chg.pnap.net - 0 | 229 | 229 | 0 | 0 | 1 | 0 |
|te0-5-0-33.ccr21.ord03.atlas.cogentco.com - 2 | 217 | 214 | 0 | 0 | 7 | 0 |
|be-202-pe04.350ecermak.il.ibone.comcast.net - 9 | 173 | 159 | 42 | 44 | 263 | 43 |
|he-3-3-0-0-cr01.350ecermak.il.ibone.comcast.net - 9 | 170 | 155 | 42 | 44 | 47 | 44 |
|he-1-13-0-0-cr01.denver.co.ibone.comcast.net - 9 | 173 | 158 | 66 | 67 | 70 | 68 |
|he-0-12-0-0-cr01.denverqwest.co.ibone.comcast.net - 6 | 185 | 174 | 66 | 67 | 70 | 68 |
|he-4-11-0-0-cr01.sanjose.ca.ibone.comcast.net - 6 | 189 | 179 | 92 | 94 | 96 | 94 |
|pos-0-11-0-0-cr01.charlotte.nc.ibone.comcast.net - 10 | 166 | 150 | 0 | 97 | 176 | 95 |
|te-9-3-ur01.placerville.ca.ccal.comcast.net - 12 | 157 | 139 | 104 | 105 | 270 | 104 |
|te-1-0-0-ten01.placerville.ca.ccal.comcast.net - 14 | 149 | 129 | 96 | 96 | 97 | 96 |
| c-98-242-32-142.hsd1.ca.comcast.net - 8 | 181 | 168 | 107 | 112 | 124 | 111 |
|________________________________________________|______|______|______|______|______|______|

Believe it or not, this is when the issue is mild. 

0 Kudos