Perhaps someone more knowledgeable than me can explain if it IS charter's issue, why the only delays/timeouts for the trace routes I do come back for GTT.net and mostly NYC area nodes.
In the last 5 mins .... (personal IP addy removed jus cause...)
3 9 ms 8 ms 8 ms dtr01wvvlnc-tge-0-0-1-2.wvvl.nc.charter.com [96.
34.67.105]
4 10 ms 8 ms 8 ms crr01ahvlnc-bue-21.ahvl.nc.charter.com [96.34.92
.52]
5 13 ms 14 ms 17 ms crr11gnvlsc-bue-10.gnvl.sc.charter.com [96.34.93
.243]
6 13 ms 20 ms 13 ms bbr01gnvlsc-bue-3.gnvl.sc.charter.com [96.34.2.1
12]
7 20 ms 22 ms 15 ms bbr01spbgsc-bue-1.spbg.sc.charter.com [96.34.0.4
2]
8 19 ms 22 ms 22 ms bbr02atlnga-bue-4.atln.ga.charter.com [96.34.0.4
0]
9 19 ms 20 ms 18 ms prr01atlnga-bue-3.atln.ga.charter.com [96.34.3.1
9]
10 19 ms 23 ms 20 ms 96-34-150-42.static.unas.mo.charter.com [96.34.1
50.42]
11 22 ms 20 ms 17 ms ae0-60g.cr1.atl1.us.as4436.gtt.net [69.31.135.12
9]
12 25 ms 28 ms 26 ms ae4-69.atl11.ip4.gtt.net [173.241.128.141]
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * 44 ms 46 ms 170.rogean.com [108.61.129.170]
Trace complete.
Krey
|