Can I get a speed test
on this win2k box I just got from
fastservers.net please thanks

216.218.211.103

Tracing route to 216.218.211.103 over a maximum of 30 hops

1 11 ms 10 ms <10 ms 10.47.96.1
2 <10 ms 30 ms 11 ms 24-29-100-41.nyc.rr.com [24.29.100.41]
3 40 ms 10 ms 10 ms pos2-0-nycmnyr-rtr1.nyc.rr.com [24.29.100.90]
4 <10 ms 51 ms 10 ms pos3-0-nycmnya-rtr1.nyc.rr.com [24.29.97.29]
5 <10 ms 20 ms 40 ms pop1-nye-P0-2.atdn.net [66.185.137.193]
6 <10 ms 10 ms 10 ms HE.atdn.net [66.185.149.198]
7 30 ms 40 ms 40 ms 216.218.255.249
8 80 ms 90 ms 90 ms 10.201.10.1
9 * 80 ms * gige-g0-0.gsr12008.fmt.he.net [216.218.130.6]
10 100 ms 90 ms 100 ms 64.71.131.174
11 171 ms 140 ms 120 ms 216.218.211.103

C:\>ping 216.218.211.103

Pinging 216.218.211.103 with 32 bytes of data:

Reply from 216.218.211.103: bytes=32 time=110ms TTL=115
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 216.218.211.103:
Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),
Approximate round trip times in milli-seconds:
Minimum = 110ms, Maximum = 110ms, Average = 27ms

C:\>ping 216.218.211.103

Pinging 216.218.211.103 with 32 bytes of data:

Request timed out.
Reply from 216.218.211.103: bytes=32 time=90ms TTL=115
Reply from 216.218.211.103: bytes=32 time=90ms TTL=115
Reply from 216.218.211.103: bytes=32 time=90ms TTL=115

Ping statistics for 216.218.211.103:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 90ms, Maximum = 90ms, Average = 67ms


Not good....but it's been posted that HE is having some troubles today, so it's most likely caused by that.

Confirmed-

Issues are rampant at HE / MAE West as a whole right now, I've been told. Things are nearing a conclusion, I'm told from the network admin at the datacenter @ HE. As of right now, I'm not losing any packets, though it appeared things had stabilized a few times earlier :cool:


At any rate, progress is being made and things should return to normal very shortly. This was an extremely rare occurrence- this is coming from 6+ years of experience at that datacenter.

Hopefully future stability and efficiency will back me up. :D

can someone do these speed test now please, i think fastservers.net is back again....

Pings arent really a good measure of speed, maybe put a file up for us to download so we can give you a more accurate measure of speed?

That said,

ping 216.218.211.103

Pinging 216.218.211.103 with 32 bytes of data:

Reply from 216.218.211.103: bytes=32 time=12ms TTL=121
Reply from 216.218.211.103: bytes=32 time=13ms TTL=121
Reply from 216.218.211.103: bytes=32 time=9ms TTL=121
Reply from 216.218.211.103: bytes=32 time=12ms TTL=121

Ping statistics for 216.218.211.103:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)



Ah, the joys of being 4 hops away from he.net :D

Can't wait till it's time for my next server, I'm going to give fastservers a try.

I agree. Although pings and traceroute are good measures of how well a box is connected, in order to test the true speed of the connections, you will need a test file somewhere on the network. That way, you will get an accurate measure of the throughput. Another good way to test the pings and traceroute yourself is to use a looking glass like www.traceroute.org.

Pinging 216.218.211.103 with 32 bytes of data:

Reply from 216.218.211.103: bytes=32 time=187ms TTL=113
Reply from 216.218.211.103: bytes=32 time=195ms TTL=113
Reply from 216.218.211.103: bytes=32 time=187ms TTL=113
Reply from 216.218.211.103: bytes=32 time=188ms TTL=113

Ping statistics for 216.218.211.103:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 187ms, Maximum = 195ms, Average = 189ms

From a 1Mbit line in the UK. Generally I get between 90ms - 150ms to US based sites.

I would tend to agree- Western Europe is where routes to our network @ MAE West (San Jose) tend to be weakest. Though many are still more than happy with it.

There are some speed analysis details (especially related to throughput), mentioned in the forum if you do a search.
specifically here:
http://webhostingtalk.com/showthread.php?s=&threadid=59306&perpage=15&highlight=fastservers&pagenumber=5

I'm not attempting to get this thread locked for morphing into an ad- just attempting to provide some examples of the network.
:D

So be careful, and keep the questions geared towards the purpose of the thread or Chicken will chomp us.

Pinging 216.218.211.103 with 32 bytes of data:

