From: sxc@cs.adelaide.edu.au (Stephen Crawley)
Newsgroups: aus.aarnet
Subject: Re: route: Australia to Germany
Date: 14 Oct 92 12:13:50 GMT
Organization: Dept. of Comp. Sci., University of Adelaide
NNTP-Posting-Host: jomsborg.cs.adelaide.edu.au

In article <1bd1flINNaan@manuel.anu.edu.au>, markus@arp.anu.edu.au (Dr Markus Buchhorn) writes:
|> 
|> I recently went jogging round the net for some sun patch files. I found
|> an excellent site in Germany. Unfortunately it had an abysmal transfer
|> rate (0.3kb/s!). Now, other sites in Europe aren't as bad, so I did
|> a 'traceroute' and found to my surprise that a lot of the problem
|> is in the U.S. - it spends a lot of its time crossing the U.S., but most
|> of that time is spent in one building (I suppose it is one building) - note
|> hops 8 thru 15. Now my question: Can This Be Fixed ? It could double the xfer
|> rate (although the last hop looks quite sick as well..)
|> 
|> Markus
|> 
|> -----------------------------------------------------------------------------
|> markus@romeo% traceroute ftp.informatik.uni-hamburg.de
|> traceroute to rzsun2.informatik.uni-hamburg.de (134.100.4.42), 30 hops max, 40 byte packets
|>  1  cschub (150.203.5.1)  0 ms  0 ms  0 ms
|>  2  actgw (150.203.1.5)  0 ms  0 ms  0 ms
|>  3  national.gw.au (139.130.188.1)  10 ms  10 ms  10 ms
|>  4  usa.gw.au (139.130.4.5)  10 ms  10 ms  10 ms
|>  5  132.160.240.1 (132.160.240.1)  610 ms  590 ms  580 ms
|>  6  ARC1.NSN.NASA.GOV (192.100.12.1)  580 ms  610 ms  600 ms
|>  7  192.52.195.253 (192.52.195.253)  580 ms  610 ms  660 ms
|>  8  t3-2.cnss9.t3.nsf.net (140.222.9.3)  620 ms  590 ms  580 ms
|>  9  t3-3.cnss8.t3.nsf.net (140.222.8.4)  580 ms  600 ms  640 ms
|> 10  t3-0.cnss24.t3.nsf.net (140.222.24.1)  670 ms  650 ms  630 ms
|> 11  t3-0.cnss40.t3.nsf.net (140.222.40.1)  660 ms  660 ms  630 ms
|> 12  t3-1.cnss32.t3.nsf.net (140.222.32.2)  670 ms  730 ms  650 ms
|> 13  t3-1.cnss56.t3.nsf.net (140.222.56.2)  780 ms  650 ms  750 ms
|> 14  t3-0.cnss58.t3.nsf.net (140.222.58.1)  660 ms  700 ms  720 ms
|> 15  t3-0.enss136.t3.nsf.net (140.222.136.1)  670 ms  700 ms  650 ms
|> 16  College-Park.MD.ALTER.NET (192.80.214.249)  660 ms  650 ms  660 ms
|> 17   (137.39.11.1)  780 ms  700 ms  670 ms
|> 18  Amsterdam.NL.EU.NET (134.222.5.1)  1080 ms  770 ms  880 ms
|> 19  Dortmund.DE.EU.NET (134.222.1.2)  890 ms  1070 ms  900 ms
|> 20  wingate.Dortmund.DE.EU.net (139.4.10.3)  1080 ms  860 ms  960 ms
|> 21  * * *
|> 22  * rzsun2.informatik.uni-hamburg.de (134.100.4.42)  8380 ms *
|> --------------------------------------------------------------------------------


You are misinterpretting the traceroute output.  

Those *.*.t3.nsf.net are not necessarily in one building.  Indeed I suspect
they are not even in the same state.  It looks like the main NSF net backbone
to me.  Anyhow, the important thing is it seems to be taking less than
100 ms to traverse them.  That's quite reasonable, and won't contribute
much to the delays.

The real killer is the delay between wingat.Dortmund.DE.EU.net and
rzsun2.informatik.uni-hamburg.de.  The likely cause is severe congestion
in the German part of the Internet.  I understand that this is a common
problem over there.

Your best bet would be to try to FTP at 3am German time :-)

--Steve

 
Xref: sparky aus.aarnet:993 comp.org.eff.talk:6401