New IP for Server #6

  • Hey - turns out IRC is out and something a little more modern has taken it's place... A little thing called Discord!

    Join our community @ https://discord.gg/JuaSzXBZrk for a pick-up game, or just to rekindle with fellow community members.

btw dos is accurate they aint to accurate due to icmp 256k filtering on main gateway and core router so dos is only real way to tell but i know its the last hop its nothing more and even if that netkonnect router is spiking the difference is it take them 20 mins to fix that and not 2 weeks with the backbone vital use /me sees vital moving backbone or we are if legend do not sort this issue out soon
 
C:\Documents and Settings\DarkBahamut.HOME-ETK7CKDAU1>ping 195.66.226.75 -t

Pinging 195.66.226.75 with 32 bytes of data:

Reply from 195.66.226.75: bytes=32 time=13ms TTL=249
Reply from 195.66.226.75: bytes=32 time=52ms TTL=249
Reply from 195.66.226.75: bytes=32 time=13ms TTL=249
Reply from 195.66.226.75: bytes=32 time=13ms TTL=249
Reply from 195.66.226.75: bytes=32 time=13ms TTL=249
Reply from 195.66.226.75: bytes=32 time=13ms TTL=249
Reply from 195.66.226.75: bytes=32 time=16ms TTL=249
Reply from 195.66.226.75: bytes=32 time=13ms TTL=249
Reply from 195.66.226.75: bytes=32 time=11ms TTL=249
Reply from 195.66.226.75: bytes=32 time=11ms TTL=249
Reply from 195.66.226.75: bytes=32 time=11ms TTL=249
Reply from 195.66.226.75: bytes=32 time=15ms TTL=249
Reply from 195.66.226.75: bytes=32 time=12ms TTL=249
Reply from 195.66.226.75: bytes=32 time=12ms TTL=249
Reply from 195.66.226.75: bytes=32 time=10ms TTL=249
Reply from 195.66.226.75: bytes=32 time=12ms TTL=249
Reply from 195.66.226.75: bytes=32 time=12ms TTL=249
Reply from 195.66.226.75: bytes=32 time=13ms TTL=249
Reply from 195.66.226.75: bytes=32 time=64ms TTL=249
Reply from 195.66.226.75: bytes=32 time=32ms TTL=249
Reply from 195.66.226.75: bytes=32 time=13ms TTL=249
Reply from 195.66.226.75: bytes=32 time=11ms TTL=249
Reply from 195.66.226.75: bytes=32 time=14ms TTL=249
Reply from 195.66.226.75: bytes=32 time=11ms TTL=249
Reply from 195.66.226.75: bytes=32 time=11ms TTL=249
Reply from 195.66.226.75: bytes=32 time=12ms TTL=249
Reply from 195.66.226.75: bytes=32 time=11ms TTL=249
Reply from 195.66.226.75: bytes=32 time=12ms TTL=249
Reply from 195.66.226.75: bytes=32 time=210ms TTL=249
Reply from 195.66.226.75: bytes=32 time=115ms TTL=249
Reply from 195.66.226.75: bytes=32 time=236ms TTL=249
Reply from 195.66.226.75: bytes=32 time=141ms TTL=249
Reply from 195.66.226.75: bytes=32 time=17ms TTL=249
Reply from 195.66.226.75: bytes=32 time=13ms TTL=249
Reply from 195.66.226.75: bytes=32 time=16ms TTL=249
Reply from 195.66.226.75: bytes=32 time=173ms TTL=249
Reply from 195.66.226.75: bytes=32 time=20ms TTL=249
Reply from 195.66.226.75: bytes=32 time=13ms TTL=249
Reply from 195.66.226.75: bytes=32 time=10ms TTL=249
Reply from 195.66.226.75: bytes=32 time=12ms TTL=249
Reply from 195.66.226.75: bytes=32 time=50ms TTL=249
Reply from 195.66.226.75: bytes=32 time=11ms TTL=249
Reply from 195.66.226.75: bytes=32 time=11ms TTL=249
Reply from 195.66.226.75: bytes=32 time=16ms TTL=249

Ping statistics for 195.66.226.75:
Packets: Sent = 44, Received = 44, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 236ms, Average = 34ms

I can see a few 100ms+ spikes in there. Im telling you that hop 6 is bust :P
 
its the last hop what yer getting spikes on the server itself i guarentee it i have done bout 1000 traces from server to server from usa from everywhere belive me its from last hop to the game server itself