Reply from 216.218.211.103: bytes=32 time=27ms TTL=115
Reply from 216.218.211.103: bytes=32 time=28ms TTL=115
Reply from 216.218.211.103: bytes=32 time=27ms TTL=115
Reply from 216.218.211.103: bytes=32 time=27ms TTL=115
Reply from 216.218.211.103: bytes=32 time=14ms TTL=115
Reply from 216.218.211.103: bytes=32 time=28ms TTL=115
Reply from 216.218.211.103: bytes=32 time=27ms TTL=115
Reply from 216.218.211.103: bytes=32 time=28ms TTL=115

Very stable pings.

PING 216.218.211.103 (216.218.211.103) from 64.246.16.91 : 56(84) bytes of data.
64 bytes from 216.218.211.103: icmp_seq=0 ttl=119 time=48.918 msec
64 bytes from 216.218.211.103: icmp_seq=1 ttl=119 time=48.994 msec
64 bytes from 216.218.211.103: icmp_seq=2 ttl=119 time=48.652 msec
64 bytes from 216.218.211.103: icmp_seq=3 ttl=119 time=49.137 msec
64 bytes from 216.218.211.103: icmp_seq=4 ttl=119 time=49.328 msec
64 bytes from 216.218.211.103: icmp_seq=5 ttl=119 time=48.667 msec
64 bytes from 216.218.211.103: icmp_seq=6 ttl=119 time=49.050 msec
64 bytes from 216.218.211.103: icmp_seq=7 ttl=119 time=49.710 msec

--- 216.218.211.103 ping statistics ---
8 packets transmitted, 8 packets received, 0% packet loss
round-trip min/avg/max/mdev = 48.652/49.057/49.710/0.325 ms

funny how people keeps giving ping result for a speed test. A T1 may still give you the same ping time as an OC12. As some have already mentioned, to do speed test, then try downloading some Mega bytes of file from a server inside fastserver.net network.

Ping does not tell anything in this case. Please ... no more ping results.

Tracing route to 216.218.211.103 over a maximum of 30 hops



1 <10 ms <10 ms <10 ms Cisco [192.168.1.1]
2 20 ms 10 ms 20 ms fe2-0.cr0.vlb.worldonline.dk [213.237.5.49]
3 20 ms 20 ms 20 ms cr0.boet.worldonline.dk [213.237.127.6]
4 20 ms 30 ms 40 ms cr0.hvi.worldonline.dk [213.237.127.26]
5 71 ms 30 ms 30 ms cr0.vby.worldonline.dk [213.237.127.60]
6 20 ms 100 ms 100 ms cr0.pbv.worldonline.dk [213.237.127.254]
7 20 ms 40 ms 60 ms so-4-2-0.cph10.ip.tiscali.net [213.200.73.5]
8 40 ms 100 ms 80 ms so-5-0-0.ams20.ip.tiscali.net [213.200.81.41]
9 40 ms 40 ms 60 ms so-2-0-0.ams10.ip.tiscali.net [213.200.81.54]
10 70 ms 40 ms 50 ms so-2-0-0.lon12.ip.tiscali.net [213.200.81.149]
11 60 ms 70 ms 50 ms 213.200.77.5
12 50 ms 80 ms 60 ms so-4-1-0.cr2.lhr3.uk.mfnx.net [208.185.156.2]
13 60 ms 51 ms 50 ms so-0-0-0.cr1.lhr3.uk.mfnx.net [208.184.231.145]
14 130 ms 121 ms 130 ms so-7-0-0.cr1.dca2.us.mfnx.net [64.125.31.186]
15 200 ms 211 ms 200 ms so-3-0-0.mpr3.sjc2.us.mfnx.net [208.184.233.133]
16 180 ms 201 ms 200 ms pos5-0.mpr1.pao1.us.mfnx.net [208.184.233.142]
17 191 ms 190 ms 190 ms 209.249.24.136.he.net [209.249.24.136]
18 191 ms 200 ms 190 ms gige-g0-0.gsr12008.fmt.he.net [216.218.130.6]
19 190 ms 190 ms 200 ms 64.71.131.174
20 190 ms 220 ms 210 ms 216.218.211.103

From Denmark

Enjoy!

3mb download --> http://65.19.139.18/test/http.03m.sav
10mb download --> http://65.19.139.18/test/http.10m.sav
50mb download --> http://65.19.139.18/test/http.50m.sav
139mb download --> http://65.19.139.18/test/http.139m.sav

07:45:53 (566.23 KB/s) - `http.139m.sav' saved [146043732/146043732] from nocster.com (http://www.nocster.com)

139mb download --> http://65.19.139.18/test/http.139m.sav

78KB/sec with a 1MBit ADSL connection from Denmark

John

100%[====================================>] 52,428,800 7.26M/s ETA 00:00

11:11:23 (7.26 MB/s) - `http.50m.sav' saved [52428800/52428800]

