[Chrysalis]

its the infamous 62.253.188.94, had no end of problems with that hop that made me move a server to different transit just to avoid it.

---------- Post added at 21:45 ---------- Previous post was at 21:40 ----------

haha ignition take a look at this.

when I first entered the traceroute page I was on the colc-2 proxy and route was this.

216-196-110-1.ams.giganews.com (216.196.110.1) 0 ms 0 ms 0 ms
2 amst-ic-1.inet.ntl.com (195.69.144.40) 0 ms 0 ms 0 ms
3 pop-bb-b-as0-0.inet.ntl.com (62.253.188.93) 8 ms 8 ms 8 ms
4 lee-bb-a-so-700-0.inet.ntl.com (62.253.185.237) 13 ms 15 ms 31 ms
5 nth-bb-b-so-000-0.inet.ntl.com (62.253.185.101) 17 ms 17 ms 19 ms
6 colc-t2core-b-pos31.inet.ntl.com (62.253.188.206) 19 ms 19 ms 20 ms
7 colc-cache-2.server.ntli.net (213.107.224.18) 19 ms 26 ms 19 ms

so I thought to myself I am going to use a leics proxy see if the routing changes and bam.

1 216-196-110-1.ams.giganews.com (216.196.110.1) 9 ms 0 ms 6 ms
2 216-196-108-122.ams.giganews.com (216.196.108.122) 0 ms 0 ms 0 ms
3 * * *
4 * * *
5 so-4-2.core2.Amsterdam1.Level3.net (212.73.240.181) 3 ms 0 ms 0 ms
6 ge-0-0-0.mp2.Amsterdam1.Level3.net (4.68.96.197) 0 ms 0 ms 0 ms
7 as-1-0.bbr2.London1.Level3.net (212.187.128.25) 8 ms 7 ms 7 ms
8 ae-0-52.gar2.London1.Level3.net (4.68.116.44) 7 ms ae-0-56.gar2.London1.Level3.net (4.68.116.172) 8 ms ae-0-52.gar2.London1.Level3.net (4.68.116.44) 7 ms
9 195.50.91.70 (195.50.91.70) 17 ms 13 ms 13 ms
10 nth-bb-b-so-400-0.inet.ntl.com (213.105.172.13) 13 ms 13 ms 15 ms
11 leic-t2core-b-so-000-0.inet.ntl.com (62.253.188.113) 14 ms 14 ms 14 ms
12 leic-sm-cat-v2.inet.ntl.com (82.3.32.61) 13 ms 15 ms 13 ms
13 leic-cache-7.server.ntli.net (82.3.32.77) 13 ms 13 ms 13 ms

---------- Post added at 21:47 ---------- Previous post was at 21:45 ----------

nottingham

1 216-196-110-1.ams.giganews.com (216.196.110.1) 0 ms 0 ms 0 ms
2 adm-b2-geth3-2.telia.net (213.248.73.1) 0 ms 0 ms 0 ms
3 adm-bb2-pos0-0-0.telia.net (213.248.64.189) 8 ms 0 ms 0 ms
4 ldn-bb2-pos7-2-0.telia.net (213.248.65.157) 8 ms 8 ms 8 ms
5 ldn-b2-pos11-1.telia.net (213.248.74.10) 8 ms 8 ms 8 ms
6 ntl-111210-ldn-b2.c.telia.net (213.248.100.38) 164 ms 145 ms *
7 bre-bb-b-as0-0.inet.ntl.com (62.253.188.122) 22 ms 24 ms 21 ms
8 bre-bb-a-ae0-0.inet.ntl.com (213.105.172.86) 21 ms 21 ms 42 ms
9 gfd-bb-b-so-700-0.inet.ntl.com (213.105.172.150) 16 ms 15 ms 16 ms
10 nth-bb-a-so-000-0.inet.ntl.com (62.253.185.97) 16 ms 15 ms 16 ms
11 nth-bb-b-ae0-0.inet.ntl.com (62.253.185.118) 16 ms 15 ms 16 ms
12 nott-t2core-b-pos31.inet.ntl.com (62.253.185.38) 17 ms 17 ms 17 ms
13 nott-cache-1.server.ntli.net (62.254.0.12) 17 ms 23 ms 17 ms

guildford

1 216-196-110-1.ams.giganews.com (216.196.110.1) 278 ms 1 ms 11 ms
2 adm-b2-geth3-2.telia.net (213.248.73.1) 1 ms 0 ms 0 ms
3 adm-bb2-pos0-0-0.telia.net (213.248.64.189) 0 ms 1 ms 0 ms
4 ldn-bb2-pos7-2-0.telia.net (213.248.65.157) 9 ms 8 ms 10 ms
5 ldn-b2-pos12-3.telia.net (213.248.64.74) 8 ms 9 ms 10 ms
6 * * ntl-111210-ldn-b2.c.telia.net (213.248.100.38) 139 ms
7 bre-bb-b-as0-0.inet.ntl.com (62.253.188.122) 23 ms 23 ms 24 ms
8 bre-bb-a-ae0-0.inet.ntl.com (213.105.172.86) 24 ms 24 ms 24 ms
9 gfd-bb-b-so-700-0.inet.ntl.com (213.105.172.150) 19 ms 18 ms 18 ms
10 glfd-t2core-b-pos31.inet.ntl.com (62.253.185.30) 18 ms 19 ms 19 ms
11 glfd-cache-3.server.ntli.net (62.252.0.6) 19 ms 17 ms 16 ms

crazy stuff all static routing I believe.