1 31 ms 32 ms 32 ms webport-cl4-hg15.ilford.mdip.bt.net [212.140.212
110]
2 31 ms 31 ms 32 ms 192.168.1.62
3 31 ms 32 ms 32 ms interconnect3-l0.ilford.fixed.bt.net [194.74.77.
27]
4 31 ms 31 ms 31 ms core1-gig10-1.ilford.ukcore.bt.net [194.74.16.11
]
5 32 ms 32 ms 32 ms core1-pos8-0.telehouse.ukcore.bt.net [194.74.65.
17]
6 32 ms 33 ms 32 ms linx-gw2.netkonect.net [195.66.224.75]
7 32 ms 32 ms 32 ms docgw2.netkonect.net [194.62.47.159]
8 180 ms 297 ms 303 ms 194.164.121.200

thats on my leet 64k isdn broardband superdooper connection:D
 
Last edited:
Tracing route to 194.164.121.200 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms SERVER.mshome.net [192.168.0.1]
2 7 ms 7 ms 41 ms 10.75.64.1
3 11 ms 9 ms 7 ms gsr01-pb.blueyonder.co.uk [62.30.192.33]
4 11 ms 13 ms 14 ms tele2-witt-pos.telewest.net [194.117.136.18]
5 12 ms 12 ms 12 ms ge31-linx-gw2.cableinet.net [194.117.154.6]
6 263 ms 271 ms 11 ms linx-gw1.netkonect.net [195.66.226.75]
7 12 ms 12 ms 11 ms docgw2.netkonect.net [194.62.47.159]
8 15 ms 11 ms 16 ms 194.164.121.200

Trace complete.
 
keep doing that and you will see what i mean its only intermitent thats why u get spikes

ill look into that hop 6 i dont go into it but u will see it on the end hop as well if u do traces over and over again
 
Tracing route to 194.164.121.200 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms SERVER.mshome.net [192.168.0.1]
2 8 ms 11 ms 8 ms 10.75.64.1
3 24 ms 8 ms 9 ms gsr01-pb.blueyonder.co.uk [62.30.192.33]
4 13 ms 11 ms 11 ms tele2-witt-pos.telewest.net [194.117.136.18]
5 11 ms 12 ms 12 ms ge31-linx-gw2.cableinet.net [194.117.154.6]
6 52 ms 341 ms 41 ms linx-gw1.netkonect.net [195.66.226.75]
7 13 ms 12 ms 28 ms docgw2.netkonect.net [194.62.47.159]
8 128 ms 239 ms 299 ms 194.164.121.200

Trace complete.

Hop 6 doing it again :P
 
nope and proberly by the time legend fix last hop the 1 whats spiking to you will be fixed:) look at my trace i dont go through it
 
You sure? ;)

its the last hop what yer getting spikes on the server itself i guarentee it i have done bout 1000 traces from server to server from usa from everywhere belive me its from last hop to the game server itself

1 31 ms 32 ms 32 ms webport-cl4-hg15.ilford.mdip.bt.net [212.140.212
110]
2 31 ms 31 ms 32 ms 192.168.1.62
3 31 ms 32 ms 32 ms interconnect3-l0.ilford.fixed.bt.net [194.74.77.
27]
4 31 ms 31 ms 31 ms core1-gig10-1.ilford.ukcore.bt.net [194.74.16.11
]
5 32 ms 32 ms 32 ms core1-pos8-0.telehouse.ukcore.bt.net [194.74.65.
17]
6 32 ms 33 ms 32 ms linx-gw2.netkonect.net [195.66.224.75]
7 32 ms 32 ms 32 ms docgw2.netkonect.net [194.62.47.159]
8 180 ms 297 ms 303 ms 194.164.121.200

thats on my leet 64k isdn broardband superdooper connection
 
6 32 ms 33 ms 32 ms linx-gw2.netkonect.net [195.66.224.75] <<<mine

6 52 ms 341 ms 41 ms linx-gw1.netkonect.net [195.66.226.75] <<<yours 2 different ips
 
that will be fixed in a short time its the last hop which is giving the major spikes and loss soon as thats fixed i will then moan bout that router if its still like that:D
 
Originally posted by Misty
that will be fixed in a short time its the last hop which is giving the major spikes and loss soon as thats fixed i will then moan bout that router if its still like that:D

:lol:

Nice one :thumb:

I'd say the texture problem is the worst tho. Thats weird and it also makes it rather hard to hit people :/
 
i just fixed the texture problem i forgot to do it soz:( and remembered cs uploaded me all his ut cd textures they are now on it so texture problem should be gone:D
 
Thanks :)

Once the spiking has gone theres no doubt server 6 will be the best ping wise. Its the only AS serve rive played on where i can hold under 30ms ;)

