New Host Test

[GMSignPainter]

Can you add a poll to this topic?

Done !
That does not prevent you from telling where you live and the tracert, thanks.

[junior]

min=766 max:928 ms:877

sux

[Gaz]

England (East Midlands)

C:\Users\Gaz>ping 70.38.27.250

Pinging 70.38.27.250 with 32 bytes of data:
Reply from 70.38.27.250: bytes=32 time=130ms TTL=53
Reply from 70.38.27.250: bytes=32 time=157ms TTL=53
Reply from 70.38.27.250: bytes=32 time=122ms TTL=53
Reply from 70.38.27.250: bytes=32 time=121ms TTL=53

Ping statistics for 70.38.27.250:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 121ms, Maximum = 157ms, Average = 132ms

C:\Users\Gaz>tracert 70.38.27.250

Tracing route to test-unmetered.iweb.com [70.38.27.250]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.2.1
2 16 ms 8 ms 17 ms 10.251.28.1
3 7 ms 8 ms 9 ms leic-cam-1b-v107.network.virginmedia.net [82.3.3
4.217]
4 26 ms 16 ms 11 ms leic-core-1b-ae2-0.network.virginmedia.net [195.
182.174.149]
5 10 ms 12 ms 8 ms nrth-bb-1b-as6-0.network.virginmedia.net [213.10
5.172.41]
6 12 ms 10 ms 13 ms popl-bb-1a-as3-0.network.virginmedia.net [213.10
5.172.14]
7 19 ms 35 ms 21 ms amst-ic-1-as0-0.network.virginmedia.net [213.105
.175.6]
8 21 ms 38 ms 20 ms ams-sara-cor-1.peer1.net [195.69.145.209]
9 22 ms 22 ms 22 ms oc48-so2-1-0.ldn-teleh-dis-1.peer1.net [216.187.
115.49]
10 106 ms 119 ms 121 ms 216.187.115.33
11 105 ms 107 ms 105 ms 10ge.xe-1-0-0.nyc-telx-dis-1.peer1.net [216.187.
115.181]
12 137 ms 126 ms 132 ms oc192.xe-1-1-0.mtl-bvh-dis-1.peer1.net [216.187.
115.53]
13 109 ms 110 ms 111 ms te6-3.cl-core05.peer1.mtl.iweb.com [216.187.90.1
34]
14 124 ms 121 ms 145 ms te8-2.v0700.cl-core06.mtl.iweb.com [67.205.127.9
4]
15 122 ms 143 ms 130 ms test-unmetered.iweb.com [70.38.27.250]

Trace complete.

[ArabianArrow]

Pinging 94.228.215.100 with 32 bytes of data:
Reply from 94.228.215.100: bytes=32 time=116ms TTL=55
Reply from 94.228.215.100: bytes=32 time=118ms TTL=55
Reply from 94.228.215.100: bytes=32 time=116ms TTL=55
Reply from 94.228.215.100: bytes=32 time=117ms TTL=55

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


1 10 ms 9 ms 9 ms 10.42.160.1
2 13 ms 18 ms 7 ms gw03.slnt.phub.net.cable.rogers.com [66.185.90.1
45]
3 9 ms 14 ms 11 ms gw01.slnt.phub.net.cable.rogers.com [66.185.93.1
93]
4 23 ms 14 ms 23 ms so-5-0-0.gw02.bloor.phub.net.cable.rogers.com [6
6.185.81.77]
5 15 ms 16 ms 17 ms so-1-0-0.gw02.wlfdle.phub.net.cable.rogers.com [
66.185.80.45]
6 30 ms 29 ms 30 ms 69.63.251.154
7 32 ms 29 ms 28 ms 162.97.119.153
8 115 ms 115 ms 116 ms po4-20G.ar4.AMS2.gblx.net [67.16.134.37]
9 118 ms 120 ms 118 ms 64.210.13.70
10 117 ms 123 ms 117 ms monitoring.alp.nl.weservit.nl [94.228.215.100]

Trace complete.

__________________________________________________________

