Some time ago....I questioned the performance of the E5hosting network
which they have with Verio.....simple tests that were run at the time
showed a NOT very impressive performance.
I was asked if I could have a look and see what might cause the lack
in performance. I worked on this for several days....testing and
gathering information.
This lead to:
1 switch problem due to malconfiguration
2 network maintenance outside the Verio network
result:
The switch problem has been solved by Verio after analizing the data
The network maintenance has been completed....without intervenience
so things are back to normal.
E5hosting asked me if I could setup a network challenge. I took
his offer....and we're busy setting that up. So more on that later....
as it will be an ongoing project that will post realtime results to
leading hosting providers on an hourly basis with detailed network health
results.....when this is completed....I'll post the link to that site.
Below are a few simple test results of the network performance as it is
today. Note that these test are done by single tcp connections so they don't
show the max throughput....as that would take multiple connections.
These are just basic test/results that anyone can run and compare to other hosts.
Apart from these you can do a simple download test at:
http://www.e5hosting.com/test.php
I am in no way affiliated to E5hosting....I was looking for an ISP
and tested....afterwards I was asked to help out and so I did.
iperf bandwidth throughput test results
Feel free to run the same test from wherever you are
usage: iperf -c 130.94.75.242
[root@linux11758 src]# iperf -s
------------------------------------------------------------
Server listening on TCP port 5001
TCP window size: 85.3 KByte (default)
------------------------------------------------------------
[ 4] local 130.94.75.242 port 5001 connected with 194.109.21.3 port 33296 (XS4ALL, NL)
[ 4] 0.0-10.1 sec 18.3 MBytes 15.2 Mbits/sec
[ 4] local 130.94.75.242 port 5001 connected with 62.129.133.5 port 33297 (VXS, NL)
[ 4] 0.0-10.0 sec 21.4 MBytes 17.9 Mbits/sec
[ 4] local 130.94.75.242 port 5001 connected with 209.200.28.196 port 33299 (Level 3 NY, USA)
[ 4] 0.0-10.0 sec 21.9 MBytes 18.3 Mbits/sec
Traceroute XS4ALL, NL result
waasdor7@xs2:~/iperf-2.0.2% traceroute servergenius.com
traceroute to servergenius.com (130.94.75.242), 64 hops max, 44 byte packets
1 124.ae0.xr1.d12.xs4all.net (194.109.21.1) 0.343 ms 0.475 ms 0.433 ms
2 0.so-6-0-0.xr1.sara.xs4all.net (194.109.5.2) 0.521 ms 0.597 ms 0.561 ms
3 acr2-ge-3-1-0.Amsterdamamx.savvis.net (208.174.49.133) 0.655 ms 0.745 ms 0.555 ms
4 acr1-ae0.Amsterdamamx.savvis.net (208.174.48.89) 0.902 ms 0.843 ms 0.810 ms
5 bcs1-so-1-2-0.Londonlnx.savvis.net (204.70.193.146) 8.684 ms 8.986 ms 9.303 ms
6 bcs2-so-0-0-0.NewYork.savvis.net (204.70.192.121) 78.991 ms 78.736 ms 78.613 ms
7 dcr3-so-0-1-0.NewYork.savvis.net (204.70.192.201) 78.693 ms dcr3-so-1-1-0.NewYork.savvis.net (204.70.192.209) 78.585 ms dcr3-so-0-1-0.NewYork.savvis.net (204.70.192.201) 78.711 ms
8 p4-3-2-0.r04.nycmny01.us.bb.verio.net (129.250.9.49) 86.750 ms p4-2-1-0.r04.nycmny01.us.bb.verio.net (129.250.9.77) 86.857 ms p4-3-2-0.r04.nycmny01.us.bb.verio.net (129.250.9.49) 86.807 ms
9 p16-1-1-0.r20.nycmny01.us.bb.verio.net (129.250.2.36) 86.907 ms 86.806 ms 78.875 ms
10 p16-7-0-0.r02.stngva01.us.bb.verio.net (129.250.2.167) 88.443 ms 88.463 ms 88.470 ms
11 mg-2.c00.stngva01.us.da.verio.net (129.250.26.202) 87.958 ms 87.945 ms 87.972 ms
12 161.58.157.85 (161.58.157.85) 88.077 ms 88.011 ms 88.115 ms
13 130.94.75.242 (130.94.75.242) 87.991 ms 88.025 ms 87.984 ms
Traceroute VirtualXS, NL result
[root@www /root]# traceroute 130.94.75.242
traceroute to 130.94.75.242 (130.94.75.242), 30 hops max, 38 byte packets
1 HOSTED-BY.VIRTUALXS.COM (62.129.133.126) 0.515 ms 0.384 ms 0.277 ms
2 pos1-0.gsr02.virtualxs.net (62.129.128.2) 0.943 ms 0.774 ms 1.167 ms
3 t2a1-p9-0.nl-ams2.eu.bt.net (166.49.210.1) 1.363 ms 1.351 ms 1.000 ms
4 t2a4-ge7-0.nl-ams2.eu.bt.net (166.49.200.52) 0.903 ms 1.070 ms 1.187 ms
5 r01.amstnl02.nl.bb.verio.net (195.69.144.36) 150.593 ms 1.469 ms 1.629 ms
6 p16-0-3-3.r21.asbnva01.us.bb.verio.net (129.250.5.87) 86.890 ms 87.571 ms 86.703 ms
7 xe-1-3-0.r20.asbnva01.us.bb.verio.net (129.250.2.170) 82.966 ms 82.802 ms 83.105 ms
8 mg-1.c00.stngva01.us.da.verio.net (129.250.28.202) 83.318 ms 83.178 ms 83.212 ms
9 161.58.157.85 (161.58.157.85) 87.275 ms 88.452 ms 83.292 ms
10 130.94.75.242 (130.94.75.242) 83.765 ms 83.251 ms 82.956 ms
Traceroute level3.net
[root@linux11758 src]# traceroute
www.level3.net
traceroute to
www.level3.net (209.245.19.41), 30 hops max, 38 byte packets
1 198.64.149.65 (198.64.149.65) 0.437 ms 0.208 ms 0.236 ms
2 161.58.157.83 (161.58.157.83) 0.359 ms 0.227 ms 0.241 ms
3 xe-1-2-0-3.r20.asbnva01.us.bb.verio.net (129.250.28.206) 0.362 ms 0.340 ms 0.366 ms
4 xe-1-3-0.r21.asbnva01.us.bb.verio.net (129.250.2.171) 0.496 ms 0.475 ms 0.365 ms
5 p16-0.level3.asbnva01.us.bb.verio.net (129.250.9.162) 0.625 ms 0.597 ms 0.616 ms
6 so-2-1-0.bbr2.Washington1.Level3.net (209.244.11.13) 0.993 ms 0.975 ms 0.990 ms
7 as-0-0.bbr2.Denver1.Level3.net (64.159.4.226) 43.463 ms ae-0-0.bbr1.Denver1.Level3.net (64.159.1.113) 43.318 ms as-0-0.bbr2.Denver1.Level3.net (64.159.4.226) 43.691 ms
8 so-6-0.hsa1.Denver1.Level3.net (4.68.112.154) 43.321 ms 4.68.113.54 (4.68.113.54) 43.575 ms so-6-0.hsa1.Denver1.Level3.net (4.68.112.154) 43.697 ms
9 se3-0.public1.Broomfield1.Level3.net (209.245.16.18) 44.570 ms 44.693 ms 44.460 ms
10 se3-0.public1.Broomfield1.Level3.net (209.245.16.18) 44.955 ms !X * *