Need feedback on a network

Customer Support Customer Only Discussion
1

Hi All,

We are in process of evaluating a new network that will provide us greater growth options and has quite good peering with major providers around.
With the change, we wish to be able to serve current customers better and to be able to add new services without worrying about exhausting our current network channels.

To be able to evaluate our options, we would like feedback from you all.

Here is a list of commands for which we need output, and list of files for which we wish to know the download speeds at your end.

Network1:

ping -n 25 64.71.235.167
tracert 64.71.235.167

Download any file of your choice:

47 MB file - http://64.71.235.167/downloads/linux-2.6.25.4.tar.bz2
20 MB file - http://64.71.235.167/downloads/tetex-fonts-2.0.2-22.0.1.EL4.8.i386.rpm
4.8 MB file - http://64.71.235.167/downloads/tora-1.3.14.1-2.i386.rpm
464M file - http://64.71.235.167/downloads/big.tar

Network2:

ping -n 25 64.59.88.66
tracert 64.59.88.66

Download any file of your choice:

47 MB file - http://64.59.88.67/linux-2.6.25.4.tar.bz2
20 MB file - http://64.59.88.67/tetex-fonts-2.0.2-22.0.1.EL4.8.i386.rpm
4.8 MB file - http://64.59.88.67/tora-1.3.14.1-2.i386.rpm
464M file - http://64.59.88.67/big.tar

People with internet connection of 1Mbps or more, may want to try download the “big.tar” one for better test results.

We will need results for both Network1 and Network2.

Thank you!

2

Re: Need feedback for a proposed network

Tanmaya,

all links on 1st one not working :slight_smile:

I just woke up for a quick email check and saw this, I will fix it for you in a couple hours, I think you already left for the day.

2nd is working for me and getting over 650KB/s on it

3

Re: Need feedback for a proposed network

Should be all fine now. Thanks!

4

Re: Need feedback for a proposed network

You are supposed to be off…thanks for fixing :slight_smile:

5

Re: Need feedback for a proposed network

For me, Network 1 is much faster

bigtar I’m getting a speed of around 360ish on Network 1 and about 1/2 of that on Network 2.

Ping times are similar (high 120s) but Network 1 is slightly faster

Location is in Northern Canada (Yukon Territory - about 100 miles from tidewater in Alaska). Connection is ADSL performing at around 3.5Mbps

Microsoft Windows [Version 6.0.6000]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\Users\George Marchewa>tracert 64.71.235.167

Tracing route to smtp1.hr2p.m****here.biz [64.71.235.167]
over a maximum of 30 hops:

1 2 ms <1 ms <1 ms 192.168.1.1
2 8 ms * 7 ms bsn5000.yt.northwestel.ca [199.85.226.218]
3 9 ms 8 ms 8 ms at-111-101.whthyt06.nwtel.org [198.135.216.77]
4 17 ms 18 ms 18 ms 198.235.216.85
5 30 ms 30 ms 31 ms so-201.drt-02.edtnabss.nwtel.org [198.135.216.61
]
6 137 ms 200 ms 199 ms 69.156.254.197
7 34 ms 30 ms 32 ms core1-edmonton_POS1-4.net.bell.ca [206.108.101.1
93]
8 35 ms 33 ms 33 ms core3-calgaryqa_POS10-0.net.bell.ca [64.230.144.
82]
9 79 ms 79 ms 79 ms core3-toronto12_pos2-2_Core.net.bell.ca [64.230.
147.57]
10 87 ms 87 ms 87 ms core3-montrealak_pos8-0-0.net.bell.ca [64.230.14
7.34]
11 95 ms 96 ms 94 ms core1-newyork83_pos_5_0_0.net.bell.ca [64.230.20
7.138]
12 96 ms 96 ms 97 ms bxX5-newyork83_POS9-0-0.net.bell.ca [64.230.187.
42]
13 93 ms 93 ms 93 ms te9-4.mpd01.jfk05.atlas.cogentco.com [154.54.10.
205]
14 93 ms 93 ms 93 ms vl3492.mpd03.jfk02.atlas.cogentco.com [154.54.7.
13]
15 101 ms 111 ms 100 ms te8-3.mpd01.dca01.atlas.cogentco.com [154.54.5.9
8]
16 113 ms 112 ms 117 ms te9-3.ccr01.atl01.atlas.cogentco.com [154.54.24.
10]
17 * 127 ms 128 ms te3-1.ccr01.mia01.atlas.cogentco.com [154.54.24.
162]
18 * 127 ms 126 ms te4-1.ccr01.mia03.atlas.cogentco.com [154.54.25.
14]
19 128 ms 127 ms 127 ms Webhosting_dot_net.demarc.cogentco.com [38.112.7
.230]
20 128 ms 128 ms 127 ms 64.71.225.26
21 494 ms 216 ms 324 ms smtp1.hr2p.m****here.biz [64.71.235.167]

Trace complete.

C:\Users\George Marchewa>tracert 64.59.88.66

Tracing route to 64.59.88.66 over a maximum of 30 hops

1 1 ms <1 ms <1 ms 192.168.1.1
2 8 ms * 8 ms bsn5000.yt.northwestel.ca [199.85.226.218]
3 9 ms 8 ms 8 ms at-111-101.whthyt06.nwtel.org [198.135.216.77]
4 18 ms 18 ms 18 ms t3-033.crt-01.ftnlbcrr.nwtel.org [198.135.216.93
]
5 31 ms 30 ms 34 ms so-201.drt-02.edtnabss.nwtel.org [198.135.216.61
]
6 31 ms 31 ms 31 ms 69.156.254.197
7 31 ms 34 ms 31 ms core1-edmonton_POS1-4.net.bell.ca [206.108.101.1
93]
8 50 ms 47 ms 46 ms core2-vancouver_POS12-0.net.bell.ca [64.230.203.
114]
9 48 ms 49 ms 50 ms core2-seattle_POS12-0.net.bell.ca [206.108.102.2
09]
10 49 ms 50 ms 50 ms bx3-seattle_POS5-0.net.bell.ca [206.108.102.202]