Its stupid that assult pings so high tho, i can ping so much lower in CTF and DOM.

(Example, Jolt AS = 40-50ms, jolt CTF = 20-25ms)

(Example 2, Orange AS = 50-60ms, Orange DOM = 15-20ms)

High pings :flack:

Packetloss :mingun:

Low pings :drool:
 
Well I thought i'd just spam my useless tracert...

Tracing route to 194.164.121.200 over a maximum of 30 hops

1 19 ms 21 ms 20 ms 81-86-230-1.dsl.pipex.com [81.86.230.1]
2 22 ms 21 ms 21 ms 62-241-161-21.dsl.pipex.com [62.241.161.21]
3 21 ms 23 ms 21 ms POS5-0.GW1.LND9.ALTER.NET [146.188.63.129]
4 21 ms 23 ms 18 ms so-3-0-0.xr2.lnd9.alter.net [158.43.150.145]
5 20 ms 22 ms 18 ms POS3-0.cr2.lnd10.gbb.uk.uu.net [158.43.150.101]

6 24 ms 22 ms 20 ms pos1-0.cr2.lnd8.gbb.uk.uu.net [158.43.253.149]
7 24 ms 23 ms 22 ms srp0-0-0.br1.lnd8.gbb.uk.uu.net [158.43.189.3]
8 21 ms 23 ms 24 ms linx-gw1.netkonect.net [195.66.226.75]
9 23 ms 25 ms 25 ms docgw2.netkonect.net [194.62.47.159]
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
...

The list goes on; anyone want to shed some light on this?
 
Tracing route to 194.164.121.200 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms my.router [192.168.1.1]
2 12 ms 10 ms 11 ms 195.190.244.173
3 16 ms 15 ms 16 ms 195.190.245.118
4 16 ms 16 ms 16 ms 32.ge-0-0-0.xr1.pbw.xs4all.net [194.109.5.77]
5 16 ms 16 ms 16 ms 0.ge-0-3-0.xr1.sara.xs4all.net [194.109.5.14]
6 16 ms 16 ms 16 ms amsix-bi1.bbnplanet.net [193.148.15.94]
7 18 ms 17 ms 17 ms p7-0.amstnl3-cr4.bbnplanet.net [212.133.10.114]

8 18 ms 19 ms 19 ms p5-0.brslbg1-cr4.bbnplanet.net [212.133.10.234]

9 18 ms 19 ms 19 ms 212.133.10.13
10 23 ms 24 ms 24 ms p3-0.londen3-cr4.bbnplanet.net [212.133.109.1]
11 23 ms 24 ms 24 ms p7-0.londen3-cr3.bbnplanet.net [195.16.160.169]

12 25 ms 25 ms 24 ms p3-0.london2-cr3.bbnplanet.net [212.133.109.21]

13 24 ms 24 ms 24 ms p5-0-0.london2-cr1.bbnplanet.net [195.16.175.178
]
14 24 ms 23 ms 24 ms fa0.netkonect.bbnplanet.net [195.16.174.150]
15 24 ms 25 ms 25 ms docgw90-gw.netkonect.net [194.62.44.139]
16 24 ms 24 ms 24 ms docgw2-gw.netkonect.net [194.164.216.94]
17 * * * Request timed out.
18 * ^C

:? :P
 
Originally posted by Timo_Maas
Well I thought i'd just spam my useless tracert...

Tracing route to 194.164.121.200 over a maximum of 30 hops

1 19 ms 21 ms 20 ms 81-86-230-1.dsl.pipex.com [81.86.230.1]
2 22 ms 21 ms 21 ms 62-241-161-21.dsl.pipex.com [62.241.161.21]
3 21 ms 23 ms 21 ms POS5-0.GW1.LND9.ALTER.NET [146.188.63.129]
4 21 ms 23 ms 18 ms so-3-0-0.xr2.lnd9.alter.net [158.43.150.145]
5 20 ms 22 ms 18 ms POS3-0.cr2.lnd10.gbb.uk.uu.net [158.43.150.101]

6 24 ms 22 ms 20 ms pos1-0.cr2.lnd8.gbb.uk.uu.net [158.43.253.149]
7 24 ms 23 ms 22 ms srp0-0-0.br1.lnd8.gbb.uk.uu.net [158.43.189.3]
8 21 ms 23 ms 24 ms linx-gw1.netkonect.net [195.66.226.75]
9 23 ms 25 ms 25 ms docgw2.netkonect.net [194.62.47.159]
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
...

The list goes on; anyone want to shed some light on this?

Yes, server 6 is now dead altogether :P