DVRIES schreef op woensdag 13 februari 2008 @ 09:21:
Als jullie mee willen werken, zouden jullie deze ip-adressen dan willen testen zodat we gelijkwaardig testuitslagen krijgen?
77.75.122.144 - een ip adres van een gameserver in nederland (Amsterdam)
217.163.10.16 - een gameserver in londen waar de routing ook verkeerd ging.
195.69.144.247 - Core1 van google.nl
62.69.179.230 - server van nu.nl
Vr.gr.
Dennis.
Hoi Dennis,
Hier zijn mijn resultaten:
Target Name: hosted-by.dahhosting.net
IP: 77.75.122.144
Date/Time: 16-Feb-08 1:11:32 PM to 16-Feb-08 1:12:17 PM
1 0 ms 6 ms 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms [192.168.1.1]
2 6 ms 12 ms 12 ms 7 ms 11 ms 9 ms 11 ms 10 ms 11 ms 9 ms 53521001.cable.casema.nl [83.82.16.1]
3 8 ms 19 ms 8 ms 11 ms 12 ms 7 ms 8 ms 7 ms 11 ms 11 ms [10.0.65.2]
4 207 ms 298 ms 10 ms 13 ms * 137 ms 9 ms 10 ms 9 ms * 53500436.cable.casema.nl [83.80.4.54]
5 10 ms 11 ms 13 ms 12 ms 18 ms 13 ms 13 ms 10 ms 11 ms 10 ms 20ge-chnl.amsix.tc2.leaseweb.net [195.69.144.215]
6 9 ms 10 ms 12 ms 9 ms 12 ms 234 ms 10 ms 12 ms 15 ms 11 ms te5-2.sr2.evo.leaseweb.net [85.17.129.250]
7 12 ms 17 ms 10 ms 12 ms 10 ms 12 ms 13 ms 19 ms 16 ms 11 ms [85.17.129.38]
8 * * * * * * * * * * [-]
9 * * * * * * * * * * [-]
10 * * * * * * * * * * [-]
11 * * * * * * * * * * [-]
12 * * * * * * * * * * [-]
13 * * * * * * * * * * [-]
14 * * * * * * * * * * [-]
15 * * * * * * * * * * [-]
16 * * * * * * * * * * [-]
17 * * * * * * * * * * [-]
18 * * * * * * * * * * [-]
19 * * * * * * * * * * [-]
20 * * * * * * * * * * [-]
21 * * * * * * * * * * [-]
22 * * * * * * * * * * [-]
23 * * * * * * * * * * [-]
24 * * * * * * * * * * [-]
25 * * * * * * * * * * [-]
26 * * * * * * * * * * [-]
27 * * * * * * * * * * [-]
28 * * * * * * * * * * [-]
29 * * * * * * * * * * [-]
30 * * * * * * * * * * [-]
31 * * * * * * * * * * [-]
32 * * * * * * * * * * [-]
33 * * * * * * * * * * [-]
34 * * * * * * * * * * [-]
35 * * * * * * * * * * [-]
Destination not reached in 35 hops
---------------
Target Name: N/A
IP: 217.163.10.16
Date/Time: 16-Feb-08 1:13:42 PM to 16-Feb-08 1:14:55 PM
1 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms [192.168.1.1]
2 7 ms 6 ms 9 ms 18 ms 20 ms 8 ms 9 ms 11 ms 8 ms 8 ms 53521001.cable.casema.nl [83.82.16.1]
3 11 ms 8 ms 8 ms 6 ms 8 ms 6 ms 21 ms 9 ms 12 ms 9 ms [10.0.65.2]
4 15 ms 11 ms 2522 ms 226 ms 17 ms 8 ms 12 ms 14 ms 12 ms * 53500436.cable.casema.nl [83.80.4.54]
5 7 ms 9 ms 33 ms 11 ms 20 ms 18 ms 9 ms 10 ms 11 ms 10 ms te3-3.mpd01.ams04.atlas.cogentco.com [149.6.84.201]
6 13 ms 13 ms 14 ms 11 ms 10 ms 10 ms 10 ms 15 ms 16 ms 12 ms vl3492.mpd01.ams03.atlas.cogentco.com [130.117.2.61]
7 21 ms 10 ms 20 ms 8 ms 13 ms 12 ms 13 ms 12 ms 9 ms 11 ms te3-4.ccr01.ams03.atlas.cogentco.com [130.117.3.61]
8 29 ms 17 ms 19 ms 20 ms 26 ms 19 ms 20 ms 19 ms 19 ms 17 ms te3-1.mpd02.lon01.atlas.cogentco.com [130.117.1.38]
9 89 ms 88 ms 91 ms 87 ms 101 ms 93 ms 93 ms 89 ms 212 ms 86 ms te3-4.mpd03.jfk02.atlas.cogentco.com [130.117.1.105]
10 * 85 ms 87 ms 87 ms 90 ms 88 ms 88 ms 89 ms 163 ms * te1-4.mpd01.jfk05.atlas.cogentco.com [154.54.5.210]
11 97 ms 86 ms 85 ms 85 ms 82 ms 85 ms 86 ms 84 ms 84 ms 86 ms Te-8-1.car2.NewYork1.Level3.net [4.68.111.45]
12 105 ms 98 ms 98 ms 84 ms 100 ms 88 ms 90 ms 91 ms 92 ms 94 ms vlan89.csw3.NewYork1.Level3.net [4.68.16.190]
13 95 ms 97 ms 98 ms 100 ms 101 ms 89 ms 91 ms 94 ms 97 ms 98 ms ae-81-81.ebr1.NewYork1.Level3.net [4.69.134.73]
14 94 ms 98 ms 86 ms 86 ms 103 ms 93 ms 95 ms 83 ms 85 ms 90 ms ae-4.ebr2.London1.Level3.net [4.69.132.110]
15 88 ms 87 ms 88 ms 87 ms 105 ms 87 ms 85 ms 87 ms 97 ms 95 ms ge-11-1.ipcolo2.London1.Level3.net [4.68.116.106]
16 86 ms 93 ms 93 ms 93 ms 84 ms 98 ms 88 ms 93 ms 90 ms 90 ms [217.163.10.16]
Ping statistics for 217.163.10.16
Packets: Sent = 10, Received = 10, Lost = 0 (0.0%)
Round Trip Times: Minimum = 84ms, Maximum = 98ms, Average = 90ms
-----------------------
Target Name: core1.ams.net.google.com
IP: 195.69.144.247
Date/Time: 16-Feb-08 1:15:32 PM to 16-Feb-08 1:16:42 PM
1 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms [192.168.1.1]
2 8 ms 11 ms 13 ms 8 ms 9 ms 9 ms 12 ms 7 ms 53521001.cable.casema.nl [83.82.16.1]
3 7 ms 8 ms 7 ms 7 ms 9 ms 7 ms 9 ms 7 ms [10.0.65.2]
4 30 ms 230 ms 42 ms 11 ms 27 ms 10 ms * 18 ms 53500436.cable.casema.nl [83.80.4.54]
5 15 ms 11 ms 9 ms 13 ms 9 ms 8 ms 9 ms 10 ms core1.ams.net.google.com [195.69.144.247]
Ping statistics for core1.ams.net.google.com
Packets: Sent = 8, Received = 8, Lost = 0 (0.0%)
Round Trip Times: Minimum = 8ms, Maximum = 15ms, Average = 10ms
------------------------
Target Name: N/A
IP: 62.69.179.230
Date/Time: 16-Feb-08 1:17:08 PM to 16-Feb-08 1:18:38 PM
1 0 ms 0 ms 0 ms 2 ms 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms [192.168.1.1]
2 8 ms 10 ms 7 ms 19 ms 13 ms 11 ms 32 ms 9 ms 10 ms 8 ms 53521001.cable.casema.nl [83.82.16.1]
3 9 ms 8 ms 7 ms 6 ms 7 ms 8 ms 17 ms 7 ms 9 ms 12 ms [10.0.65.2]
4 14 ms 215 ms 301 ms 12 ms 12 ms 10 ms * 32 ms 22 ms 9 ms 53500436.cable.casema.nl [83.80.4.54]
5 42 ms 12 ms 10 ms 13 ms 10 ms 11 ms 10 ms 198 ms 16 ms 15 ms br1.ams.terremark.net [195.69.145.48]
6 19 ms 9 ms 9 ms 139 ms 12 ms 10 ms 21 ms 10 ms 11 ms 21 ms [85.112.0.73]
7 * * * * * * * * * * [-]
8 13 ms 13 ms 23 ms 11 ms 11 ms 10 ms 12 ms 12 ms 9 ms 12 ms [62.69.179.230]
Ping statistics for 62.69.179.230
Packets: Sent = 10, Received = 10, Lost = 0 (0.0%)
Round Trip Times: Minimum = 9ms, Maximum = 23ms, Average = 12ms
Die 4 is is een beetje een probleem. Bij alle ip adressen zijn er packet losses en errors en ligt de ping beduidend hoger dan bij de rest.