11 50 ms 52 ms 50 ms 64.212.107.53
12 144 ms 140 ms 141 ms te1-1-10G.ar1.MIA2.gblx.net [67.17.108.62]
13 211 ms 291 ms 226 ms ip-204.246.200.2.gblx.net [204.246.200.2]
14 131 ms 130 ms 129 ms 64.59.88.66

Trace complete.

6

Re: Need feedback for a proposed network

wow the reply time on ping of last hop(server) of network1 is quite odd very extreme high, but hop before is not, odd… thanks for the input we will await some more :slight_smile:

7

retrace drops the last hop back to 128 - normal

8

Using big.tar I am getting 751kb/s on Network1 and network2 753kb/s

This is on ATT 6MB DSL.

I will do some traces and pathping(it does trace + quality of ping in one) in a little while, my wifi is playing funny ona ll of the traces and pings giving too many 200ms+ false replies when it is clearly faster(on network1 and 2, it is wifi issue only not any network issue)

9

Hey Guys,

From the UK I am getting very similar ping times (160ms) for both networks.

Network 1 is giving me a download of 360kb/s
Network 2 is giving me a download speed of 330kb/s

Not much in it from the uk, but Net 1 is about 10% quicker on download.

Cheers

10

From eastern Pennsylvania, I got the following:

Network 1 ping: Minimum = 62ms, Maximum = 87ms, Average = 65ms

Network 2 ping: Minimum = 49ms, Maximum = 53ms, Average = 49ms

Network 1 tracert:
1 2 ms 1 ms 1 ms 24.115.55.163.res-cmts.mtp.ptd.net [24.115.55.163]
2 8 ms 8 ms 7 ms 10.42.0.1.res-cmts.mtp.ptd.net [10.42.0.1]
3 8 ms 7 ms 7 ms gateway2-ge2-2-54.str.ptd.net [204.186.5.46]
4 25 ms 25 ms 26 ms sl-st2-pit-2-2.sprintlink.net [144.232.229.45]
5 28 ms 27 ms 28 ms 144.232.13.145
6 29 ms 28 ms 29 ms sl-bb20-msq-2-0.sprintlink.net [144.232.20.74]
7 28 ms 27 ms 28 ms sl-bb21-msq-15-0.sprintlink.net [144.232.9.110]

8 32 ms 33 ms 31 ms sl-bb27-rly-8-0.sprintlink.net [144.232.20.73]
9 33 ms 31 ms 32 ms sl-bb26-rly-13-0.sprintlink.net [144.232.14.181]

10 33 ms 35 ms 34 ms sl-bb20-dc-13-0-0.sprintlink.net [144.232.20.12]

11 60 ms 62 ms 62 ms sl-bb21-mia-2-0-0.sprintlink.net [144.232.9.24]

12 63 ms 61 ms 65 ms sl-st20-mia-1-0.sprintlink.net [144.232.2.197]
13 57 ms 61 ms 62 ms sl-internap-145-0.sprintlink.net [144.223.245.146]
14 206 ms 186 ms 184 ms border5.pc1.bbnet1.mia003.pnap.net [69.25.0.13]

15 62 ms 66 ms 63 ms webhosting-9.border5.mia003.pnap.net [216.52.162.66]
16 63 ms 63 ms 64 ms 64.71.225.26
17 63 ms 64 ms 64 ms smtp1.hr2p.m****here.biz [64.71.235.167]

Network 2 tracert:
1 2 ms 1 ms 1 ms 24.115.55.163.res-cmts.mtp.ptd.net [24.115.55.163]
2 7 ms 7 ms 7 ms 10.42.0.1.res-cmts.mtp.ptd.net [10.42.0.1]
3 8 ms 8 ms 7 ms gateway2-ge2-2-54.str.ptd.net [204.186.5.46]
4 17 ms 33 ms 7 ms gateway-t1-2-str2str2.str.ptd.net [207.44.122.177]
5 13 ms 17 ms 14 ms ge-6-11.car2.Newark1.Level3.net [4.79.190.25]
6 13 ms 16 ms 17 ms ae-31-53.ebr1.Newark1.Level3.net [4.68.99.94]
7 18 ms 18 ms 16 ms ae-1-100.ebr2.Newark1.Level3.net [4.69.132.22]
8 29 ms 19 ms 20 ms ae-4.ebr3.Washington1.Level3.net [4.69.132.101]

9 20 ms 32 ms 19 ms ae-73-73.csw2.Washington1.Level3.net [4.69.134.166]
10 28 ms 32 ms 19 ms ae-71-71.ebr1.Washington1.Level3.net [4.69.134.133]
11 36 ms 36 ms 35 ms ae-2.ebr3.Atlanta2.Level3.net [4.69.132.85]
12 40 ms 35 ms 36 ms ae-72-70.ebr2.Atlanta2.Level3.net [4.69.138.19]

13 61 ms 47 ms 46 ms ae-4-4.car2.Miami1.Level3.net [4.69.133.9]
14 46 ms 45 ms 46 ms ae-24-24.car4.Miami1.Level3.net [4.69.133.26]
15 52 ms 50 ms 51 ms EASY-ONLINE.car4.Miami1.Level3.net [4.71.208.6]