Pinging 93.190.137.7 with 32 bytes of data:
Reply from 93.190.137.7: bytes=32 time=124ms TTL=50
Reply from 93.190.137.7: bytes=32 time=124ms TTL=50
Reply from 93.190.137.7: bytes=32 time=124ms TTL=50
Reply from 93.190.137.7: bytes=32 time=124ms TTL=50

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


Tracing route to 93.190.137.7 over a maximum of 30 hops

1 8 ms 9 ms 10 ms 10.42.160.1
2 8 ms 7 ms 7 ms gw03.slnt.phub.net.cable.rogers.com [66.185.90.1
45]
3 11 ms 8 ms 9 ms gw01.slnt.phub.net.cable.rogers.com [66.185.93.1
97]
4 14 ms 25 ms 13 ms so-5-0-0.gw02.bloor.phub.net.cable.rogers.com [6
6.185.81.77]
5 26 ms 25 ms 25 ms 66.185.82.118
6 45 ms 25 ms 29 ms chg-s1-rou-1001.US.eurorings.net [206.223.119.95
]
7 126 ms 129 ms 124 ms nyk-s2-rou-1001.US.eurorings.net [134.222.226.15
0]
8 109 ms 111 ms 110 ms mchr-s1-rou-1041.UK.eurorings.net [134.222.226.1
58]
9 123 ms 124 ms 122 ms asd2-rou-1021.NL.eurorings.net [134.222.228.13]

10 124 ms 123 ms 123 ms asd2-rou-1002.NL.eurorings.net [134.222.229.109]

11 286 ms 213 ms 237 ms 134.222.97.2
12 126 ms 137 ms 125 ms cn-nawij-is-cr10-ten1-3.caiw.net [62.45.254.5]
13 124 ms 125 ms 124 ms cn-nawij-is-cr10-po2-2.caiw.net [62.45.63.158]
14 128 ms 125 ms 125 ms 93.190.137.7

Trace complete.

__________________________________________________________


Pinging 188.165.193.199 with 32 bytes of data:
Reply from 188.165.193.199: bytes=32 time=107ms TTL=118
Reply from 188.165.193.199: bytes=32 time=105ms TTL=118
Reply from 188.165.193.199: bytes=32 time=107ms TTL=118
Reply from 188.165.193.199: bytes=32 time=107ms TTL=118

Ping statistics for 188.165.193.199:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 105ms, Maximum = 107ms, Average = 106ms



Tracing route to ns210101.ovh.net [188.165.193.199]
over a maximum of 30 hops:

1 7 ms 10 ms 18 ms 10.42.160.1
2 8 ms 6 ms 7 ms gw03.slnt.phub.net.cable.rogers.com [66.185.90.1
45]
3 11 ms 12 ms 9 ms gw01.slnt.phub.net.cable.rogers.com [66.185.93.1
97]
4 24 ms 14 ms 14 ms so-4-1-0.gw02.ym.phub.net.cable.rogers.com [66.1
85.83.198]
5 15 ms 11 ms 15 ms 69.63.251.209
6 21 ms 16 ms 15 ms 69.63.250.185
7 101 ms 31 ms 31 ms 69.63.248.97
8 * * * Request timed out.
9 121 ms 109 ms 133 ms 20g.vss-3-6k.routers.chtix.eu [213.251.130.73]
10 105 ms 107 ms 105 ms ns210101.ovh.net [188.165.193.199]

Trace complete.

__________________________________________________________

Pinging 70.38.27.250 with 32 bytes of data:
Reply from 70.38.27.250: bytes=32 time=22ms TTL=55
Reply from 70.38.27.250: bytes=32 time=23ms TTL=55
Reply from 70.38.27.250: bytes=32 time=21ms TTL=55
Reply from 70.38.27.250: bytes=32 time=22ms TTL=55

Ping statistics for 70.38.27.250:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 21ms, Maximum = 23ms, Average = 22ms


Tracing route to test-unmetered.iweb.com [70.38.27.250]
over a maximum of 30 hops:

1 10 ms 7 ms 9 ms 10.42.160.1
2 10 ms 6 ms 7 ms gw03.slnt.phub.net.cable.rogers.com [66.185.90.1
45]
3 7 ms 8 ms 9 ms gw01.slnt.phub.net.cable.rogers.com [66.185.93.1
93]
4 14 ms 12 ms 13 ms so-4-1-0.gw02.ym.phub.net.cable.rogers.com [66.1
85.83.198]
5 14 ms 14 ms 15 ms 69.63.251.205
6 33 ms 16 ms 67 ms gw01.mtmc.phub.net.cable.rogers.com [66.185.81.1
37]
7 14 ms 13 ms 13 ms 209.58.94.37
8 33 ms 31 ms 31 ms 209.58.94.26
9 51 ms 35 ms 35 ms Vlan1999.icore1.MTT-Montreal.as6453.net [216.6.1
15.54]
10 62 ms 22 ms 27 ms te6-2.cl-core04.tata.mtl.iweb.com [206.82.135.30
]
11 27 ms 21 ms 23 ms te8-1.v0699.cl-core06.mtl.iweb.com [67.205.127.8
6]
12 21 ms 23 ms 37 ms test-unmetered.iweb.com [70.38.27.250]

Trace complete.

[Wardys]

Neuquen / Argentina

Better ping 70.38.27.250

min 216 , max 218, media 216

[dgafjoey]

Location: USA california

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Joey>ping 94.228.215.100

Pinging 94.228.215.100 with 32 bytes of data:
Reply from 94.228.215.100: bytes=32 time=201ms TTL=53
Reply from 94.228.215.100: bytes=32 time=197ms TTL=53
Reply from 94.228.215.100: bytes=32 time=195ms TTL=53
Reply from 94.228.215.100: bytes=32 time=198ms TTL=53

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

C:\Users\Joey>ping 93.190.137.7

Pinging 93.190.137.7 with 32 bytes of data:
Reply from 93.190.137.7: bytes=32 time=180ms TTL=50
Reply from 93.190.137.7: bytes=32 time=181ms TTL=50
Reply from 93.190.137.7: bytes=32 time=182ms TTL=50
Reply from 93.190.137.7: bytes=32 time=189ms TTL=50

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

C:\Users\Joey>ping 188.165.193.199

Pinging 188.165.193.199 with 32 bytes of data:
Reply from 188.165.193.199: bytes=32 time=185ms TTL=116
Reply from 188.165.193.199: bytes=32 time=183ms TTL=116
Reply from 188.165.193.199: bytes=32 time=192ms TTL=116
Reply from 188.165.193.199: bytes=32 time=191ms TTL=116

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

C:\Users\Joey>tracert 94.228.215.100

Tracing route to monitoring.alp.nl.weservit.nl [94.228.215.100]
over a maximum of 30 hops:

1 1 ms <1 ms 1 ms myrouter.home [192.168.1.1]
2 6 ms 7 ms 7 ms L100.LSANCA-VFTTP-121.verizon-gni.net [173.58.73
.1]
3 12 ms 12 ms 15 ms G10-0-4-1921.LSANCA-LCR-09.verizon-gni.net [130.
81.138.84]
4 12 ms 12 ms 13 ms so-4-0-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81
.28.72]
5 12 ms 15 ms 13 ms 0.so-1-2-0.XL3.LAX15.ALTER.NET [152.63.10.133]
6 13 ms 13 ms 14 ms 0.ae3.BR3.LAX15.ALTER.NET [152.63.113.185]
7 12 ms 12 ms 26 ms xe-8-0-0.edge1.LosAngeles9.Level3.net [4.68.62.1
17]
8 22 ms 17 ms 17 ms ae-63-60.ebr3.LosAngeles1.Level3.net [4.69.144.5
2]
9 94 ms 88 ms 89 ms ae-4-4.ebr4.Washington1.Level3.net [4.69.132.82]

