Last Month the Japanese try to retrive this mod a little bit more. They played in the at 2pm CET. At the moment the gametracker,com Server Monitorring is off. Hope soon they turn it on. The ranking seems to work.
It's no wonder I have a shit ping. This is the horrific journey (including timeouts) that my poor little ping has to make JUST to GET to the ISR server.
Then it has to rough the seas AGAIN to get back to me...
...by which point my car is glitching up against an EU_Pine_m1 like a dog shagging someones leg.
Someone fix the internets.
Microsoft Windows XP [Version 5.1.2600] (C) Copyright 1985-2001 Microsoft Corp.
E:\Documents and Settings\fo0k>tracert 82.103.139.177
Tracing route to e82-103-139-177s.easyspeedy.com [82.103.139.177] over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1 2 137 ms 120 ms 119 ms r220-101-66-2.cpe.unwired.net.au [220.101.66.2] 3 150 ms 127 ms 129 ms v1683-cr2.equ.syd.bbn.unwired.net.au [220.101.190.90] 4 226 ms 129 ms 129 ms ge-2-1.br1.equ.syd.bbn.unwired.net.au [220.101.190.202] 5 228 ms 119 ms 119 ms g0-3-590.cor13.hay.connect.com.au [203.63.71.78] 6 137 ms 119 ms 119 ms ge-0-1-0.bdr5.hay.connect.com.au [203.63.217.18] 7 134 ms 119 ms 120 ms so1-0-0.sybr5.global-gateway.net.nz [203.96.120.125] 8 * * * Request timed out. 9 * * * Request timed out. 10 283 ms 259 ms 269 ms gi1-3.mpd01.lax05.atlas.cogentco.com [154.54.13.121] 11 290 ms 507 ms 259 ms vl3493.mpd01.lax01.atlas.cogentco.com [154.54.6.229] 12 * * * Request timed out. 13 423 ms 310 ms 308 ms te9-2.ccr01.atl01.atlas.cogentco.com [154.54.24.1] 14 459 ms 319 ms 319 ms te9-4.mpd01.dca01.atlas.cogentco.com [154.54.24.9] 15 455 ms 449 ms 449 ms te2-4.mpd03.jfk02.atlas.cogentco.com [154.54.3.46] 16 584 ms 528 ms 510 ms te2-2.mpd02.lon01.atlas.cogentco.com [66.28.4.42] 17 538 ms 520 ms 538 ms gi6-0-0.core01.lon01.atlas.cogentco.com [130.117.1.73] 18 473 ms 449 ms 680 ms po3-0.core01.ams03.atlas.cogentco.com [130.117.0.197] 19 478 ms 459 ms 460 ms po0-0.core01.dus01.atlas.cogentco.com [130.117.1.66] 20 499 ms 490 ms 459 ms po4-0.core01.ham01.atlas.cogentco.com [130.117.1.190] 21 535 ms 468 ms 459 ms po0-0.core01.cph01.atlas.cogentco.com [130.117.2.126] 22 509 ms 469 ms 499 ms netgroup.demarc.cogentco.com [130.117.21.198] 23 495 ms 469 ms 469 ms vl923.cr1.taa.cph.ngdc.net [217.116.255.27] 24 509 ms 469 ms 470 ms easyspeedy.cust.ngdc.net [83.221.128.113] 25 618 ms 490 ms 479 ms e82-103-139-177s.easyspeedy.com [82.103.139.177]
Trace complete.
E:\Documents and Settings\fo0k>tracert 82.103.139.177
And my ping..
Microsoft Windows XP [Version 5.1.2600] (C) Copyright 1985-2001 Microsoft Corp.
E:\Documents and Settings\fo0k>ping 82.103.139.177
Pinging 82.103.139.177 with 32 bytes of data:
Reply from 82.103.139.177: bytes=32 time=513ms TTL=40 Reply from 82.103.139.177: bytes=32 time=503ms TTL=40 Reply from 82.103.139.177: bytes=32 time=481ms TTL=40 Reply from 82.103.139.177: bytes=32 time=550ms TTL=40
Ping statistics for 82.103.139.177: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 481ms, Maximum = 550ms, Average = 511ms
Registered Member #78 Joined: [ 18:27 ] [ 13 Mar 2004 ]
Ping is the time from a request is sent to an answer is received, so this is your ping, not twice this Why the tracert? Instead of just ping.
Just have to rub this in a bit: PING 82.103.139.177 (82.103.139.177): 56 data bytes 64 bytes from 82.103.139.177: icmp_seq=0 ttl=47 time=34.216 ms 64 bytes from 82.103.139.177: icmp_seq=1 ttl=47 time=31.956 ms 64 bytes from 82.103.139.177: icmp_seq=2 ttl=47 time=32.587 ms 64 bytes from 82.103.139.177: icmp_seq=3 ttl=47 time=32.486 ms 64 bytes from 82.103.139.177: icmp_seq=4 ttl=47 time=33.356 ms 64 bytes from 82.103.139.177: icmp_seq=5 ttl=47 time=33.103 ms 64 bytes from 82.103.139.177: icmp_seq=6 ttl=47 time=33.383 ms 64 bytes from 82.103.139.177: icmp_seq=7 ttl=47 time=33.657 ms 64 bytes from 82.103.139.177: icmp_seq=8 ttl=47 time=33.994 ms 64 bytes from 82.103.139.177: icmp_seq=9 ttl=47 time=34.366 ms
--- 82.103.139.177 ping statistics --- 10 packets transmitted, 10 packets received, 0% packet loss round-trip min/avg/max/stddev = 31.956/33.310/34.366/0.749 ms
Registered Member #727 Joined: [ 10:25 ] [ 12 Nov 2004 ]
I'm currently at my university, connected through VPN, and still I have less hops. Oddly enough, however, the actual server doesn't respond.
„Traceroute“ wurde gestartet …
traceroute to 82.103.139.177 (82.103.139.177), 64 hops max, 40 byte packets 1 vpn3030-3.rz.RWTH-Aachen.DE (134.130.5.234) 14.775 ms 11.506 ms 3.312 ms 2 7-254.vpn.RWTH-Aachen.DE (134.130.247.254) 15.232 ms 4.922 ms 13.874 ms 3 c6k-ww10.noc.RWTH-Aachen.DE (137.226.138.1) 92.179 ms 6.008 ms 6.805 ms 4 c6k-rwth.noc.RWTH-Aachen.DE (137.226.139.49) 4.530 ms 5.526 ms 9.901 ms 5 pfi-stone-2.noc.RWTH-Aachen.DE (134.130.9.244) 6.535 ms 3.906 ms 5.595 ms 6 n6k-xwin.noc.RWTH-Aachen.DE (134.130.9.225) 5.241 ms 48.716 ms 42.213 ms 7 xr-aac1-te1-3.x-win.dfn.de (188.1.43.109) 50.279 ms 52.865 ms 34.156 ms 8 zr-fra1-te0-0-0-3.x-win.dfn.de (80.81.192.222) 45.145 ms 16.498 ms 18.516 ms 9 ffm2nxg1.ip.tele.dk (80.81.192.16) 16.195 ms 8.602 ms 74.271 ms 10 pos0-0.2488M.ffm2nxg2.ip.tele.dk (83.88.21.14) 11.717 ms 29.311 ms 17.400 ms 11 pos0-1-0-0.2488M.albnqh2.ip.tele.dk (83.88.26.154) 41.793 ms 63.918 ms 68.824 ms 12 te3-3.10G.alb2nxc7.ip.tele.dk (83.88.25.102) 37.699 ms 32.598 ms 34.259 ms 13 cpe.ge2-1.0x57361dbe.alb2nxc7.customer.tele.dk (87.54.29.190) 33.781 ms 39.487 ms 72.806 ms 14 ge1-3.cr1.taa.cph.ngdc.net (217.116.255.74) 36.094 ms 40.671 ms 38.511 ms 15 easyspeedy.cust.ngdc.net (83.221.128.113) 36.079 ms 47.280 ms 36.514 ms 16 * * *
Anything below down to 64 is * * * as well. Odd, but probably not important. But man, am I remote from the internet here. Six layers of RWTH (my university), then two DFN (Deutsches Forschungsnetzwerk, German Research Network) before I see anything interesting at all.
Tracing route to e82-103-139-177s.easyspeedy.com [82.103.139.177] over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.8.1 2 8 ms 8 ms 8 ms 10.105.128.1 3 9 ms 9 ms 10 ms dr1ge9-18ledsal.leds.al.charter.com [71.91.53.29 ] 4 10 ms 9 ms 18 ms er1ten5-1-0ledsal.leds.al.charter.com [71.91.53. 89] 5 16 ms 15 ms 15 ms 12.118.120.9 6 18 ms 15 ms 16 ms tbr2.attga.ip.att.net [12.123.20.182] 7 18 ms 15 ms 15 ms 12.122.96.65 8 79 ms 217 ms 218 ms 192.205.34.62 9 16 ms 15 ms 16 ms ae-1-55.bbr1.Atlanta1.Level3.net [4.68.103.129]
10 130 ms 139 ms 132 ms as-0-0.bbr1.Dusseldorf1.Level3.net [212.187.128. 98] 11 132 ms 131 ms 133 ms so-3-0-0.mp1.Copenhagen1.Level3.net [4.68.128.18 9] 12 237 ms 308 ms 226 ms ge-1-1.car1.Copenhagen1.Level3.net [4.68.125.190 ] 13 132 ms 131 ms 133 ms 213.242.108.154 14 141 ms 132 ms 131 ms e82-103-139-177s.easyspeedy.com [82.103.139.177]