dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
1586
share rss forum feed


RaleighTWC

@cisco.com

[TWC] High Backbone latency?

I'm currently seeing some abnormally high latency times in any of my traceroutes to various destinations (Google's public DNS, Yahoo, Youtube, etc) and they are starting on the backbone.

Local response times are good out until the backbone hops, at which point they jump from 30ms up into the 130-150ms range.

I would wager that TWC is aware of this and that I'm not the only one seeing it, but wanted to post here as well.

Traceroutes to follow.



RaleighTWC

@rr.com

Here are some traces:
Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.1
2 49 ms 18 ms 28 ms rrcs-24-172-248-1.midsouth.biz.rr.com [24.172.24
8.1]
3 35 ms 14 ms 15 ms 66.26.45.181
4 37 ms 19 ms 18 ms ae19.chrlncpop-rtr1.southeast.rr.com [24.93.64.2
]
5 34 ms 55 ms 33 ms ae-3-0.cr0.atl20.tbone.rr.com [66.109.6.82]
6 167 ms 160 ms 175 ms ae-0-0.pr0.atl20.tbone.rr.com [66.109.6.171]
7 193 ms 198 ms 217 ms 72.14.219.56
8 29 ms 32 ms 30 ms 72.14.233.56
9 34 ms 65 ms 32 ms 66.249.94.24
10 51 ms 33 ms 33 ms 209.85.248.57
11 * * * Request timed out.
12 33 ms 30 ms 31 ms google-public-dns-a.google.com [8.8.8.8]

Trace complete.

Tracing route to cnn-lax-tmp.gslb.vgtf.net [157.166.240.11]
over a maximum of 30 hops:

1 2 ms 1 ms 1 ms 192.168.1.1
2 32 ms 49 ms 28 ms rrcs-24-172-248-1.midsouth.biz.rr.com [24.172.24
8.1]
3 21 ms 16 ms 15 ms 66.26.45.181
4 20 ms 25 ms 40 ms ae19.chrlncpop-rtr1.southeast.rr.com [24.93.64.2
]
5 171 ms 157 ms 159 ms 107.14.19.18
6 154 ms 157 ms 161 ms ae-0-0.pr0.atl20.tbone.rr.com [66.109.6.171]
7 162 ms 157 ms 195 ms xe-7-1-0.edge4.Atlanta2.Level3.net [4.59.12.29]

8 35 ms 31 ms 42 ms vlan51.ebr1.Atlanta2.Level3.net [4.69.150.62]
9 152 ms 161 ms 178 ms ae-63-63.ebr3.Atlanta2.Level3.net [4.69.148.241]

10 191 ms 180 ms 176 ms ae-7-7.ebr3.Dallas1.Level3.net [4.69.134.21]
11 82 ms 82 ms 86 ms ae-3-3.ebr2.LosAngeles1.Level3.net [4.69.132.77]

12 221 ms 228 ms 229 ms ae-92-92.csw4.LosAngeles1.Level3.net [4.69.137.3
0]
13 83 ms 82 ms 86 ms ae-4-90.edge1.LosAngeles9.Level3.net [4.69.144.2
02]

Tracing route to 70.42.29.74 over a maximum of 30 hops

1 1 ms 1 ms 1 ms 192.168.1.1
2 48 ms 21 ms 51 ms rrcs-24-172-248-1.midsouth.biz.rr.com [24.172.24
8.1]
3 14 ms 32 ms 14 ms 66.26.45.181
4 57 ms 19 ms 18 ms ae19.chrlncpop-rtr1.southeast.rr.com [24.93.64.2
]
5 165 ms 180 ms 180 ms 107.14.19.18
6 155 ms 186 ms 182 ms ae-0-0.pr0.atl20.tbone.rr.com [66.109.6.171]
7 36 ms 36 ms 34 ms Vlan556.icore1.A56-Atlanta.as6453.net [209.58.44
.49]
8 159 ms 163 ms 152 ms if-3-1715.tcore1.AEQ-Ashburn.as6453.net [209.58.
44.22]
9 190 ms 175 ms 186 ms if-9-0-0.mcore3.TTT-Scarborough.as6453.net [216.
6.98.113]
10 178 ms 171 ms 168 ms if-0-0-0-0.tcore1.TTT-Scarborough.as6453.net [64
.86.32.1]
11 72 ms 54 ms 53 ms if-9-9.tcore1.TNK-Toronto.as6453.net [64.86.33.2
5]
12 186 ms 181 ms 167 ms if-0-0-0-4.core4.TNK-Toronto.as6453.net [63.243.
172.29]
13 51 ms 79 ms 49 ms ix-4-0-3.core4.TNK-Toronto.as6453.net [216.6.49.
2]
14 50 ms 50 ms 49 ms border1.te9-1-bbnet2.tor001.pnap.net [70.42.24.1
96]

Extended ping to the hop in question:
ping -t 66.109.6.171