10 82 ms 84 ms 89 ms ae-74-74.csw2.Washington1.Level3.net [4.69.134.1
82]
11 84 ms 86 ms 85 ms ae-72-72.ebr2.Washington1.Level3.net [4.69.134.1
49]
12 228 ms 171 ms 172 ms ae-43-43.ebr2.Frankfurt1.Level3.net [4.69.137.57
]
13 175 ms 179 ms 175 ms ae-45-45.ebr1.Dusseldorf1.Level3.net [4.69.143.1
65]
14 177 ms 177 ms 176 ms ae-1-100.ebr2.Dusseldorf1.Level3.net [4.69.141.1
50]
15 182 ms 179 ms 179 ms ae-46-46.ebr1.Amsterdam1.Level3.net [4.69.143.20
1]
16 183 ms 184 ms 181 ms ae-1-51.edge5.Amsterdam1.Level3.net [4.69.139.13
9]
17 188 ms 181 ms 182 ms 212.72.41.30
18 201 ms 199 ms 202 ms 20ge-r1.ams2.nl.as5580.net [80.94.64.126]
19 199 ms 199 ms 199 ms 10ge-netrouting.r1.ams2.nl.as5580.net [78.152.63
.6]
20 193 ms 199 ms 191 ms monitoring.alp.nl.weservit.nl [94.228.215.100]

Trace complete.

C:\Users\Joey>tracert 93.190.137.7

Tracing route to 93.190.137.7 over a maximum of 30 hops

1 <1 ms 1 ms <1 ms myrouter.home [192.168.1.1]
2 24 ms 10 ms 9 ms L100.LSANCA-VFTTP-121.verizon-gni.net [173.58.73
.1]
3 11 ms 9 ms 9 ms G10-0-4-1021.LSANCA-LCR-10.verizon-gni.net [130.
81.140.2]
4 11 ms 12 ms 10 ms so-4-0-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81
.28.74]
5 13 ms 12 ms 12 ms 0.so-6-0-0.XT2.LAX9.ALTER.NET [152.63.10.157]
6 71 ms 69 ms 69 ms 0.so-7-1-0.XL4.CHI13.ALTER.NET [152.63.64.14]
7 71 ms 69 ms 69 ms TenGigE0-7-1-0.GW2.CHI13.ALTER.NET [152.63.65.14
5]
8 68 ms 69 ms 69 ms tinet-gw.customer.alter.net [152.179.92.6]
9 178 ms 174 ms 172 ms xe-8-2-0.ams10.ip4.tinet.net [213.200.81.145]
10 181 ms 182 ms 185 ms caiw-diensten-gw.ip4.tinet.net [77.67.72.134]
11 187 ms 186 ms 187 ms cn-nawij-is-cr10-ten1-3.caiw.net [62.45.254.5]
12 185 ms 184 ms 179 ms cn-nawij-is-cr10-po2-2.caiw.net [62.45.63.158]
13 185 ms 177 ms 184 ms 93.190.137.7

Trace complete.

C:\Users\Joey>tracert 188.165.193.199

Tracing route to ns210101.ovh.net [188.165.193.199]
over a maximum of 30 hops:

1 2 ms 2 ms <1 ms myrouter.home [192.168.1.1]
2 7 ms 7 ms 6 ms L100.LSANCA-VFTTP-121.verizon-gni.net [173.58.73
.1]
3 10 ms 9 ms 9 ms G10-0-4-1021.LSANCA-LCR-10.verizon-gni.net [130.
81.140.2]
4 9 ms 12 ms 12 ms so-4-0-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81
.28.74]
5 19 ms 12 ms 11 ms 0.so-6-0-0.XT2.LAX9.ALTER.NET [152.63.10.157]
6 12 ms 12 ms 12 ms 0.so-7-1-0.XL4.LAX15.ALTER.NET [152.63.1.242]
7 12 ms 12 ms 12 ms POS7-0-0.GW3.LAX15.ALTER.NET [152.63.112.109]
8 13 ms 11 ms 11 ms 65.241.36.82
9 86 ms 95 ms 85 ms xe-2-1-3-0.ashtr1.Ashburn.opentransit.net [193.2
51.240.90]
10 168 ms 176 ms 164 ms pos0-6-5-0.pastr1.Paris.opentransit.net [193.251
.242.97]
11 166 ms 167 ms 167 ms gigabitethernet11-1-0.auvcr2.Aubervilliers.opent
ransit.net [193.251.132.117]
12 166 ms 169 ms 159 ms te2-3.parse3.Paris.opentransit.net [193.251.129.
13]
13 * 204 ms 191 ms 10g.th1-1-6k.routers.chtix.eu [213.251.128.57]
14 184 ms 182 ms 189 ms 20g.vss-3-6k.routers.chtix.eu [94.23.122.93]
15 189 ms 187 ms 191 ms ns210101.ovh.net [188.165.193.199]

Trace complete.

C:\Users\Joey>

[weixman]

ShenZhen of GuangDong province south of China

Pinging 188.165.193.199 with 32 bytes of data:

Reply from 188.165.193.199: bytes=32 time=254ms TTL=114
Reply from 188.165.193.199: bytes=32 time=253ms TTL=114
Reply from 188.165.193.199: bytes=32 time=253ms TTL=114
Reply from 188.165.193.199: bytes=32 time=258ms TTL=114

Ping statistics for 188.165.193.199:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 253ms, Maximum = 258ms, Average = 254ms

C:\Documents and Settings\Administrator>tracert 188.165.193.199

Tracing route to ns210101.ovh.net [188.165.193.199]
over a maximum of 30 hops:

1 2 ms 2 ms 2 ms 192.168.1.1
2 21 ms 20 ms 21 ms 116.25.116.1
3 22 ms 21 ms 21 ms 113.106.40.53
4 98 ms 67 ms 25 ms 119.145.44.206
5 24 ms 23 ms 23 ms 119.145.47.62
6 48 ms 49 ms 47 ms 202.97.35.61
7 46 ms 49 ms 47 ms 202.97.33.38
8 51 ms 50 ms 53 ms 202.97.33.190
9 50 ms 47 ms 47 ms 202.97.35.33
10 228 ms 227 ms 225 ms 202.97.52.146
11 517 ms 535 ms 515 ms ldn-b3-link.telia.net [80.239.193.141]
12 231 ms 229 ms 227 ms ldn-bb2-link.telia.net [80.91.245.28]
13 265 ms 265 ms 265 ms adm-bb4-link.telia.net [80.91.253.146]
14 235 ms 264 ms 238 ms adm-b1-link.telia.net [80.91.253.165]
15 270 ms 271 ms 269 ms 10g.ams-1-6k.routers.chtix.eu [213.251.128.101]

16 309 ms * 250 ms 40g.rbx-1-6k.routers.chtix.eu [213.251.130.65]
17 255 ms 808 ms 253 ms vss-3-6k.routers.chtix.eu [188.165.9.134]
18 257 ms 253 ms 255 ms ns210101.ovh.net [188.165.193.199]

Trace complete.



Pinging 94.228.215.100 with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Reply from 94.228.215.100: bytes=32 time=564ms TTL=45

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






Pinging 93.190.137.7 with 32 bytes of data:

Reply from 93.190.137.7: bytes=32 time=289ms TTL=50
Reply from 93.190.137.7: bytes=32 time=292ms TTL=50
Reply from 93.190.137.7: bytes=32 time=289ms TTL=50
Reply from 93.190.137.7: bytes=32 time=289ms TTL=50

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

C:\Documents and Settings\Administrator>tracert 93.190.137.7

Tracing route to 93.190.137.7 over a maximum of 30 hops

1 2 ms 2 ms 2 ms 192.168.1.1
2 24 ms 21 ms 23 ms 116.25.116.1
3 372 ms 21 ms 23 ms 113.106.40.53
4 21 ms 21 ms 21 ms 119.145.44.210
5 28 ms 23 ms 23 ms 119.145.47.50
6 26 ms 23 ms 25 ms 202.97.34.14
7 23 ms 26 ms 25 ms 202.97.60.158
8 180 ms 179 ms 179 ms 202.97.51.230
9 213 ms 193 ms 197 ms 202.97.50.62
10 193 ms 193 ms 191 ms 218.30.54.70
11 303 ms 309 ms 305 ms xe-0-3-0.ams10.ip4.tinet.net [89.149.183.81]
12 299 ms 299 ms 299 ms caiw-diensten-gw.ip4.tinet.net [77.67.72.134]
13 291 ms 291 ms 291 ms cn-nawij-is-cr10-ten1-3.caiw.net [62.45.254.5]
14 294 ms 293 ms 293 ms cn-nawij-is-cr10-po2-2.caiw.net [62.45.63.158]
15 293 ms 293 ms 295 ms 93.190.137.7

Trace complete.





Pinging 70.38.27.250 with 32 bytes of data:

Reply from 70.38.27.250: bytes=32 time=270ms TTL=47
Reply from 70.38.27.250: bytes=32 time=268ms TTL=47
Reply from 70.38.27.250: bytes=32 time=265ms TTL=47
Reply from 70.38.27.250: bytes=32 time=268ms TTL=47

Ping statistics for 70.38.27.250:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 265ms, Maximum = 270ms, Average = 267ms

C:\Documents and Settings\Administrator>tracert 70.38.27.250

Tracing route to test-unmetered.iweb.com [70.38.27.250]
over a maximum of 30 hops:

1 2 ms 2 ms 2 ms 192.168.1.1
2 21 ms 19 ms 23 ms 116.25.116.1
3 21 ms 21 ms 21 ms 113.106.40.53
4 22 ms 21 ms 21 ms 119.145.44.210
5 23 ms 23 ms 23 ms 119.145.47.10
6 30 ms 29 ms 32 ms 202.97.33.202
7 27 ms 25 ms 27 ms 202.97.60.50
8 188 ms 189 ms 187 ms 202.97.51.210
9 201 ms * 201 ms 202.97.50.62
10 200 ms 199 ms 203 ms te3-5.ccr02.sjc03.atlas.cogentco.com [154.54.11.
89]
11 * * 197 ms te9-3.mpd01.sjc04.atlas.cogentco.com [154.54.0.1
70]
12 200 ms 200 ms 197 ms te8-2.mpd01.sfo01.atlas.cogentco.com [154.54.2.1
65]
13 235 ms 243 ms 231 ms te0-3-0-3.mpd22.mci01.atlas.cogentco.com [154.54
.7.225]
14 247 ms 245 ms 245 ms te0-2-0-3.mpd22.ord01.atlas.cogentco.com [154.54
.6.254]
15 262 ms 261 ms 261 ms te0-3-0-6.ccr21.ymq02.atlas.cogentco.com [154.54
.28.10]
16 269 ms 269 ms 271 ms te8-4.cl-core06.cogent.mtl.iweb.com [38.104.154.
202]
17 265 ms 267 ms 267 ms test-unmetered.iweb.com [70.38.27.250]

Trace complete.

[Cobain]

C:\Users\Cobb>ping 70.38.27.250

Pinging 70.38.27.250 with 32 bytes of data:
Reply from 70.38.27.250: bytes=32 time=320ms TTL=54
Reply from 70.38.27.250: bytes=32 time=317ms TTL=54
Reply from 70.38.27.250: bytes=32 time=319ms TTL=54
Reply from 70.38.27.250: bytes=32 time=315ms TTL=54

Ping statistics for 70.38.27.250:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 315ms, Maximum = 320ms, Average = 317ms

C:\Users\Cobb>ping 188.165.192.199

Pinging 188.165.192.199 with 32 bytes of data:
Reply from 188.165.192.199: bytes=32 time=226ms TTL=54
Reply from 188.165.192.199: bytes=32 time=230ms TTL=54
Reply from 188.165.192.199: bytes=32 time=228ms TTL=54
Reply from 188.165.192.199: bytes=32 time=226ms TTL=54

Ping statistics for 188.165.192.199:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 226ms, Maximum = 230ms, Average = 227ms

Greetings from Malaysia. Just switched to a landline (was using Wimax) and the current host offers much better response time at 230ms. The 70.38.27.250 host averages 320ms

Will do the other hosts and tracert later.. dinner