16 50 ms 49 ms 50 ms 64.59.88.66

Download from Network 1 (yesterday) was averaging about 270-275.

Download from Network 2 (today) was averaging about 250.

This is my vacation home, so not the greatest connection. It’s interesting that I’m finding faster speeds on Network 2.

11

It seems that today is not the best day for testing from NZ as I’m getting very inconsistant results with pings and downloads. The only consistant result is that trace route for network 1 never gets further than 64.71.225.26. Downloads were spread over a 4 hr period from 8:30pm on Sunday Evening local time (GMT + 1200)

ADSL Connection: Data Rate Down/Up 4608Kb/768Kb

[COLOR=“Blue”]Network 1
Pings
Time minimum: 264.00 ms
Time average: 298.08 ms
Time maximum: 319.00 ms

Hop Hostname IP Time 1
1 gabrielle.local 192.168.2.32 0.140ms
1 . 192.168.2.1 0.843ms
1 . 192.168.2.1 0.646ms
2 . 192.168.2.1 1.361ms
2 218.101.61.97 218.101.61.97 122.046ms
3 ae1-947.ie4.telstraclear.net 218.101.61.54 81.541ms
4 ge-1-2-0-843.ie1.telstraclear.net 218.101.61.105 97.252ms
5 ge-0-2-0-1.xcore1.acld.telstraclear.net 203.98.50.251 105.988ms
6 203.167.233.10 203.167.233.10 130.425ms
7 static.net.reach.com 202.84.142.146 140.428ms
8 i-4-1.wil-core02.net.reach.com 202.84.142.133 227.611ms
9 p9_0-ashc1.net.reach.com 202.84.140.90 235.192ms
10 static.net.reach.com 202.84.251.54 274.237ms
11 no reply *
12 te1-1-10G.ar1.MIA2.gblx.net 67.17.108.62 311.004ms
13 INTERNAP.Tengigabitethernet2-2.ar1.MIA2.gblx.net 64.212.16.166 325.072ms
14 border5.pc1.bbnet1.mia003.pnap.net 69.25.0.13 317.175ms
15 webhosting-9.border5.mia003.pnap.net 216.52.162.66 320.618ms
16 64.71.225.26 64.71.225.26 328.576ms
17 no reply *
18 no reply *
19 no reply *
20 no reply *
21 no reply *
22 no reply *
23 no reply *
24 no reply *
25 no reply *
26 no reply *
27 no reply *
28 no reply *
29 no reply *
30 no reply *
31 no reply *

http://64.71.235.167/downloads/linux-2.6.25.4.tar.bz2
186.7 KB/s, 49.6 KB/s, 34.3 KB/s, 31.4 KB/s, 79.0 KB/s