Pinging 66.109.6.171 with 32 bytes of data:
Reply from 66.109.6.171: bytes=32 time=184ms TTL=58
Reply from 66.109.6.171: bytes=32 time=166ms TTL=58
Reply from 66.109.6.171: bytes=32 time=161ms TTL=58
Reply from 66.109.6.171: bytes=32 time=201ms TTL=58
Reply from 66.109.6.171: bytes=32 time=156ms TTL=58
Reply from 66.109.6.171: bytes=32 time=194ms TTL=58
Reply from 66.109.6.171: bytes=32 time=155ms TTL=58
Reply from 66.109.6.171: bytes=32 time=163ms TTL=58
Reply from 66.109.6.171: bytes=32 time=165ms TTL=58
Reply from 66.109.6.171: bytes=32 time=202ms TTL=58
Reply from 66.109.6.171: bytes=32 time=160ms TTL=58
Reply from 66.109.6.171: bytes=32 time=149ms TTL=58
Reply from 66.109.6.171: bytes=32 time=159ms TTL=58
Reply from 66.109.6.171: bytes=32 time=159ms TTL=58
Reply from 66.109.6.171: bytes=32 time=156ms TTL=58
Reply from 66.109.6.171: bytes=32 time=157ms TTL=58
Reply from 66.109.6.171: bytes=32 time=154ms TTL=58
Reply from 66.109.6.171: bytes=32 time=196ms TTL=58
Reply from 66.109.6.171: bytes=32 time=158ms TTL=58
Reply from 66.109.6.171: bytes=32 time=157ms TTL=58
Reply from 66.109.6.171: bytes=32 time=167ms TTL=58
Reply from 66.109.6.171: bytes=32 time=158ms TTL=58
Reply from 66.109.6.171: bytes=32 time=157ms TTL=58
Reply from 66.109.6.171: bytes=32 time=163ms TTL=58
Reply from 66.109.6.171: bytes=32 time=157ms TTL=58
Reply from 66.109.6.171: bytes=32 time=153ms TTL=58
Reply from 66.109.6.171: bytes=32 time=172ms TTL=58
Reply from 66.109.6.171: bytes=32 time=166ms TTL=58
Reply from 66.109.6.171: bytes=32 time=159ms TTL=58
Reply from 66.109.6.171: bytes=32 time=188ms TTL=58
Reply from 66.109.6.171: bytes=32 time=157ms TTL=58
Reply from 66.109.6.171: bytes=32 time=160ms TTL=58

Ping statistics for 66.109.6.171:
Packets: Sent = 32, Received = 32, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 149ms, Maximum = 202ms, Average = 165ms

While no loss is being seen, there is certainly an increase in latency here. There seems to be a slight jump at the CMTS as well, but the largest is to be found on the backbone.



RaleighTWC

@rr.com

Once again the problem persists tonight, with latency reliably going up at around 7:30 PM EST and it will reliably go back down around 11-11:30 PM EST.

I have to believe that this is more localized to my CMTS at this point, I can't imagine such a drastic increase in latency on the backbone during primetime would go overlooked. My only hope is that perhaps someone else on here is seeing this issue and can throw a little weight behind it.


harald

join:2010-10-22
Columbus, OH
kudos:1

There is no problem with your latencies.

Latency only counts when it occurs at the server you are trying to use. Intermediate high pings are NOT an issue.


Fleeced

join:2012-10-06
kudos:2

And none of those pings I would consider "High". Having up to 300ms of ping times is pretty typical, so there's no real issue that you're showing soon.



neumannu47
Premium
join:2002-08-14
USA
reply to RaleighTWC

My ping times are higher than normal tonight in Cary, and my streaming video is choppy. It sure seems like excessive traffic somewhere close by.


meks

join:2013-01-13
Dallas, TX
reply to RaleighTWC

I've been having some issues as well in the DFW area.

Tracing route to www.google.com [173.194.77.103]
over a maximum of 30 hops:

1 80 ms 32 ms 29 ms cpe-76-187-96-1.tx.res.rr.com [76.187.96.1]
2 14 ms 13 ms 15 ms 70.125.216.173
3 18 ms 16 ms 17 ms tge8-1.dllatx12-er01.texas.rr.com [24.175.39.136]
4 48 ms 23 ms 24 ms tge2-2.dllatx1k-tr01.texas.rr.com [24.175.38.4]
5 27 ms 23 ms 23 ms agg21.dllatxl3-cr01.texas.rr.com [24.175.49.0]
6 22 ms 23 ms 23 ms ae-4-0.cr0.dfw10.tbone.rr.com [66.109.6.88]
7 18 ms 18 ms 16 ms 107.14.17.234
8 1817 ms 855 ms 230 ms 74.125.48.65
9 18 ms 17 ms 18 ms 72.14.233.67
10 16 ms 38 ms 24 ms 72.14.237.217
11 110 ms 23 ms 22 ms 216.239.47.121
12 25 ms 22 ms 25 ms 216.239.46.61
13 * * * Request timed out.
14 130 ms 16 ms 19 ms ob-in-f103.1e100.net [173.194.77.103]


nephipower

join:2012-02-20
San Antonio, TX

Well posting on this forum is not going to help at all. You are going to need to either post on the direct forum for TWC or call tech support and inform them of the problem.

I would try direct forum first since trying to work with tech support on the phone will be like talking to a brick wall most of the time.


Fleeced

join:2012-10-06
kudos:2
reply to RaleighTWC

Meks, your ping spike happens on google's network, which TWC can't fix.