[X] My Assistant

These are quite annoying.

Each download connections are lower than 40 KB/s, and sometimes failed with interrupt.
So I just got broken zip files, and I have to recheck them.

I retried several times, but it doesn't help.

Try a download manager. The zip file you download from the archiver page shall be the same file each time, so a download manager can reasemble the file from pieces (given it's a good download manager and you download the zip to the same place always).

But remember to configure the download manager, if you spam too many connections the archiver will kick you out.

PS: Try to check if the problematic archiver you get (for downloads of different galleries) is always at the same IP.

This post has been edited by blue penguin: Jan 11 2014, 06:18

Try a download manager. The zip file you download from the archiver page shall be the same file each time, so a download manager can reasemble the file from pieces (given it's a good download manager and you download the zip to the same place always).

But remember to configure the download manager, if you spam too many connections the archiver will kick you out.

PS: Try to check if the problematic archiver you get (for downloads of different galleries) is always at the same IP.

the slow archive server is 95.211.199.136.

I'm trying use mipony to handling the downloads, and I have a feel that I'm back to 10 years before.
Using download manager to download http files with continuously. (IMG:[invalid] style_emoticons/default/mellow.gif)

Well, good news! The archivers are being replaced this month. The new ones are spinning up as we speak.

Somehow I got a similar Problem but without the interrupt and with other Archiv-Server:

37.48.81.81
37.48.81.88

I have that Problem since around 2-3 Days.

It seams to be a Problem only present by the new Server, because if I donwload something via the old ones (eg. 95.211.209.53) I get rates which are normal for my Connection. (between 600 KB/s and 1.5 MB/s for a single Archive)

As long as it's not interrupting, it shouldn't really be a problem. You can run several connections in parallel if speed is an issue.

Servers will invariably perform differently for different people, as it depends on your ISP's routing. From what I can see in the logs, some get as much as 4-5 MB/s per thread from the new archivers.

I'm having problems with 37.48.81.81
Downloads fail quite often.

What do you mean by fails? A couple of possibilities:

• The download does not start
• The download slows down until it is so slow it does not download anymore
• The downloaded file is corrupted
• ...

Now I download 1 archive with the 3 connections in parallel.

total download speed: 50KB/s (IMG:[invalid] style_emoticons/default/sad.gif)

the archiver is 37.48.81.88.

This post has been edited by f_riz: Jan 19 2014, 05:53

What do you mean by fails? A couple of possibilities:

• The download does not start
• The download slows down until it is so slow it does not download anymore
• The downloaded file is corrupted
• ...

The download starts at normal speed but then at some point the speed slows down until it doesn't download anymore. I can resume the download with a download manager but it's kind of annoying to do that each time it happens.

Well, there's nothing wrong with the archiver...

--2014-01-19 08:39:23-- [37.48.81.88] http://37.48.81.88/100M.bin
Connecting to 37.48.81.88:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 104857600 (100M) [application/octet-stream]
Saving to: “100M.bin”

100%[==================================================================================>] 104,857,600 48.6M/s in 2.1s

2014-01-19 08:39:25 (48.6 MB/s) - “100M.bin” saved [104857600/104857600]

(To a server at a different host.)

In the meantime, I tracked the connection using tracert.
For me it looks like that for the new Archiver one hop more is needed, which is within the "leaseweb.net" network.
What I also realized is that depending on the time the download rate vary drastically and that exactly at that one hop the response times vary widely. (high response time = low download rates)

Perhaps this helps the other to find their problems, at least with the download rate.
For me that means starting a download after a certain time is not recommendable.

Either we (forum people) or Tenboro can only guess at most network peculiarities. Slow or diminishing download speeds are very often caused by routers (actually groups of routers) that enforce some throtling (Or routers that enforce throtling during certain periods of the day). Such routers can be anywhere, but most comonly they're used by client end ISPs.

traceroute was a good diagnosis tool before idiots decided that ICMP is a threat to security and firewalls shall kill it.

I'll say that the best way to test/evaluate what is happening is to have many test points. Try to download from home, some cafeteria with free wifi, the library, using at least two different machines.

traceroute was a good diagnosis tool before idiots decided that ICMP is a threat to security and firewalls shall kill it.

Heh. Among other reasons, that's why traceroute on non-retarded operating systems - that is, pretty much everything except Windows - actually sends UDP packets by default (though ICMP Echo Request is an option).

Of course, they still depend on getting an ICMP Time Exceeded in return.

I'm having a different problem with 37.48.81.81.

Whenever I try to download from that archiver, it just says "You cannot have more than ten simultaneous downloads", but I have no other downloads running atm. Is that actually a ban?

I'm having a different problem with 37.48.81.81.

Whenever I try to download from that archiver, it just says "You cannot have more than ten simultaneous downloads", but I have no other downloads running atm. Is that actually a ban?

Guessing you're on a shared and fluctuating IP, as there's nothing in the log from the one you posted that from.

Now it's another error: "You have clocked too many downloaded bytes on this gallery, effectively downloading it more than five times."

Not quite sure what that means. I tried and failed to download it five times? That's a possibility, even with a download manager, the download process often just slow to a halt for no reason, presumably interrupted.

If this "shared and fluctuating IP" is the cause, any solutions? (Switching ISP is not an option.) And how do I download the archive when the above mentioned error appears?

BTW I'm also experiencing this "Archive Downloads are slow and failed eventually" problem.

This post has been edited by Senkousha: Jan 22 2014, 17:34

Chalk up another one having issues 37.48.81.88
Current download speeds: 27Kbps..

I haven't had any fail yet but the current speed is ridiculous for a single archive.

My Personal Trace Route
Tracing route to celestia.is.best.pony [37.48.81.88]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 8 ms 8 ms 8 ms 96.120.40.177
3 12 ms 11 ms 11 ms te-8-3-ur03.deleted.comcast.net [ip delete]
4 23 ms 9 ms 10 ms te-9-4-ur02.deleted..comcast.net [ip delete]
5 8 ms 11 ms 10 ms te-8-1-ur02.deleted..comcast.net [ip delete]
6 32 ms 11 ms 20 ms ip delete
7 27 ms 27 ms 27 ms he-3-3-0-0-cr01.ashburn.va.ibone.comcast.net [ip delete]
8 52 ms 46 ms 44 ms 23.30.207.94
9 123 ms 122 ms 125 ms vlan52.ebr2.Washington12.Level3.net [4.69.146.222]
10 131 ms 131 ms 125 ms 4.69.148.49
11 123 ms 124 ms 123 ms ae-43-43.ebr2.London1.Level3.net [4.69.137.73]
12 123 ms 124 ms 124 ms ae-48-48.ebr2.Amsterdam1.Level3.net [4.69.143.81]
13 123 ms 121 ms 124 ms ae-58-223.csw2.Amsterdam1.Level3.net [4.69.153.210]
14 173 ms 140 ms 124 ms ae-2-52.edge3.Amsterdam1.Level3.net [4.69.139.169]
15 164 ms 160 ms 159 ms FIBERRING-B.edge3.Amsterdam1.Level3.net [212.72.33.218]
16 160 ms 161 ms 157 ms 5.79.79.241
17 159 ms 157 ms 165 ms celestia.is.best.pony [37.48.81.88]

Using an Online Trace Route ---http://tracert.com
1: s6.hostlocal.com (207.158.52.56) 0.110ms pmtu 1500
1: 207.158.52.125 (207.158.52.125) 0.529ms
1: 207.158.52.125 (207.158.52.125) 0.487ms
2: vlan127.car1.SanDiego1.Level3.net (4.79.33.229) 7.852ms
3: ae-11-11.car2.SanDiego1.Level3.net (4.69.133.210) 143.620ms asymm 27
4: ae-4-4.ebr2.Dallas1.Level3.net (4.69.133.214) 143.156ms asymm 17
5: ae-91-91.csw4.Dallas1.Level3.net (4.69.151.161) 142.362ms asymm 17
6: ae-72-72.ebr2.Dallas1.Level3.net (4.69.151.142) 142.117ms asymm 17
7: ae-3-3.ebr2.NewYork1.Level3.net (4.69.137.122) 140.953ms asymm 15
8: ae-82-82.csw3.NewYork1.Level3.net (4.69.148.42) 140.827ms asymm 15
9: ae-81-81.ebr1.NewYork1.Level3.net (4.69.134.73) 141.973ms asymm 17
10: ae-1-100.ebr2.Washington12.Level3.net (4.69.143.214) 142.761ms asymm 17
11: ae-46-46.ebr2.Amsterdam1.Level3.net (4.69.143.73) 140.845ms asymm 15
12: ae-44-44.ebr2.London1.Level3.net (4.69.137.77) 143.715ms asymm 17
13: ae-2-52.edge3.Amsterdam1.Level3.net (4.69.139.169) 142.391ms asymm 15
14: ae-59-224.csw2.Amsterdam1.Level3.net (4.69.153.214) 142.607ms
15: ae-2-52.edge3.Amsterdam1.Level3.net (4.69.139.169) 144.539ms
16: FIBERRING-B.edge3.Amsterdam1.Level3.net (212.72.33.218) 144.207ms asymm 15
17: celestia.is.best.pony (37.48.81.88) 146.658ms !H
Resume: pmtu 1500

This post has been edited by Grey Kitsune: Jan 23 2014, 06:06

I am having the same problem (<50k download speeds when using the new archivers). It may be network routing (traceroute is different enough that it's hard to pin down where the throttling server is) but 20-30 minutes for a mid-size file (60-70 MB) and 2-3 hours for large ones is pretty ridiculous.

7 27 ms 27 ms 27 ms he-3-3-0-0-cr01.ashburn.va.ibone.comcast.net [ip delete]
8 52 ms 46 ms 44 ms 23.30.207.94
9 123 ms 122 ms 125 ms vlan52.ebr2.Washington12.Level3.net [4.69.146.222]
10 131 ms 131 ms 125 ms 4.69.148.49
11 123 ms 124 ms 123 ms ae-43-43.ebr2.London1.Level3.net [4.69.137.73]

As comcast takes 10 times longer to route from Ashburn (Virginia yep? I've never been to US) than the main internet routers take to pass the request across the atlantic ocean, then comcast do have serious routing problems.