View Single Post
Career Officer
Join Date: Jun 2012
Posts: 2,407
# 5
10-10-2013, 07:15 PM
Quote:
Originally Posted by jbmonroe View Post
...


7 22 ms 21 ms 15 ms 10.bu-ether15.orldfljo00w-bcr00.tbone.rr.com [66.109.6.9
8 36 ms 35 ms 27 ms bu-ether18.atlngamq47w-bcr01.tbone.rr.com [66.109.1.72]
9 25 ms 25 ms 33 ms 66.109.1.91

10 97 ms 104 ms 97 ms te0-0-0-10.ccr21.atl02.atlas.cogentco.com [154.54.12.109
11 96 ms 102 ms 93 ms be2052.mpd21.atl01.atlas.cogentco.com [154.54.40.249]
12 104 ms 118 ms 100 ms be2171.mpd22.dca01.atlas.cogentco.com [154.54.31.110]


Not sure why it goes bad during the transition from BrightHouse (RoadRunner) to Cogent, but it does so in a big way.
Normally, these latency values aren't too bad, assuming that there is no packet drop occurring...

Now the next question is what does the 'Net Test' results look like? Under normal conditions, sustained throughput should be in the 300 - 500 range. If your 'Net Test' results are much lower, then that would mean that the Road Runner gateway onto the Cogent Communication network would be silently dropping packets due to a lack of bandwidth, similar to the situation between Cogent and Verizon a few months ago...

The 'Net Test' network diagnostics is useful, because it doesn't connect to the STO servers, (so any performance issues caused by the servers are out of the picture,) instead, it connects to a diagnostic server that is one the same as the STO servers. So it measures straight Internet throughput performance. And if you don't have throughput, that means the STO servers can't get the data to maintain a session with your STO Client...

Last edited by grouchyotaku; 10-10-2013 at 07:22 PM.