[COLOR=“#0000ff”]Network 2
Pings
Time minimum: 258.00 ms
Time average: 282.96 ms
Time maximum: 378.00 ms

Hop Hostname IP Time 1
1 gabrielle.local 192.168.2.32 0.142ms
1 . 192.168.2.1 0.860ms
1 . 192.168.2.1 0.646ms
2 . 192.168.2.1 1.360ms
2 218.101.61.97 218.101.61.97 95.524ms
3 ae1-947.ie4.telstraclear.net 218.101.61.54 100.034ms
4 ge-1-2-0-843.ie1.telstraclear.net 218.101.61.105 109.854ms
5 ge-0-2-0-1.xcore1.acld.telstraclear.net 203.98.50.251 118.165ms
6 203.167.233.10 203.167.233.10 133.378ms
7 static.net.reach.com 202.84.142.158 90.420ms
8 i-4-1.wil-core02.net.reach.com 202.84.142.133 215.556ms
9 i-6-2.tlot03.net.reach.com 202.84.251.218 215.009ms
10 ge-6-20.car3.LosAngeles1.Level3.net 4.68.111.133 244.047ms
11 vlan69.csw1.LosAngeles1.Level3.net 4.68.20.62 264.962ms
12 ae-62-62.ebr2.LosAngeles1.Level3.net 4.69.137.17 246.776ms
13 ae-3.ebr3.Dallas1.Level3.net 4.69.132.78 273.105ms
14 ae-7.ebr3.Atlanta2.Level3.net 4.69.134.22 296.252ms
15 ae-72-70.ebr2.Atlanta2.Level3.net 4.69.138.19 291.622ms
16 ae-4-4.car2.Miami1.Level3.net 4.69.133.9 307.106ms
17 ae-24-24.car4.Miami1.Level3.net 4.69.133.26 300.433ms
18 EASY-ONLINE.car4.Miami1.Level3.net 4.71.208.6 292.053ms
19 64.59.88.66 64.59.88.66 314.389ms

http://64.59.88.66/linux-2.6.25.4.tar.bz2
160.1 KB/s, 133.5KB/s, 41.2 KB/s, 47.1 KB/s, 65.1 KB/s

12

nzkiwi, thanks

That is what we have been wanting to know a bit how it is doing down in NZ, Australia, etc not bad, Network1 that last hop is our border/edge router the return may be blocked to you for some reason.

13

Here is the results from Casper, Wyoming on Bresnan High Speed at 11:30 AM MST (GMT -7).

Network 1:

PING 64.71.235.167 (64.71.235.167): 56 data bytes
64 bytes from 64.71.235.167: icmp_seq=0 ttl=51 time=106.671 ms
64 bytes from 64.71.235.167: icmp_seq=1 ttl=51 time=105.393 ms
64 bytes from 64.71.235.167: icmp_seq=2 ttl=51 time=104.762 ms
64 bytes from 64.71.235.167: icmp_seq=3 ttl=51 time=107.113 ms
64 bytes from 64.71.235.167: icmp_seq=4 ttl=51 time=105.335 ms

— 64.71.235.167 ping statistics —
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max/stddev = 104.762/105.855/107.113/0.886 ms

traceroute to 64.71.235.167 (64.71.235.167), 64 hops max, 40 byte packets
1 192.168.2.1 (192.168.2.1) 3.922 ms 1.605 ms 0.976 ms
2 host-10-253-200-1.csp-wy.client.bresnan.net (10.253.200.1) 14.307 ms 13.254 ms 15.012 ms
3 cspwy001hb6-GE-0-0-0-U240.int.bresnan.net (69.145.214.243) 10.064 ms 9.802 ms 8.197 ms
4 66.62.160.33 (66.62.160.33) 15.199 ms cspwy001hb1-VL80.int.bresnan.net (69.145.214.82) 9.895 ms 11.110 ms
5 66.62.160.33 (66.62.160.33) 15.611 ms 16.194 ms 20.768 ms
6 den1-core-02.360.net (66.62.6.66) 46.116 ms 42.791 ms 49.236 ms
7 lax1-core-01.360.net (66.62.3.41) 48.757 ms 46.335 ms 47.664 ms
8 lax1-edge-01.360.net (66.62.5.131) 42.357 ms 48.297 ms 46.772 ms
9 laiix.he.net (198.32.146.50) 43.461 ms 42.725 ms 46.653 ms
10 10gigabitethernet1-2.core1.dal1.he.net (72.52.92.58) 78.119 ms 83.171 ms 78.460 ms
11 10gigabitethernet5-2.core1.ash1.he.net (72.52.92.62) 115.131 ms 113.354 ms 121.589 ms
12 10gigabitethernet1-1.core1.mia1.he.net (72.52.92.54) 150.163 ms 139.399 ms 141.140 ms
13 209.51.161.102 (209.51.161.102) 102.407 ms 104.909 ms 110.599 ms
14 64.59.83.2 (64.59.83.2) 104.061 ms 104.151 ms 103.553 ms
15 64.71.226.34 (64.71.226.34) 104.657 ms 107.544 ms 103.582 ms
16 64.71.225.26 (64.71.225.26) 104.212 ms 106.843 ms 102.583 ms
17 smtp1.hr2p.m****here.biz (64.71.235.167) 105.596 ms 106.488 ms 103.392 ms

On 20 MB file - http://64.71.235.167/downloads/tetex...EL4.8.i386.rpm I got about 530 KB a second

Network 2

PING 64.59.88.66 (64.59.88.66): 56 data bytes
64 bytes from 64.59.88.66: icmp_seq=0 ttl=50 time=102.405 ms
64 bytes from 64.59.88.66: icmp_seq=1 ttl=50 time=106.639 ms
64 bytes from 64.59.88.66: icmp_seq=2 ttl=50 time=109.469 ms
64 bytes from 64.59.88.66: icmp_seq=3 ttl=50 time=105.640 ms
64 bytes from 64.59.88.66: icmp_seq=4 ttl=50 time=112.501 ms

— 64.59.88.66 ping statistics —
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max/stddev = 102.405/107.331/112.501/3.432 ms

traceroute to 64.59.88.66 (64.59.88.66), 64 hops max, 40 byte packets
1 192.168.2.1 (192.168.2.1) 2.389 ms 1.696 ms 1.099 ms
2 host-10-253-200-1.csp-wy.client.bresnan.net (10.253.200.1) 19.835 ms 10.011 ms 16.345 ms
3 cspwy001hb6-GE-0-0-0-U240.int.bresnan.net (69.145.214.243) 10.084 ms 9.536 ms 10.889 ms
4 cspwy001hb1-VL88.int.bresnan.net (69.145.214.90) 17.610 ms 10.296 ms 13.097 ms
5 66.62.160.33 (66.62.160.33) 19.552 ms 16.443 ms 19.402 ms
6 den1-core-02.360.net (66.62.4.2) 55.150 ms 63.972 ms 49.204 ms
7 lax1-core-01.360.net (66.62.3.41) 47.107 ms 52.234 ms 56.345 ms
8 lax1-edge-01.360.net (66.62.5.195) 50.168 ms 63.166 ms 45.077 ms
9 laiix.he.net (198.32.146.50) 49.066 ms 52.443 ms 47.848 ms
10 10gigabitethernet1-2.core1.dal1.he.net (72.52.92.58) 81.249 ms 77.283 ms 77.477 ms
11 10gigabitethernet5-2.core1.ash1.he.net (72.52.92.62) 121.565 ms 125.984 ms 115.076 ms
12 10gigabitethernet1-1.core1.mia1.he.net (72.52.92.54) 143.570 ms 140.447 ms 138.830 ms
13 209.51.161.102 (209.51.161.102) 104.786 ms 112.866 ms 107.459 ms
14 64.59.88.66 (64.59.88.66) 106.644 ms 109.996 ms 119.652 ms

On 20 MB file - http://64.59.88.66/tetex-fonts-2.0.2...EL4.8.i386.rpm I got almost 900 KB a second.

14

I just retried the downloads on another computer, and the results are more in line with others are seeing. From Network1 I’m seeing about 670 KBPS; from Network 2 I’m seeing about 660 KBPS.

15

From Ohio

Network 1
|------------------------------------------------------------------------------------------|
| WinMTR statistics |

Host - % Sent Recv Best Avrg Wrst Last
192.168.1.1 - 0 74 74 0 12 328 0
NW-ESR1-72-49-96-1.fuse.net - 0 74 74 0 16 234 15
10ge2-4.ws-osr1.zoomtown.com - 0 74 74 0 23 281 15
10ge2-4.sw2.core.fuse.net - 2 74 73 0 26 282 16
CINCINNATI.car2.Cincinnati1.Level3.net - 0 74 74 0 22 203 15
ge-6-23.car2.Cincinnati1.Level3.net - 0 74 74 0 24 328 16
ae-2-2.bar2.Cincinnati1.Level3.net - 0 74 74 0 23 328 16
ae-7-7.ebr2.Atlanta2.Level3.net - 2 74 73 15 40 266 31
ae-4-4.car2.Miami1.Level3.net - 2 74 73 31 69 500 46
ae-11-11.car1.Miami1.Level3.net - 0 73 73 31 65 437 46
INTERNAP-NE.car1.Miami1.Level3.net - 0 73 73 31 70 515 47
border5.pc2.bbnet2.mia003.pnap.net - 0 73 73 31 70 640 47
webhosting-9.border5.mia003.pnap.net - 0 73 73 31 66 562 94
64.71.225.26 - 0 73 73 31 58 594 31
smtp1.hr2p.m****here.biz - 0 73 73 31 54 500 47
________________________________________________ ______ ______ ______ ______ ______ ______
WinMTR - 0.8. Copyleft @2000-2002 Vasile Laurentiu Stanimir ( [email protected] )

Network 2
|------------------------------------------------------------------------------------------|
| WinMTR statistics |

Host - % Sent Recv Best Avrg Wrst Last
192.168.1.1 - 0 83 83 0 3 172 172
NW-ESR1-72-49-96-1.fuse.net - 0 83 83 0 20 250 78
10ge2-4.ws-osr1.zoomtown.com - 2 83 81 0 19 172 15
10ge2-4.sw2.core.fuse.net - 0 82 82 0 26 203 16
CINCINNATI.car2.Cincinnati1.Level3.net - 0 82 82 15 21 282 15
ge-6-21.car2.Cincinnati1.Level3.net - 0 82 82 0 24 219 16
ae-2-2.bar2.Cincinnati1.Level3.net - 0 82 82 0 28 531 15
ae-7-7.ebr2.Atlanta2.Level3.net - 0 82 82 15 36 359 16
ae-4-4.car2.Miami1.Level3.net - 0 82 82 31 49 343 32
ae-24-24.car4.Miami1.Level3.net - 0 82 82 31 54 610 31
EASY-ONLINE.car4.Miami1.Level3.net - 2 82 81 31 58 531 31
64.59.88.66 - 0 82 82 31 43 437 32
________________________________________________ ______ ______ ______ ______ ______ ______
WinMTR - 0.8. Copyleft @2000-2002 Vasile Laurentiu Stanimir ( [email protected] )
16

Thanks for the heads up Stephen. :slight_smile:

Testing from Perth, West Australia.

Output as follows for Network 1:

For ping -n 25 64.71.235.167

Ping statistics for 64.71.235.167:
    Packets: Sent = 25, Received = 25, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 295ms, Maximum = 296ms, Average = 295ms

For tracert 64.71.235.167

Tracing route to smtp1.hr2p.m****here.biz [64.71.235.167]
over a maximum of 30 hops:

  1     1 ms     1 ms     1 ms  192.168.1.254
  2    15 ms    14 ms    14 ms  nexthop.wa.ii.net [203.59.14.16]
  3    15 ms    15 ms    15 ms  gi2-6.per-qv1-bdr1.ii.net [203.215.4.72]
  4    72 ms    72 ms    72 ms  gi0-15-1-0.syd-ult-core1.ii.net [203.215.20.2]
  5    72 ms    72 ms    73 ms  202.139.19.33
  6   226 ms   226 ms   226 ms  203.208.191.157
  7   230 ms   230 ms   229 ms  208.50.13.185
  8   295 ms   295 ms   295 ms  te1-1-10G.ar1.MIA2.gblx.net [67.17.108.62]
  9   284 ms   286 ms   284 ms INTERNAP.Tengigabitethernet2-2.ar1.MIA2.gblx.net [64.212.16.166]
 10   300 ms   438 ms   436 ms border5.pc1.bbnet1.mia003.pnap.net [69.25.0.13]
 11   294 ms   294 ms   294 ms  webhosting-9.border5.mia003.pnap.net [216.52.162.66]
 12   295 ms   294 ms   294 ms  64.71.225.26
 13   296 ms   296 ms   295 ms  smtp1.hr2p.m****here.biz [64.71.235.167]

Download file from 64.71.235.167 - avg 210KBytes/sec

Output as follows for Network 2:

For ping -n 25 64.59.88.66

Ping statistics for 64.59.88.66:
    Packets: Sent = 25, Received = 25, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 300ms, Maximum = 303ms, Average = 300ms

For tracert 64.59.88.66

Tracing route to 64.59.88.66 over a maximum of 30 hops

  1     1 ms     1 ms     1 ms  192.168.1.254
  2    15 ms    14 ms    15 ms  nexthop.wa.ii.net [203.59.14.16]
  3    15 ms    15 ms    14 ms  gi2-6.per-qv1-bdr1.ii.net [203.215.4.72]
  4    74 ms    74 ms    74 ms  gi0-15-1-1.syd-ult-core1.ii.net [203.215.20.4]
  5    72 ms    72 ms    73 ms  202.139.19.33
  6   226 ms   226 ms   227 ms  203.208.191.157
  7   230 ms   230 ms   231 ms  208.50.13.165
  8   296 ms   295 ms   295 ms  te1-1-10G.ar1.MIA2.gblx.net [67.17.108.62]
  9   301 ms   301 ms   344 ms  ip-204.246.200.2.gblx.net [204.246.200.2]
 10   301 ms   301 ms   301 ms  64.59.88.66

Download file from 64.59.88.66 - avg 46KBytes/sec - very slow.

Hope that helps. Network 1 FTW! Perth seems to have worst result on network 2. But network 1 is awesome, can I have that one? :slight_smile:

17

From the Northern Mariana Islands:

Pinging 64.71.235.167 with 32 bytes of data:
Reply from 64.71.235.167: bytes=32 time=271ms TTL=48
Reply from 64.71.235.167: bytes=32 time=260ms TTL=48
Reply from 64.71.235.167: bytes=32 time=216ms TTL=48
Reply from 64.71.235.167: bytes=32 time=212ms TTL=48
Reply from 64.71.235.167: bytes=32 time=212ms TTL=48
Reply from 64.71.235.167: bytes=32 time=253ms TTL=48
Reply from 64.71.235.167: bytes=32 time=209ms TTL=48
Reply from 64.71.235.167: bytes=32 time=210ms TTL=48
Reply from 64.71.235.167: bytes=32 time=206ms TTL=48
Reply from 64.71.235.167: bytes=32 time=251ms TTL=48
Reply from 64.71.235.167: bytes=32 time=276ms TTL=48
Reply from 64.71.235.167: bytes=32 time=217ms TTL=48
Reply from 64.71.235.167: bytes=32 time=266ms TTL=48
Reply from 64.71.235.167: bytes=32 time=208ms TTL=48
Reply from 64.71.235.167: bytes=32 time=224ms TTL=48
Reply from 64.71.235.167: bytes=32 time=261ms TTL=48
Reply from 64.71.235.167: bytes=32 time=235ms TTL=48
Reply from 64.71.235.167: bytes=32 time=206ms TTL=48
Reply from 64.71.235.167: bytes=32 time=215ms TTL=48
Request timed out.
Reply from 64.71.235.167: bytes=32 time=224ms TTL=48
Reply from 64.71.235.167: bytes=32 time=207ms TTL=48
Reply from 64.71.235.167: bytes=32 time=243ms TTL=48
Reply from 64.71.235.167: bytes=32 time=273ms TTL=48
Reply from 64.71.235.167: bytes=32 time=232ms TTL=48

Ping statistics for 64.71.235.167:
Packets: Sent = 25, Received = 24, Lost = 1 (4% loss),
Approximate round trip times in milli-seconds:
Minimum = 206ms, Maximum = 276ms, Average = 232ms

Tracing route to smtp1.hr2p.m****here.biz [64.71.235.167]
over a maximum of 30 hops:

2 7 ms 8 ms 7 ms 202.88.84.161
3 78 ms 36 ms 13 ms 202-88-65-65.Saipan-gw3.pti1.com [202.88.65.65]

4 38 ms 27 ms 63 ms 202-88-64-4.Saipan-gw4.pti1.com [202.88.64.4]
5 163 ms 150 ms 152 ms se-8-0-8.c2.LosAngeles1.Level3.net [4.78.198.9]

6 175 ms 172 ms 178 ms vlan53.csw1.LosAngeles1.Level3.net [4.68.102.94]

7 181 ms 142 ms 147 ms ae-62-62.ebr2.LosAngeles1.Level3.net [4.69.137.1
7]
8 241 ms 234 ms 235 ms ae-3.ebr3.Dallas1.Level3.net [4.69.132.78]
9 232 ms 234 ms 219 ms ae-7.ebr3.Atlanta2.Level3.net [4.69.134.22]
10 201 ms 213 ms 206 ms ae-72-70.ebr2.Atlanta2.Level3.net [4.69.138.19]

11 247 ms 214 ms 236 ms ae-4-4.car2.Miami1.Level3.net [4.69.133.9]
12 232 ms 253 ms 228 ms ae-11-11.car1.Miami1.Level3.net [4.69.133.5]
13 218 ms 204 ms 214 ms INTERNAP-NE.car1.Miami1.Level3.net [4.79.100.46]

14 213 ms 216 ms 234 ms border5.pc2.bbnet2.mia003.pnap.net [69.25.0.77]

15 244 ms 246 ms 244 ms webhosting-9.border5.mia003.pnap.net [216.52.162
.66]
16 268 ms 215 ms 213 ms 64.71.225.26
17 204 ms 216 ms 219 ms smtp1.hr2p.m****here.biz [64.71.235.167]

Trace complete.

4.8 MB file: 00:46

Pinging 64.59.88.66 with 32 bytes of data:
Reply from 64.59.88.66: bytes=32 time=204ms TTL=51
Reply from 64.59.88.66: bytes=32 time=271ms TTL=51
Reply from 64.59.88.66: bytes=32 time=229ms TTL=51
Reply from 64.59.88.66: bytes=32 time=240ms TTL=51
Reply from 64.59.88.66: bytes=32 time=218ms TTL=51
Reply from 64.59.88.66: bytes=32 time=217ms TTL=51
Reply from 64.59.88.66: bytes=32 time=249ms TTL=51
Reply from 64.59.88.66: bytes=32 time=214ms TTL=51
Reply from 64.59.88.66: bytes=32 time=216ms TTL=51
Reply from 64.59.88.66: bytes=32 time=238ms TTL=51
Reply from 64.59.88.66: bytes=32 time=274ms TTL=51
Reply from 64.59.88.66: bytes=32 time=200ms TTL=51
Reply from 64.59.88.66: bytes=32 time=210ms TTL=51
Reply from 64.59.88.66: bytes=32 time=204ms TTL=51
Reply from 64.59.88.66: bytes=32 time=199ms TTL=51
Reply from 64.59.88.66: bytes=32 time=209ms TTL=51
Reply from 64.59.88.66: bytes=32 time=248ms TTL=51
Reply from 64.59.88.66: bytes=32 time=261ms TTL=51
Reply from 64.59.88.66: bytes=32 time=260ms TTL=51
Reply from 64.59.88.66: bytes=32 time=235ms TTL=51
Reply from 64.59.88.66: bytes=32 time=262ms TTL=51
Reply from 64.59.88.66: bytes=32 time=212ms TTL=51
Reply from 64.59.88.66: bytes=32 time=277ms TTL=51
Reply from 64.59.88.66: bytes=32 time=235ms TTL=51
Reply from 64.59.88.66: bytes=32 time=203ms TTL=51

Ping statistics for 64.59.88.66:
Packets: Sent = 25, Received = 25, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 199ms, Maximum = 277ms, Average = 231ms

Tracing route to 64.59.88.66 over a maximum of 30 hops

2 8 ms 8 ms 7 ms 202.88.84.161
3 11 ms 18 ms 15 ms 202-88-65-65.Saipan-gw3.pti1.com [202.88.65.65]

4 26 ms 22 ms 14 ms 202-88-64-4.Saipan-gw4.pti1.com [202.88.64.4]
5 214 ms 200 ms 178 ms se-8-0-7.c2.LosAngeles1.Level3.net [4.78.205.61]

6 159 ms 153 ms 143 ms vlan51.csw1.LosAngeles1.Level3.net [4.68.102.30]

7 174 ms 151 ms 155 ms ae-62-62.ebr2.LosAngeles1.Level3.net [4.69.137.1
7]
8 176 ms 181 ms 187 ms ae-3.ebr3.Dallas1.Level3.net [4.69.132.78]
9 215 ms 217 ms 260 ms ae-7.ebr3.Atlanta2.Level3.net [4.69.134.22]
10 231 ms 191 ms 207 ms ae-72-70.ebr2.Atlanta2.Level3.net [4.69.138.19]

11 246 ms 211 ms 241 ms ae-4-4.car2.Miami1.Level3.net [4.69.133.9]
12 281 ms 300 ms 282 ms ae-24-24.car4.Miami1.Level3.net [4.69.133.26]
13 227 ms 269 ms 248 ms EASY-ONLINE.car4.Miami1.Level3.net [4.71.208.6]

14 262 ms 202 ms 205 ms 64.59.88.66

Trace complete.

4.8 MB file: 02:12

Ping times between the two networks were close enough to be irrelevant, but the throughput on network 1 is much better for us as evidenced in dramatically lower download times. Interesting that network 2 has fewer hops but poorer download times…

18

wow last to results seem almost abnormal, it would be good if you could test again at another time too :slight_smile:
I am doing the same myself.

BTW Network1 is existing cluster2 network and we are just testing some options as far as some services we may sell now, or later on with network2.
Network2 is also changing for the better here in the coming days with additional carriers coming online and we are working to see what difference they may make as well.

19

Feedback from Amsterdam/NL/Europe

My output (from Amsterdam, The Netherlands, Europe)
[SIZE=“5”]Network1:[/SIZE]

[INDENT][SIZE=“1”]C:>ping -n 25 64.71.235.167
Pinging 64.71.235.167 with 32 bytes of data:
Reply from 64.71.235.167: bytes=32 time=113ms TTL=49
Reply from 64.71.235.167: bytes=32 time=114ms TTL=49
Reply from 64.71.235.167: bytes=32 time=114ms TTL=49
Reply from 64.71.235.167: bytes=32 time=113ms TTL=49
Reply from 64.71.235.167: bytes=32 time=113ms TTL=49
Reply from 64.71.235.167: bytes=32 time=113ms TTL=49
Reply from 64.71.235.167: bytes=32 time=114ms TTL=49
Reply from 64.71.235.167: bytes=32 time=114ms TTL=49
Reply from 64.71.235.167: bytes=32 time=114ms TTL=49
Reply from 64.71.235.167: bytes=32 time=114ms TTL=49
Reply from 64.71.235.167: bytes=32 time=114ms TTL=49
Reply from 64.71.235.167: bytes=32 time=115ms TTL=49
Reply from 64.71.235.167: bytes=32 time=115ms TTL=49
Reply from 64.71.235.167: bytes=32 time=113ms TTL=49
Reply from 64.71.235.167: bytes=32 time=113ms TTL=49
Reply from 64.71.235.167: bytes=32 time=113ms TTL=49
Reply from 64.71.235.167: bytes=32 time=115ms TTL=49
Reply from 64.71.235.167: bytes=32 time=114ms TTL=49
Reply from 64.71.235.167: bytes=32 time=113ms TTL=49
Reply from 64.71.235.167: bytes=32 time=114ms TTL=49
Reply from 64.71.235.167: bytes=32 time=115ms TTL=49
Reply from 64.71.235.167: bytes=32 time=113ms TTL=49
Reply from 64.71.235.167: bytes=32 time=115ms TTL=49
Reply from 64.71.235.167: bytes=32 time=115ms TTL=49
Reply from 64.71.235.167: bytes=32 time=115ms TTL=49

Ping statistics for 64.71.235.167:
Packets: Sent = 25, Received = 25, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 113ms, Maximum = 115ms, Average = 113ms

C:>tracert 64.71.235.167
Tracing route to smtp1.hr2p.mhere.biz [64.71.235.167]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms k035.sbp.ams2.nl.above.net [62.4.95.97]
2 <1 ms <1 ms <1 ms ge-1-2-0.mpr1.ams1.nl.above.net [64.125.26.74]
3 1 ms 1 ms 1 ms ge6-0-0-104-1000m.ar1.ams1.gblx.net [64.208.110.69]
4 224 ms 226 ms 221 ms te2-1-10g.ar1.mia2.gblx.net [67.17.108.90]
5 115 ms 115 ms 115 ms internap.tengigabitethernet2-2.ar1.mia2.gblx.net [64.212.16.166]
6 116 ms 115 ms 116 ms border5.pc1.bbnet1.mia003.pnap.net [69.25.0.13]
7 115 ms 117 ms 115 ms webhosting-9.border5.mia003.pnap.net [216.52.162.66]
8 115 ms 116 ms 116 ms 64.71.225.26
9 115 ms 115 ms 115 ms smtp1.hr2p.mhere.biz [64.71.235.167]
Trace complete.[/SIZE][/INDENT]
Network1 download around 450-515 kb/sec, but not very stable

[SIZE=“5”]Network2:[/SIZE]
[INDENT][SIZE=“1”]C:>ping -n 25 64.59.88.66
Pinging 64.59.88.66 with 32 bytes of data:
Reply from 64.59.88.66: bytes=32 time=117ms TTL=53
Reply from 64.59.88.66: bytes=32 time=115ms TTL=53
Reply from 64.59.88.66: bytes=32 time=115ms TTL=53
Reply from 64.59.88.66: bytes=32 time=115ms TTL=53
Reply from 64.59.88.66: bytes=32 time=114ms TTL=53
Reply from 64.59.88.66: bytes=32 time=114ms TTL=53
Reply from 64.59.88.66: bytes=32 time=114ms TTL=53
Reply from 64.59.88.66: bytes=32 time=114ms TTL=53
Reply from 64.59.88.66: bytes=32 time=114ms TTL=53
Reply from 64.59.88.66: bytes=32 time=114ms TTL=53
Reply from 64.59.88.66: bytes=32 time=114ms TTL=53
Reply from 64.59.88.66: bytes=32 time=114ms TTL=53
Reply from 64.59.88.66: bytes=32 time=114ms TTL=53
Reply from 64.59.88.66: bytes=32 time=114ms TTL=53
Reply from 64.59.88.66: bytes=32 time=114ms TTL=53
Reply from 64.59.88.66: bytes=32 time=115ms TTL=53
Reply from 64.59.88.66: bytes=32 time=114ms TTL=53
Reply from 64.59.88.66: bytes=32 time=114ms TTL=53
Reply from 64.59.88.66: bytes=32 time=116ms TTL=53
Reply from 64.59.88.66: bytes=32 time=116ms TTL=53
Reply from 64.59.88.66: bytes=32 time=114ms TTL=53
Reply from 64.59.88.66: bytes=32 time=114ms TTL=53
Reply from 64.59.88.66: bytes=32 time=115ms TTL=53
Reply from 64.59.88.66: bytes=32 time=113ms TTL=53
Reply from 64.59.88.66: bytes=32 time=114ms TTL=53

Ping statistics for 64.59.88.66:
Packets: Sent = 25, Received = 25, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 113ms, Maximum = 117ms, Average = 114ms

C:>tracert 64.59.88.66
Tracing route to 64.59.88.66 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms k035.sbp.ams2.nl.above.net [62.4.95.97]
2 <1 ms <1 ms <1 ms ge-1-2-0.mpr1.ams1.nl.above.net [64.125.26.74]
3 81 ms 3 ms 2 ms pni.level3.mpr1.ams1.nl.above.net [62.4.95.214]
4 2 ms 1 ms 1 ms ae-32-54.ebr2.amsterdam1.level3.net [4.68.120.126]
5 24 ms 17 ms 17 ms ae-2.ebr2.london1.level3.net [4.69.132.133]
6 90 ms 90 ms 88 ms ae-41.ebr1.newyork1.level3.net [4.69.137.66]
7 88 ms 89 ms 89 ms ae-91-91.csw4.newyork1.level3.net [4.69.134.78]
8 86 ms 87 ms 89 ms ae-93-93.ebr3.newyork1.level3.net [4.69.134.109]
9 90 ms 87 ms 89 ms ae-3.ebr3.washington1.level3.net [4.69.132.89]
10 91 ms 89 ms 89 ms ae-73-73.csw2.washington1.level3.net [4.69.134.166]
11 96 ms 90 ms 89 ms ae-71-71.ebr1.washington1.level3.net [4.69.134.133]
12 106 ms 107 ms 107 ms ae-2.ebr3.atlanta2.level3.net [4.69.132.85]
13 106 ms 108 ms 107 ms ae-72-70.ebr2.atlanta2.level3.net [4.69.138.19]
14 112 ms 113 ms 112 ms ae-4-4.car2.miami1.level3.net [4.69.133.9]
15 115 ms 113 ms 113 ms ae-24-24.car4.miami1.level3.net [4.69.133.26]
16 114 ms 114 ms 114 ms easy-online.car4.miami1.level3.net [4.71.208.6]
17 118 ms 115 ms 114 ms 64.59.88.66

Trace complete.[/SIZE][/INDENT]Network2 download around 258 kb/sec, however the start was at 500kb/sec (speed drops during download)

I performed this tests directly from an 100Mbit connection from a Abovenet datacenter.
FYI: I also did a download-test from download.microsoft.com, where I achieved 2500kb/sec on a Exchange-server-2007 download.

Regards, and success with getting better connectivity!
JP Veen

20

Re: Feedback from Amsterdam/NL/Europe

about ms download center, it is multi threaded so it will start multiple download sessions :0

You can use some download accelerators and do the same thing here if you wanted to test it that way :slight_smile: