Tracing route to force.imageleet.com [74.86.13.149]
over a maximum of 30 hops:
1 <1 ms 8 ms <1 ms 192.168.0.1
2 33 ms 31 ms 32 ms 213.123.106.186
3 27 ms 25 ms 25 ms 213.123.106.161
4 32 ms 37 ms 34 ms 213.1.67.14
5 32 ms 34 ms 30 ms 213.1.67.252
6 32 ms 31 ms 31 ms 213.1.79.10
7 35 ms 35 ms 34 ms 87.237.20.244
8 43 ms 38 ms 43 ms bundle-ether1.lontr1.London.opentransit.net [193
.251.255.101]
9 36 ms 39 ms 40 ms 81.52.179.254
10 238 ms 277 ms 106 ms bbr01.eq01.wdc02.networklayer.com [207.138.112.2
42]
11 125 ms 119 ms 127 ms ae0.bbr01.tl01.atl01.networklayer.com [173.192.1
8.153]
12 166 ms 170 ms 166 ms po7.bbr02.eq01.dal01.networklayer.com [173.192.1
8.134]
13 166 ms 166 ms 165 ms po6.dar02.sr01.dal01.networklayer.com [173.192.1
8.213]
14 175 ms * 172 ms po2.fcr02.sr04.dal01.networklayer.com [66.228.11
8.182]
15 167 ms 171 ms 167 ms force.imageleet.com [74.86.13.149]
Trace complete.
bbr01.eq01.wdc02.networklayer.com [207.138.112.242] could be the problem. The pings there were OTT.
1 20 ms 1 ms 1 ms idg89.internetdsl.tpnet.pl [79.189.84.89]
2 12 ms 11 ms 12 ms lub-ru2.idsl.tpnet.pl [213.25.2.109]
3 * * * Timeout.
4 * * * Timeout.
5 * * * Timeout.
6 * * * Timeout.
7 46 ms 46 ms 46 ms ldn-bb1-link.telia.net [80.91.254.5]
8 122 ms 123 ms 121 ms ash-bb1-link.telia.net [80.91.246.68]
9 122 ms 122 ms 123 ms te2-6.bbr01.eq01.wdc02.networklayer.com [213.248
.78.130]
10 137 ms 137 ms * ae0.bbr01.tl01.atl01.networklayer.com [173.192.1
8.153]
11 182 ms 181 ms 182 ms po7.bbr02.eq01.dal01.networklayer.com [173.192.1
8.134]
12 187 ms 186 ms 186 ms po6.dar02.sr01.dal01.networklayer.com [173.192.1
8.213]
13 183 ms * 181 ms po2.fcr02.sr04.dal01.networklayer.com [66.228.11
8.182]
14 183 ms 187 ms 187 ms force.imageleet.com [74.86.13.149]
Maby you're having routing issue with the ftp redirect server. If you cant reach the redirect, the files will be downloaded directly from the MM server at a very slow speed.
I got the reflex of the fly, now catch me if you can!
Yes, routing issues have this tendency to fix themselves, internet signal routing is so unpredictable and random that there is no telling when your signal will be good or bad. I remember one week during 2009 my routing path changed and I was having packet loss like u can't believe, then after 1 weeks it just went back to normal.
I got the reflex of the fly, now catch me if you can!
Hops 3 to 6 timeout? Did some quick googling and I don't get that. Hops 1 or 2 would be normal but that just looks like a problem to me , although I may not be the man to ask
1 20 ms 1 ms 1 ms idg89.internetdsl.tpnet.pl [79.189.84.89]
2 12 ms 11 ms 12 ms lub-ru2.idsl.tpnet.pl [213.25.2.109]
3 * * * Timeout.
4 * * * Timeout.
5 * * * Timeout.
6 * * * Timeout.
7 46 ms 46 ms 46 ms ldn-bb1-link.telia.net [80.91.254.5]
8 122 ms 123 ms 121 ms ash-bb1-link.telia.net [80.91.246.68]
9 122 ms 122 ms 123 ms te2-6.bbr01.eq01.wdc02.networklayer.com [213.248
.78.130]
10 137 ms 137 ms * ae0.bbr01.tl01.atl01.networklayer.com [173.192.1
8.153]
11 182 ms 181 ms 182 ms po7.bbr02.eq01.dal01.networklayer.com [173.192.1
8.134]
12 187 ms 186 ms 186 ms po6.dar02.sr01.dal01.networklayer.com [173.192.1
8.213]
13 183 ms * 181 ms po2.fcr02.sr04.dal01.networklayer.com [66.228.11
8.182]
14 183 ms 187 ms 187 ms force.imageleet.com [74.86.13.149]