|reply to OSUGoose |
Re: Terrible latency in the evenings... Powell, OH
Our local routes look to be different, but I wonder if we are both seeing node congestion? Does yours slow down in the evening, or is it all day?
We take a slightly diff path, because im on the Insight/RR and your on TWC/RR, but we share:
5 631 ms be21.clevohek-ccr01.mwrtn.rr.com [22.214.171.124]
6 659 ms ae10-0.cr0.dca20.tbone.rr.com [126.96.36.199]
Beyond that we differ because I hit a local server, while you hit google's.
Try downloading Ping Plotter and let it run during a typical slowdown period, I've seen others get more results when RR is faced with that data.
And I get the normal evening slowdowns, but there are times off-peak I slow down too, and im on Turbo 15/.768 D2 package.
I see latency well before those hops. Generally
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 [188.8.131.52]
If I ping 184.108.40.206 during slow times, I see the high latency before even getting past that router.
You need to download PingPlotter, it does pings in set intervals to normalize the results.
I have it running against ohiodominican.edu now. I ran ping plotter off and on over the last 9 months, but it usually shows my first or second hop on the TW network, which would seem to be something more local to me...
ok, I just know from experience RR wont listen to the build in ping cmd, they wanted a Ping Plotter to see how it ranged. Could be your neighborhood needs rebalanced esp since its cold and cabling could be retracting from the fittings and allowing some leakage, or RR is being cheep and have oversold you.
It happens in all temperatures, but was sporadic over the last couple months. It's been every night since Sunday so far this week. I'm leaning toward oversold, but good luck proving it.