between 7 and 8.5 Mbps from my server in the San Francisco Bay Area

I will think your server is inside HE too, inside the same data center as fastserver's. So it's internal transfer probably just between switches (if not through the same switch) and hence you are getting that high number.

*****
Ping wird ausgeführt für 216.218.211.103 mit 32 Bytes Daten:

Antwort von 216.218.211.103: Bytes=32 Zeit=172ms TTL=111
Antwort von 216.218.211.103: Bytes=32 Zeit=172ms TTL=111
Antwort von 216.218.211.103: Bytes=32 Zeit=172ms TTL=111
Antwort von 216.218.211.103: Bytes=32 Zeit=172ms TTL=111

Ping-Statistik für 216.218.211.103:
Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0 (0% Verlust),
Ca. Zeitangaben in Millisek.:
Minimum = 172ms, Maximum = 172ms, Mittelwert = 172ms
*****
Routenverfolgung zu 216.218.211.103 über maximal 30 Abschnitte

1 <10 ms <10 ms <10 ms 192.168.1.1
2 <10 ms 15 ms 16 ms 212.53.104.xxx
3 <10 ms 15 ms 16 ms ec-zrh-bor01.net.econophone.ch [212.53.96.xxx]
4 <10 ms 16 ms 15 ms Loopback0.GW2.ZUR4.Alter.Net [146.188.0.68]
5 16 ms <10 ms 16 ms 422.at-2-0-0.XR2.ZUR4.Alter.Net [146.188.9.225]

6 <10 ms 16 ms 15 ms so-1-0-0.TR1.ZUR3.Alter.Net [146.188.3.77]
7 94 ms 94 ms 109 ms so-4-0-0.IR1.NYC12.Alter.Net [146.188.3.201]
8 94 ms 94 ms 109 ms 0.so-1-0-0.IL1.NYC9.ALTER.NET [152.63.23.61]
9 93 ms 94 ms 109 ms 0.so-3-0-0.TL1.NYC9.ALTER.NET [152.63.9.246]
10 93 ms 110 ms 94 ms 0.so-2-1-0.XL1.NYC8.ALTER.NET [152.63.1.41]
11 94 ms 109 ms 94 ms 0.so-3-0-0.XR1.NYC8.ALTER.NET [152.63.19.30]
12 94 ms 93 ms 110 ms 183.ATM4-0.BR1.NYC8.ALTER.NET [152.63.23.73]
13 94 ms 110 ms 93 ms 200.atm6-0.pr1.lga2.us.mfnx.net [208.184.231.245
]
14 94 ms 109 ms 94 ms so-2-2-0.cr2.lga2.us.mfnx.net [216.200.127.169]

15 94 ms 109 ms 94 ms so-0-0-0.cr2.lga1.us.mfnx.net [208.184.232.197]

16 94 ms 110 ms 109 ms so-1-0-0.cr2.iad1.us.mfnx.net [208.184.233.65]
17 94 ms 109 ms 110 ms pos8-0.mpr1.iad1.us.mfnx.net [208.185.0.145]
18 156 ms 172 ms 172 ms so-6-1-0.mpr4.sjc2.us.mfnx.net [216.200.127.26]

19 172 ms 172 ms 172 ms pos6-0.mpr2.pao1.us.mfnx.net [208.185.175.162]
20 172 ms 157 ms 187 ms 209.249.24.136.he.net [209.249.24.136]
21 172 ms 172 ms 171 ms gige-g0-0.gsr12008.fmt.he.net [216.218.130.6]
22 172 ms 172 ms 172 ms 64.71.131.174
23 172 ms 172 ms 171 ms 216.218.211.103

Ablaufverfolgung beendet.
*****
From a aDSL-Line (2MBit down/376KBit up) in Switzerland who uses uunet.

12:49:10 (273.31 KB/s) - `http.03m.sav' saved [2908160/2908160] (39ms ping) from telus 8mbps down/1mbps up dsl... bloody fast if u ask me... ! :D

14:38:00 (440.24 KB/s) - `http.03m.sav' saved [2908160/2908160] (82ms ping) from fdcservers

Originally posted by ap_surge
Enjoy!

3mb download --> http://65.19.139.18/test/http.03m.sav
10mb download --> http://65.19.139.18/test/http.10m.sav
50mb download --> http://65.19.139.18/test/http.50m.sav
139mb download --> http://65.19.139.18/test/http.139m.sav

Atrivo in CA -- cogent
--------
100%[====================================>] 52,428,800 5.45M/s ETA 00:00

13:28:35 (5.45 MB/s) - `http.50m.sav' saved [52428800/52428800]
-------

Webreseller in PA -- Yipes
-------
16:33:32 (495.90 KB/s) - `http.50m.sav' saved [52428800/52428800]