View Single Post
Ensign
Join Date: Dec 2012
Posts: 1
# 26 Same for me.
01-12-2013, 01:14 PM
3 25 ms 23 ms 29 ms ************ [*.*.*.*]
4 28 ms 31 ms 35 ms ************ [*.*.*.*]
5 24 ms 25 ms 23 ms ae-1.r00.londen01.uk.bb.gin.ntt.net [83.231.199.161]
6 25 ms 26 ms 24 ms ae-6.r02.londen03.uk.bb.gin.ntt.net [129.250.3.2]
7 24 ms 25 ms 24 ms te2-4.mag01.lon02.atlas.cogentco.com [130.117.14.173]
8 149 ms 205 ms 205 ms te7-2.ccr01.lon02.atlas.cogentco.com [130.117.50.138]
9 27 ms 27 ms 24 ms te0-0-0-2.ccr21.lon01.atlas.cogentco.com [130.117.1.157]
10 29 ms 31 ms 27 ms te0-1-0-4.mpd21.lon13.atlas.cogentco.com [154.54.57.98]
11 103 ms 102 ms 103 ms te0-3-0-4.ccr21.bos01.atlas.cogentco.com [154.54.30.129]
12 104 ms 108 ms 99 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42]
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 * * * Request timed out.
20 * * * Request timed out.
21 * ^C


Same, clearly a routing issue between Cogentco and whomever hosts the STO network.