Slow download

Sun Jul 03, 2011 11:31 am

Hello, i wanted to play invasion but download speed from server is very slow. It's below 1kbps and I'm downloading the stuff 2nd day and get already bored. Is it possible to download files faster?

Sun Jul 03, 2011 11:34 am

I can confirm this. The FTP (or whatever download type it is) is pretty much non-functional, I had intermittent connection and timed out repeatedly before I gave up. Thought it was another one of my internet problems.

Sun Jul 03, 2011 12:33 pm

Cant see any issues with the redirect

Files download at the normal speed for me

Sun Jul 03, 2011 12:47 pm

Still, I doubt it's a coincidence that more than one person is having the same problem unless we're both in Europe maybe? It could be a more serious issue, like a wire across the pond being f***ed. It might fix itself...or be fixed... we can hope. I want to mash! :(

Mon Jul 04, 2011 5:21 am

I am from Europe too. But there is a problem. I have to download larger file called "dinotopia" and when it's around 50% map ends and error message pops up. After that I have to start download it from server again.. Maybe someone could upload files?

Mon Jul 04, 2011 6:37 am

Yeah, that's not really a problem with the file. The server is having trouble putting files through to us and when it disconnects for long enough without timing out, it resets the current file.

The problem is just that the file is way too big to be downloaded in between these blips which reset the download. So basically, we won't get on the server until the problem is fixed unless someone can provide us with a mirror of all the files, and instructions on how to use it.

Mon Jul 04, 2011 10:39 am

Do a trace route to clandw.com if you could.

Mon Jul 04, 2011 10:50 am

I was thinking the same thing. Am I right in saying that Death Warrant has had routing issues in the past? I'll run it in a few minutes when I get on my PC.

Code: Select all

Tracing route to clandw.com [74.208.27.214]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  (my router)
  2    26 ms    26 ms    27 ms  (BT exchange)
  3    26 ms    27 ms    25 ms  217.32.85.161
  4    32 ms    31 ms    31 ms  213.1.67.10
  5    31 ms    31 ms    31 ms  213.1.79.10
  6    31 ms    31 ms    31 ms  87.237.20.244
  7    33 ms    35 ms    35 ms  bundle-ether1.lontr1.London.opentransit.net [193
.251.255.101]
  8    75 ms    92 ms    77 ms  te7-7.ccr01.lon01.atlas.cogentco.com [130.117.14
.153]
  9    75 ms    74 ms    74 ms  te4-4.mpd02.lon01.atlas.cogentco.com [130.117.1.
134]
 10   126 ms   127 ms   125 ms  te0-3-0-4.ccr21.bos01.atlas.cogentco.com [154.54
.30.129]
 11   128 ms   127 ms   127 ms  te0-3-0-7.mpd22.ord01.atlas.cogentco.com [154.54
.7.81]
 12   140 ms   139 ms   140 ms  te0-1-0-2.mpd22.mci01.atlas.cogentco.com [154.54
.3.202]
 13   139 ms   139 ms   139 ms  te4-4.mpd01.mci01.atlas.cogentco.com [154.54.30.
166]
 14   139 ms   139 ms   139 ms  te-1-3.bb-a.ga.mkc.us.oneandone.net [38.104.86.4
2]
 15   139 ms   141 ms   141 ms  te-2-1.bb-d.slr.lxa.us.oneandone.net [74.208.1.6
5]
 16   140 ms   175 ms   139 ms  ae-1.gw-dista-a.slr.lxa.oneandone.net [74.208.1.
105]
 17   141 ms   141 ms   139 ms  vl-987.gw-ps1.slr.lxa.oneandone.net [74.208.1.13
3]
 18   140 ms   139 ms   140 ms  perfora.net [74.208.27.214]

Trace complete.

I see nothing out of the ordinary apart from the fact that the pings when the packet leaves London get pretty damn high. Maybe that's just the nature of the beast with the transatlantic line but it used to be better.

Edit: Trying something else. I pinged the Chicago server IP direct.

Code: Select all

Tracing route to (Chicago's IP censored)
over a maximum of 30 hops:

  1    <1 ms     2 ms    <1 ms  (my router)
  2    27 ms    27 ms    28 ms  (my exchange)
  3    25 ms    26 ms    27 ms  217.32.85.193
  4    32 ms    32 ms    31 ms  213.1.67.10
  5    32 ms    32 ms    32 ms  213.1.79.10
  6    53 ms    31 ms    31 ms  87.237.20.244
  7    32 ms    37 ms    39 ms  bundle-ether1.lontr1.London.opentransit.net [193
.251.255.101]
  8    48 ms    33 ms    34 ms  xe-0-0-0-6.r02.londen03.uk.bb.gin.ntt.net [129.2
50.8.197]
  9    33 ms    33 ms    33 ms  ae-4.r22.londen03.uk.bb.gin.ntt.net [129.250.5.2
4]
 10   132 ms   123 ms   108 ms  as-0.r22.nycmny01.us.bb.gin.ntt.net [129.250.3.2
54]
 11   112 ms   114 ms   125 ms  ae-0.r23.nycmny01.us.bb.gin.ntt.net [129.250.3.7
3]
 12   148 ms   151 ms     *     ae-3.r20.chcgil09.us.bb.gin.ntt.net [129.250.2.4
0]
 13   147 ms   148 ms   152 ms  ae-1.r06.chcgil09.us.bb.gin.ntt.net [129.250.4.1
46]
 14   134 ms   133 ms   128 ms  xe-0-3-0-6.r06.chcgil09.us.ce.gin.ntt.net [128.2
42.179.22]
 15   131 ms   137 ms   137 ms  ip65.208-100-32.static.steadfast.net [208.100.32
.65]
 16   127 ms   133 ms   127 ms  ip74.208-100-32.static.steadfast.net [208.100.32
.74]
 17   134 ms   136 ms   130 ms  ip220.208-100-49.static.steadfast.net [208.100.4
9.220]

Trace complete.

Again, seems pretty clean. However, there was one timeout (*) but it might have just been a blip?

Edit 2: Another for clandw.org.

Code: Select all

Tracing route to clandw.org [174.36.175.244]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2    31 ms    38 ms    30 ms  213.123.106.186
  3    25 ms    25 ms    27 ms  217.32.85.193
  4    32 ms    31 ms    31 ms  213.1.67.10
  5    35 ms    34 ms    40 ms  213.1.79.10
  6    32 ms    31 ms    31 ms  87.237.20.244
  7    35 ms    35 ms    34 ms  bundle-ether1.lontr1.London.opentransit.net [193
.251.255.101]
  8    33 ms    33 ms    36 ms  81.52.179.254
  9   105 ms   105 ms   106 ms  bbr01.eq01.wdc02.networklayer.com [207.138.112.2
42]
 10   104 ms   105 ms   106 ms  po99.bbr02.eq01.wdc02.networklayer.com [173.192.
18.195]
 11   124 ms   137 ms   124 ms  po3.bbr02.eq01.chi01.networklayer.com [173.192.1
8.155]
 12   150 ms   149 ms   149 ms  ae1.bbr02.cf01.den01.networklayer.com [173.192.1
8.131]
 13   156 ms   155 ms   156 ms  ae7.bbr01.cf01.den01.networklayer.com [173.192.1
8.168]
 14   188 ms   187 ms   187 ms  po4.bbr01.wb01.sea01.networklayer.com [173.192.1
8.144]
 15   191 ms   191 ms   189 ms  po2.cer01.sr01.sea01.networklayer.com [173.192.1
8.199]
 16   190 ms   183 ms   204 ms  po1.fcr01.sr01.sea01.networklayer.com [67.228.11
8.134]
 17   188 ms   187 ms   188 ms  light.imageleet.net [174.36.175.244]

Trace complete.

They all seem to tell me absolutely nothing. Morsad's showed a completely different story.

Mon Jul 04, 2011 12:11 pm

This is mine for clandw.org

Code: Select all

  1   185 ms     2 ms    11 ms  idg89.internetdsl.tpnet.pl [79.189.84.89]
  2    13 ms    12 ms    12 ms  lub-ru2.idsl.tpnet.pl [213.25.2.109]
  3     *        *        *     Timeout.
  4     *        *        *     Timeout.
  5     *        *        *     Timeout.
  6    33 ms    32 ms    32 ms  hbg-bb2-link.telia.net [80.91.249.202]
  7    46 ms    50 ms    46 ms  ldn-bb2-link.telia.net [80.91.250.151]
  8   122 ms   122 ms   122 ms  ash-bb1-link.telia.net [80.91.246.66]
  9   122 ms   122 ms   122 ms  te2-6.bbr01.eq01.wdc02.networklayer.com [213.248
.78.130]
 10   123 ms   136 ms   152 ms  po99.bbr02.eq01.wdc02.networklayer.com [173.192.
18.195]
 11   139 ms   139 ms   138 ms  po3.bbr02.eq01.chi01.networklayer.com [173.192.1
8.155]
 12   166 ms   167 ms   168 ms  ae1.bbr02.cf01.den01.networklayer.com [173.192.1
8.131]
 13   164 ms   165 ms   165 ms  ae7.bbr01.cf01.den01.networklayer.com [173.192.1
8.168]
 14   203 ms   202 ms   203 ms  po4.bbr01.wb01.sea01.networklayer.com [173.192.1
8.144]
 15   203 ms   203 ms   202 ms  po2.cer01.sr01.sea01.networklayer.com [173.192.1
8.199]
 16   198 ms   198 ms   198 ms  po1.fcr01.sr01.sea01.networklayer.com [67.228.11
8.134]
 17   199 ms   203 ms   198 ms  light.imageleet.net [174.36.175.244]

Mon Jul 04, 2011 2:26 pm

shits my bad ping this ip .

74.86.13.149