|reply to hamburglar_ |
Re: Terrible latency in the evenings... Powell, OH
said by hamburglar_:If you show that trace to a TW employee, they'll tell you there is nothing wrong with it since the destination is @92ms, ask hob. They will tell you to ignore the other hops and just look at the last hop. Of course, your problem is congested gateway(second hop) and you will need patience and time to convince TW that you have a congested node. Good luck!
I always see it starting on the second hop (10.160.64.1), so I'm not even leaving the local RR network and getting latency. During the day, it's almost solid less than 50ms.
Tracing route to google-public-dns-a.google.com [18.104.22.168]
over a maximum of 30 hops:
1 1 ms 1 ms <1 ms 192.168.50.2
2 592 ms 83 ms 69 ms 10.160.64.1
3 98 ms 80 ms 21 ms ae1-1112.cr02.clmcohib.midohio.rr.com [22.214.171.124]
4 319 ms * 353 ms be21.clevohek-ccr01.mwrtn.rr.com [126.96.36.199]
5 339 ms 485 ms 342 ms ae10-0.cr0.dca20.tbone.rr.com [188.8.131.52]
6 50 ms 45 ms 294 ms 184.108.40.206
7 292 ms 268 ms 204 ms 220.127.116.11
8 124 ms 123 ms 60 ms 18.104.22.168
9 74 ms 261 ms 158 ms 22.214.171.124
10 48 ms 60 ms 141 ms 126.96.36.199
11 147 ms 50 ms 69 ms 188.8.131.52
12 72 ms 36 ms 92 ms google-public-dns-a.google.com [184.108.40.206]
I know what you are saying, and the problem with tracert is that it happens over multiple seconds while waiting for DNS lookups. When I can ping the third hop and my destination at the same time and I see very similar 300-400ms results simultaneously, it is hard to argue with.
The tech that came out this time did seem to accept that a bigger problem was at hand. This is especially so since I can confirm the same issue with my neighbor down the street. Hell, I was even over at her house running pings that showed the same results during one of the slowdowns.
Keep up with the tech and don't keep your hope too high, sometimes they develop amnesia. Kidding aside, I hope they fix you up the soonest.
Orchard Park, NY
|reply to bluepoint |
"If you show that trace to a TW employee, they'll tell you there is nothing wrong with it since the destination is @92ms, ask hob."
Will you please stop running around these forums telling people what I might say.
Abnormal consistent ping times to the first hop indicates abnormal behavior.
"A foolish consistency is the hobgoblin of little minds."
- Ralph Waldo Emerson