Server 5 down end of month

pinhead · May 26, 2008

It seems everyone whines about lag on server 5 so there's really no point in having me waste the server's resources any further.

Unless a bunch of clans explicitly want to play on this current server 5 please do post here. I am willing to keep it hosted if it's actually gonna be used eagerly. If not then it'll just go down end of the month and probably get replaced by a different server or 5 will be gone altogether for a while.

Weirdo or some other UTA admin will probably make an announcement about that ...

Torp · May 26, 2008

Tbh, the server is alright for 75% of match its just its prone to having laggy spikes lasting up to a minute where your ping seems to randomly treble.

endgegner · May 27, 2008

My experience with it was übernaize ping for me with lagspikes.... Wouldn't mind playing there at all if there weren't random spikes. I think the league needs the available server though.

Prometheus · May 27, 2008

Server was fine when we played on it first, true we had spikes but ping was ok. Now its unplayable ping over 200 on it might be my isp ( FKN DEUTSCHE TELEKOM) tho. :boozer:

pinhead · May 27, 2008

Prometheus said:
Server was fine when we played on it first, true we had spikes but ping was ok. Now its unplayable ping over 200 on it might be my isp ( FKN DEUTSCHE TELEKOM) tho.

Can you post a tracert to the server?
(Go to start, run, type "cmd", <enter>, type "tracert 82.94.241.251", <enter>, wait till done, right-click, mark, select the text, right-click again, paste here)

Solar´ · May 27, 2008

Code:

Bezig met het traceren van de route naar unreal.pyrii.net [82.94.241.251]
via maximaal 30 hops:

  1   <1 ms   <1 ms   <1 ms  192.168.1.1
  2    10 ms     9 ms     9 ms  1.114-243-81.adsl-dyn.isp.belgacom.be [81.243.11
4.1]
  3    11 ms    12 ms    12 ms  197.237-201-80.adsl-static.isp.belgacom.be [80.2
01.237.197]
  4    12 ms    12 ms    12 ms  ge0-0.intlstr1.isp.belgacom.be [194.78.0.46]
  5    11 ms    12 ms    12 ms  80.84.20.206
  6    17 ms    17 ms    17 ms  80.84.18.26
  7    18 ms    17 ms    17 ms  80.84.18.74
  8    18 ms    25 ms    22 ms  ams-ix.tc2.xs4all.net [195.69.144.166]
  9    19 ms    19 ms    19 ms  0.so-2-0-0.xr4.1d12.xs4all.net [194.109.5.9]
 10    19 ms    17 ms    17 ms  0.so-3-0-0.cr1.3d12.xs4all.net [194.109.5.58]
 11    19 ms    19 ms    20 ms  unreal.pyrii.net [82.94.241.251]

De trace is voltooid.





Bezig met het traceren van de route naar unreal.pyrii.net [82.94.241.251]
via maximaal 30 hops:

  1   <1 ms   <1 ms   <1 ms  192.168.1.1
  2     9 ms     9 ms     9 ms  1.114-243-81.adsl-dyn.isp.belgacom.be [81.243.11
4.1]
  3    11 ms    12 ms    12 ms  197.237-201-80.adsl-static.isp.belgacom.be [80.2
01.237.197]
  4    11 ms    12 ms    12 ms  ge0-0.intlstr1.isp.belgacom.be [194.78.0.46]
  5    11 ms    12 ms    12 ms  80.84.20.206
  6    17 ms    17 ms    17 ms  80.84.18.26
  7    15 ms    17 ms    17 ms  80.84.18.74
  8    18 ms    17 ms    17 ms  ams-ix.tc2.xs4all.net [195.69.144.166]
  9    17 ms    17 ms    17 ms  0.so-2-0-0.xr3.3d12.xs4all.net [194.109.5.13]
 10    19 ms    17 ms    19 ms  0.so-2-0-0.cr1.3d12.xs4all.net [194.109.5.74]
 11    18 ms    17 ms    17 ms  unreal.pyrii.net [82.94.241.251]

De trace is voltooid.

It went very quick untill hop 5 :/

'//3iRd(o) · May 27, 2008

It would be very useful if people could post a minutes worth of 1k/s ping to the server and a pathping also; ICMP priority of 32 bytes won't really reflect what you get in game, so this at least highlights any spikes.

Copy the following code and paste into a comand prompt, then post the output file which will be finished when you see the '(Complete)'; text (will take ~5-6 minutes) - the text file can be found in your c $:\$ drive and will be called 'uta5ping'.

Code:

echo %date% - %time% >c:\uta5ping.txt
ping -n 60 -l 1024 82.94.241.251 >>c:\uta5ping.txt
echo %date% - %time% >>c:\uta5ping.txt
pathping 82.94.241.251 >>c:\uta5ping.txt
echo %date% - %time% >>c:\uta5ping.txt
echo (Complete).

Snuggs · May 27, 2008

i made a trace ...with 1395 sent packs :lol:

many spikes..and a hugh 1

Code:

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                             192.168.1.1 -    0 | 1395 | 1395 |    0 |    0 |   16 |    0 |
|                           217.0.116.187 -    0 | 1395 | 1395 |    0 |   13 |   16 |   16 |
|                            217.0.75.166 -    0 | 1395 | 1395 |    0 |   14 |   16 |   16 |
|                  f-eb5.F.DE.net.DTAG.DE -    1 | 1395 | 1394 |    0 |   24 |  218 |   16 |
|                            64.208.27.65 -    1 | 1395 | 1385 |    0 |   69 | 2719 |    0 |
|      XS4ALL.so-7-0-0.nar1.AMS1.gblx.net -    1 | 1394 | 1391 |    0 |   19 |  125 |   16 |
|          0.so-1-0-0.xr3.3d12.xs4all.net -    1 | 1394 | 1388 |    0 |   28 |  140 |   31 |
|          0.so-2-0-0.cr1.3d12.xs4all.net -    1 | 1394 | 1392 |   15 |   30 |  250 |   31 |
|                        unreal.pyrii.net -    1 | 1394 | 1392 |   15 |   21 |  188 |   31 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR - 0.8. Copyleft @2000-2002 Vasile Laurentiu Stanimir  ( [email protected] )

will do cmd thing ..if needed

Solar´ · May 27, 2008

Code:

di 27/05/2008 - 14:28:43,53 


Pingen naar 82.94.241.251 met 1024 byte gegevens:



Antwoord van 82.94.241.251: bytes=1024 tijd=38 ms TTL=54

Antwoord van 82.94.241.251: bytes=1024 tijd=37 ms TTL=54

Antwoord van 82.94.241.251: bytes=1024 tijd=36 ms TTL=54

Antwoord van 82.94.241.251: bytes=1024 tijd=37 ms TTL=54

Antwoord van 82.94.241.251: bytes=1024 tijd=38 ms TTL=54

Antwoord van 82.94.241.251: bytes=1024 tijd=37 ms TTL=54

Antwoord van 82.94.241.251: bytes=1024 tijd=39 ms TTL=54

Antwoord van 82.94.241.251: bytes=1024 tijd=38 ms TTL=54

Antwoord van 82.94.241.251: bytes=1024 tijd=37 ms TTL=54

Antwoord van 82.94.241.251: bytes=1024 tijd=38 ms TTL=54

Antwoord van 82.94.241.251: bytes=1024 tijd=37 ms TTL=54

Antwoord van 82.94.241.251: bytes=1024 tijd=39 ms TTL=54

Antwoord van 82.94.241.251: bytes=1024 tijd=38 ms TTL=54

Antwoord van 82.94.241.251: bytes=1024 tijd=37 ms TTL=54

Antwoord van 82.94.241.251: bytes=1024 tijd=38 ms TTL=54

Antwoord van 82.94.241.251: bytes=1024 tijd=37 ms TTL=54

Antwoord van 82.94.241.251: bytes=1024 tijd=39 ms TTL=54

Antwoord van 82.94.241.251: bytes=1024 tijd=38 ms TTL=54

Antwoord van 82.94.241.251: bytes=1024 tijd=43 ms TTL=54

Antwoord van 82.94.241.251: bytes=1024 tijd=38 ms TTL=54

Antwoord van 82.94.241.251: bytes=1024 tijd=37 ms TTL=54

Antwoord van 82.94.241.251: bytes=1024 tijd=38 ms TTL=54

Antwoord van 82.94.241.251: bytes=1024 tijd=37 ms TTL=54

Antwoord van 82.94.241.251: bytes=1024 tijd=36 ms TTL=54

Antwoord van 82.94.241.251: bytes=1024 tijd=37 ms TTL=54

Antwoord van 82.94.241.251: bytes=1024 tijd=38 ms TTL=54

Antwoord van 82.94.241.251: bytes=1024 tijd=38 ms TTL=54

Antwoord van 82.94.241.251: bytes=1024 tijd=37 ms TTL=54

Antwoord van 82.94.241.251: bytes=1024 tijd=36 ms TTL=54

Antwoord van 82.94.241.251: bytes=1024 tijd=37 ms TTL=54

Antwoord van 82.94.241.251: bytes=1024 tijd=38 ms TTL=54

Antwoord van 82.94.241.251: bytes=1024 tijd=37 ms TTL=54

Antwoord van 82.94.241.251: bytes=1024 tijd=39 ms TTL=54

Antwoord van 82.94.241.251: bytes=1024 tijd=38 ms TTL=54

Antwoord van 82.94.241.251: bytes=1024 tijd=38 ms TTL=54

Antwoord van 82.94.241.251: bytes=1024 tijd=37 ms TTL=54

Antwoord van 82.94.241.251: bytes=1024 tijd=39 ms TTL=54

Antwoord van 82.94.241.251: bytes=1024 tijd=38 ms TTL=54

Antwoord van 82.94.241.251: bytes=1024 tijd=38 ms TTL=54

Antwoord van 82.94.241.251: bytes=1024 tijd=37 ms TTL=54

Antwoord van 82.94.241.251: bytes=1024 tijd=37 ms TTL=54

Antwoord van 82.94.241.251: bytes=1024 tijd=38 ms TTL=54

Antwoord van 82.94.241.251: bytes=1024 tijd=37 ms TTL=54

Antwoord van 82.94.241.251: bytes=1024 tijd=39 ms TTL=54

Antwoord van 82.94.241.251: bytes=1024 tijd=38 ms TTL=54

Antwoord van 82.94.241.251: bytes=1024 tijd=38 ms TTL=54

Antwoord van 82.94.241.251: bytes=1024 tijd=37 ms TTL=54

Antwoord van 82.94.241.251: bytes=1024 tijd=39 ms TTL=54

Antwoord van 82.94.241.251: bytes=1024 tijd=36 ms TTL=54

Antwoord van 82.94.241.251: bytes=1024 tijd=38 ms TTL=54

Antwoord van 82.94.241.251: bytes=1024 tijd=37 ms TTL=54

Antwoord van 82.94.241.251: bytes=1024 tijd=38 ms TTL=54

Antwoord van 82.94.241.251: bytes=1024 tijd=38 ms TTL=54

Antwoord van 82.94.241.251: bytes=1024 tijd=37 ms TTL=54

Antwoord van 82.94.241.251: bytes=1024 tijd=36 ms TTL=54

Antwoord van 82.94.241.251: bytes=1024 tijd=37 ms TTL=54

Antwoord van 82.94.241.251: bytes=1024 tijd=38 ms TTL=54

Antwoord van 82.94.241.251: bytes=1024 tijd=37 ms TTL=54

Antwoord van 82.94.241.251: bytes=1024 tijd=37 ms TTL=54

Antwoord van 82.94.241.251: bytes=1024 tijd=38 ms TTL=54



Ping-statistieken voor 82.94.241.251:

    Pakketten: verzonden = 60, ontvangen = 60, verloren = 0

    (0% verlies).De gemiddelde tijd voor het uitvoeren van ‚‚n bewerking in milliseconden:

    Minimum = 36ms, Maximum = 43ms, Gemiddelde = 37ms

di 27/05/2008 - 14:29:42,75 


Bezig met het traceren van de route naar unreal.pyrii.net [82.94.241.251]

via maximaal 30 hops:

  0  MANU [192.168.1.10] 

  1  192.168.1.1 

  2  1.114-243-81.adsl-dyn.isp.belgacom.be [81.243.114.1] 

  3  165.237-201-80.adsl-static.isp.belgacom.be [80.201.237.165] 

  4  ge1-0.intlstr1.isp.belgacom.be [194.78.0.146] 

  5  80.84.20.34 

  6  80.84.18.161 

  7  80.84.18.74 

  8  ams-ix.tc2.xs4all.net [195.69.144.166] 

  9  0.so-2-0-0.xr3.3d12.xs4all.net [194.109.5.13] 

 10  0.so-3-0-0.cr1.3d12.xs4all.net [194.109.5.58] 

 11  unreal.pyrii.net [82.94.241.251] 



Statistieken worden nu gedurende een periode van 275 seconden berekend...

            Van bron - hier  Dit knooppunt / deze verbinding

Hop  RTT    Verl./verzonden  Verloren/verz.   Adres

  0                                           MANU [192.168.1.10] 

                                0/ 100 =  0%   |

  1    0ms     0/ 100 =  0%     0/ 100 =  0%  192.168.1.1 

                                0/ 100 =  0%   |

  2   12ms     0/ 100 =  0%     0/ 100 =  0%  1.114-243-81.adsl-dyn.isp.belgacom.be [81.243.114.1] 

                                0/ 100 =  0%   |

  3   22ms     0/ 100 =  0%     0/ 100 =  0%  165.237-201-80.adsl-static.isp.belgacom.be [80.201.237.165] 

                                0/ 100 =  0%   |

  4   14ms     0/ 100 =  0%     0/ 100 =  0%  ge1-0.intlstr1.isp.belgacom.be [194.78.0.146] 

                                0/ 100 =  0%   |

  5   19ms     0/ 100 =  0%     0/ 100 =  0%  80.84.20.34 

                                0/ 100 =  0%   |

  6   19ms     0/ 100 =  0%     0/ 100 =  0%  80.84.18.161 

                                0/ 100 =  0%   |

  7   23ms     0/ 100 =  0%     0/ 100 =  0%  80.84.18.74 

                                0/ 100 =  0%   |

  8   20ms     0/ 100 =  0%     0/ 100 =  0%  ams-ix.tc2.xs4all.net [195.69.144.166] 

                                0/ 100 =  0%   |

  9   23ms     0/ 100 =  0%     0/ 100 =  0%  0.so-2-0-0.xr3.3d12.xs4all.net [194.109.5.13] 

                                0/ 100 =  0%   |

 10   26ms     0/ 100 =  0%     0/ 100 =  0%  0.so-3-0-0.cr1.3d12.xs4all.net [194.109.5.58] 

                                0/ 100 =  0%   |

 11   19ms     0/ 100 =  0%     0/ 100 =  0%  unreal.pyrii.net [82.94.241.251] 



De trace is voltooid.

di 27/05/2008 - 14:35:48,34

Here you go

Prometheus · May 27, 2008

pinhead said:
Can you post a tracert to the server?
(Go to start, run, type "cmd", <enter>, type "tracert 82.94.241.251", <enter>, wait till done, right-click, mark, select the text, right-click again, paste here)

Will do pinny

Prometheus · May 27, 2008

Tracing route to unreal.pyrii.net [82.94.241.251]
over a maximum of 30 hops:

1 * * * Request timed out.
2 13 ms 12 ms 12 ms btr04.ip.t-com.hr [172.29.252.49]
3 26 ms 13 ms 12 ms 172.29.1.161
4 13 ms 13 ms 14 ms gtr10-gtr02.ip.t-com.hr [195.29.240.33]
5 30 ms 31 ms 32 ms mil8-hpt-11.mil.seabone.net [195.22.196.81]
6 166 ms * 167 ms ash2-new11-racc1.new.seabone.net [195.22.216.227
]
7 163 ms 174 ms * ash-ix.he.net [206.223.115.37]
8 188 ms 188 ms * 10gigabitethernet1-2.core1.ams1.he.net [72.52.92
.98]
9 * 178 ms * ams-ix.sara.xs4all.net [195.69.144.48]
10 * 177 ms 180 ms 0.so-1-0-0.xr3.3d12.xs4all.net [194.109.5.5]
11 * * 273 ms 0.so-2-0-0.cr1.3d12.xs4all.net [194.109.5.74]
12 266 ms 265 ms 177 ms unreal.pyrii.net [82.94.241.251]

Trace complete.

dErzOnk · May 27, 2008

Routenverfolgung zu unreal.pyrii.net [82.94.241.251] über maximal 30 Abschnitte:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 254 ms 49 ms 22 ms lo1.br04.ber.de.hansenet.net [213.191.89.4]
3 8 ms 8 ms 8 ms ae1-104.crju01.ber.de.hansenet.net [62.109.111.61]
4 27 ms 28 ms 28 ms so-6-1-0-0.cr01.fra.de.hansenet.net [213.191.87.173]
5 27 ms 28 ms 27 ms ae0-101.pr01.fra.de.hansenet.net [62.109.109.176]
6 26 ms 28 ms 28 ms decix-hansenet-2-de.fra.seabone.net [195.22.211.113]
7 27 ms 28 ms 28 ms de-cix.he.net [80.81.192.172]
8 * 32 ms * 10gigabitethernet1-4.core1.ams1.he.net [72.52.92.94]
9 40 ms 38 ms 39 ms ams-ix.sara.xs4all.net [195.69.144.48]
10 186 ms 151 ms 152 ms 0.so-1-0-0.xr3.3d12.xs4all.net [194.109.5.5]
11 201 ms 144 ms 139 ms 0.so-2-0-0.cr1.3d12.xs4all.net [194.109.5.74]
12 136 ms 135 ms 143 ms unreal.pyrii.net [82.94.241.251]

Ablaufverfolgung beendet.

looks like xs4all is not like me

really server5 was allright (all had lagspikes) but last match it was a permanent 200 and more ping for me...

sry man

nightwing` · May 27, 2008

looks fine for me
only in xs4all.net ping increases slightly

Code:

A rastrear a rota para unreal.pyrii.net [82.94.241.251]
até um máximo de 30 saltos:

  1    34 ms    38 ms    38 ms  194-79-94-16.nr.ip.pt [194.79.94.16]
  2     *        *        *     O pedido excedeu o tempo.
  3    36 ms    34 ms    36 ms  195.23.197.0
  4    53 ms    52 ms    52 ms  195.23.15.222
  5    71 ms    74 ms    72 ms  TenGigabitEthernet1-4.ar2.mad1.gblx.net [208.48.
24.1]
  6    82 ms    85 ms    81 ms  XS4ALL.so-7-0-0.nar1.AMS1.gblx.net [146.82.33.17
8]
  7    89 ms    89 ms    89 ms  0.so-1-0-0.xr3.3d12.xs4all.net [194.109.5.5]
  8   188 ms    95 ms    95 ms  0.so-2-0-0.cr1.3d12.xs4all.net [194.109.5.74]
  9    80 ms    81 ms    81 ms  unreal.pyrii.net [82.94.241.251]

Rastreio concluído.



A rastrear a rota para unreal.pyrii.net [82.94.241.251]
até um máximo de 30 saltos:

  1    38 ms    38 ms    36 ms  194-79-94-16.nr.ip.pt [194.79.94.16]
  2     *        *        *     O pedido excedeu o tempo.
  3    38 ms    38 ms    38 ms  195.23.197.0
  4    65 ms    54 ms    56 ms  195.23.15.222
  5    73 ms    71 ms    72 ms  TenGigabitEthernet1-4.ar2.mad1.gblx.net [208.48.
24.1]
  6    83 ms    81 ms    85 ms  XS4ALL.so-7-0-0.nar1.AMS1.gblx.net [146.82.33.17
8]
  7    88 ms   116 ms    87 ms  0.so-1-0-0.xr3.3d12.xs4all.net [194.109.5.5]
  8    83 ms    83 ms    83 ms  0.so-2-0-0.cr1.3d12.xs4all.net [194.109.5.74]
  9    79 ms    79 ms    78 ms  unreal.pyrii.net [82.94.241.251]

Rastreio concluído.


A rastrear a rota para unreal.pyrii.net [82.94.241.251]
até um máximo de 30 saltos:

  1    34 ms    38 ms    38 ms  194-79-94-16.nr.ip.pt [194.79.94.16]
  2     *        *        *     O pedido excedeu o tempo.
  3    34 ms    38 ms    38 ms  195.23.197.0
  4    53 ms    56 ms    54 ms  195.23.15.222
  5    73 ms    70 ms    70 ms  TenGigabitEthernet1-4.ar2.mad1.gblx.net [208.48.
24.1]
  6    82 ms    83 ms    85 ms  XS4ALL.so-7-0-0.nar1.AMS1.gblx.net [146.82.33.17
8]
  7    88 ms    89 ms    89 ms  0.so-1-0-0.xr3.3d12.xs4all.net [194.109.5.5]
  8    84 ms    85 ms    85 ms  0.so-2-0-0.cr1.3d12.xs4all.net [194.109.5.74]
  9    82 ms    81 ms    81 ms  unreal.pyrii.net [82.94.241.251]

Rastreio concluído.

Cassius · May 27, 2008

.

27.05.2008 - 21:18:01,51

Pinging 82.94.241.251 with 1024 bytes of data:

Reply from 82.94.241.251: bytes=1024 time=57ms TTL=49

Reply from 82.94.241.251: bytes=1024 time=54ms TTL=49

Reply from 82.94.241.251: bytes=1024 time=56ms TTL=49

Reply from 82.94.241.251: bytes=1024 time=56ms TTL=48

Reply from 82.94.241.251: bytes=1024 time=56ms TTL=49

Reply from 82.94.241.251: bytes=1024 time=55ms TTL=49

Reply from 82.94.241.251: bytes=1024 time=55ms TTL=49

Reply from 82.94.241.251: bytes=1024 time=58ms TTL=48

Reply from 82.94.241.251: bytes=1024 time=98ms TTL=48

Reply from 82.94.241.251: bytes=1024 time=95ms TTL=49

Reply from 82.94.241.251: bytes=1024 time=99ms TTL=48

Reply from 82.94.241.251: bytes=1024 time=104ms TTL=48

Reply from 82.94.241.251: bytes=1024 time=107ms TTL=49

Reply from 82.94.241.251: bytes=1024 time=57ms TTL=48

Reply from 82.94.241.251: bytes=1024 time=67ms TTL=48

Reply from 82.94.241.251: bytes=1024 time=67ms TTL=48

Reply from 82.94.241.251: bytes=1024 time=72ms TTL=48

Reply from 82.94.241.251: bytes=1024 time=77ms TTL=48

Reply from 82.94.241.251: bytes=1024 time=82ms TTL=49

Reply from 82.94.241.251: bytes=1024 time=87ms TTL=48

Reply from 82.94.241.251: bytes=1024 time=79ms TTL=49

Reply from 82.94.241.251: bytes=1024 time=56ms TTL=49

Reply from 82.94.241.251: bytes=1024 time=55ms TTL=49

Reply from 82.94.241.251: bytes=1024 time=54ms TTL=48

Reply from 82.94.241.251: bytes=1024 time=56ms TTL=48

Reply from 82.94.241.251: bytes=1024 time=55ms TTL=48

Reply from 82.94.241.251: bytes=1024 time=57ms TTL=49

Reply from 82.94.241.251: bytes=1024 time=56ms TTL=49

Reply from 82.94.241.251: bytes=1024 time=57ms TTL=49

Reply from 82.94.241.251: bytes=1024 time=55ms TTL=48

Reply from 82.94.241.251: bytes=1024 time=55ms TTL=48

Reply from 82.94.241.251: bytes=1024 time=55ms TTL=48

Reply from 82.94.241.251: bytes=1024 time=57ms TTL=49

Reply from 82.94.241.251: bytes=1024 time=56ms TTL=49

Reply from 82.94.241.251: bytes=1024 time=56ms TTL=49

Reply from 82.94.241.251: bytes=1024 time=56ms TTL=48

Reply from 82.94.241.251: bytes=1024 time=55ms TTL=48

Reply from 82.94.241.251: bytes=1024 time=57ms TTL=48

Reply from 82.94.241.251: bytes=1024 time=57ms TTL=49

Reply from 82.94.241.251: bytes=1024 time=55ms TTL=48

Reply from 82.94.241.251: bytes=1024 time=55ms TTL=48

Reply from 82.94.241.251: bytes=1024 time=54ms TTL=49

Reply from 82.94.241.251: bytes=1024 time=57ms TTL=49

Reply from 82.94.241.251: bytes=1024 time=57ms TTL=49

Reply from 82.94.241.251: bytes=1024 time=56ms TTL=48

Reply from 82.94.241.251: bytes=1024 time=58ms TTL=49

Reply from 82.94.241.251: bytes=1024 time=55ms TTL=48

Reply from 82.94.241.251: bytes=1024 time=56ms TTL=49

Reply from 82.94.241.251: bytes=1024 time=55ms TTL=49

Reply from 82.94.241.251: bytes=1024 time=57ms TTL=48

Reply from 82.94.241.251: bytes=1024 time=57ms TTL=48

Reply from 82.94.241.251: bytes=1024 time=54ms TTL=49

Reply from 82.94.241.251: bytes=1024 time=56ms TTL=49

Reply from 82.94.241.251: bytes=1024 time=58ms TTL=48

Reply from 82.94.241.251: bytes=1024 time=55ms TTL=49

Reply from 82.94.241.251: bytes=1024 time=57ms TTL=49

Reply from 82.94.241.251: bytes=1024 time=56ms TTL=49

Reply from 82.94.241.251: bytes=1024 time=56ms TTL=49

Reply from 82.94.241.251: bytes=1024 time=55ms TTL=48

Reply from 82.94.241.251: bytes=1024 time=55ms TTL=48

Ping statistics for 82.94.241.251:

Packets: Sent = 60, Received = 60, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 54ms, Maximum = 107ms, Average = 61ms

27.05.2008 - 21:19:00,68

Tracing route to unreal.pyrii.net [82.94.241.251]

over a maximum of 30 hops:

0 cassius.alfanett.no [192.168.1.100]

1 192.168.1.1

2 10.0.0.1

3 128.84-49-199.nextgentel.com [84.49.199.128]

4 172.24.49.30

5 217-13-6-150.dd.nextgentel.com [217.13.6.150]

6 217-13-0-2.dd.nextgentel.com [217.13.0.2]

7 * * 178.84-48-4.nextgentel.com [84.48.4.178]

8 oso-b3-link.telia.net [80.239.193.93]

9 oso-b1-link.telia.net [80.91.251.70]

10 s-bb1-link.telia.net [80.91.249.27]

11 s-b1-link.telia.net [80.91.254.57]

12 global-ic-120468-s-b1.c.telia.net [213.248.77.214]

13 XS4ALL.so-7-0-0.nar1.AMS1.gblx.net [146.82.33.178]

14 0.so-1-0-0.xr3.3d12.xs4all.net [194.109.5.5]

15 0.so-2-0-0.cr1.3d12.xs4all.net [194.109.5.74]

16 unreal.pyrii.net [82.94.241.251]

Computing statistics for 400 seconds...

Source to Here This Node/Link

Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address

0 cassius.alfanett.no [192.168.1.100]

0/ 100 = 0% |

1 1ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.1

0/ 100 = 0% |

2 2ms 0/ 100 = 0% 0/ 100 = 0% 10.0.0.1

0/ 100 = 0% |

3 17ms 0/ 100 = 0% 0/ 100 = 0% 128.84-49-199.nextgentel.com [84.49.199.128]

0/ 100 = 0% |

4 12ms 97/ 100 = 97% 97/ 100 = 97% 172.24.49.30

0/ 100 = 0% |

5 14ms 0/ 100 = 0% 0/ 100 = 0% 217-13-6-150.dd.nextgentel.com [217.13.6.150]

0/ 100 = 0% |

6 18ms 0/ 100 = 0% 0/ 100 = 0% 217-13-0-2.dd.nextgentel.com [217.13.0.2]

0/ 100 = 0% |

7 26ms 0/ 100 = 0% 0/ 100 = 0% 178.84-48-4.nextgentel.com [84.48.4.178]

0/ 100 = 0% |

8 18ms 1/ 100 = 1% 1/ 100 = 1% oso-b3-link.telia.net [80.239.193.93]

0/ 100 = 0% |

9 17ms 0/ 100 = 0% 0/ 100 = 0% oso-b1-link.telia.net [80.91.251.70]

0/ 100 = 0% |

10 26ms 0/ 100 = 0% 0/ 100 = 0% s-bb1-link.telia.net [80.91.249.27]

0/ 100 = 0% |

11 42ms 0/ 100 = 0% 0/ 100 = 0% s-b1-link.telia.net [80.91.254.57]

0/ 100 = 0% |

12 29ms 0/ 100 = 0% 0/ 100 = 0% global-ic-120468-s-b1.c.telia.net [213.248.77.214]

0/ 100 = 0% |

13 45ms 0/ 100 = 0% 0/ 100 = 0% XS4ALL.so-7-0-0.nar1.AMS1.gblx.net [146.82.33.178]

0/ 100 = 0% |

14 43ms 0/ 100 = 0% 0/ 100 = 0% 0.so-1-0-0.xr3.3d12.xs4all.net [194.109.5.5]

0/ 100 = 0% |

15 45ms 0/ 100 = 0% 0/ 100 = 0% 0.so-2-0-0.cr1.3d12.xs4all.net [194.109.5.74]

0/ 100 = 0% |

16 40ms 0/ 100 = 0% 0/ 100 = 0% unreal.pyrii.net [82.94.241.251]

Trace complete.

27.05.2008 - 21:25:53,06

Some mod edit this oversized quote :p:

endgegner · May 27, 2008

Code:

(Complete).echo Tue 05/27/2008 - 15:35:34.32 


Pinging 82.94.241.251 with 1024 bytes of data:



Reply from 82.94.241.251: bytes=1024 time=91ms TTL=51

Reply from 82.94.241.251: bytes=1024 time=90ms TTL=50

Request timed out.

Reply from 82.94.241.251: bytes=1024 time=90ms TTL=50

Reply from 82.94.241.251: bytes=1024 time=90ms TTL=50

Reply from 82.94.241.251: bytes=1024 time=90ms TTL=51

Reply from 82.94.241.251: bytes=1024 time=91ms TTL=50

Reply from 82.94.241.251: bytes=1024 time=91ms TTL=50

Reply from 82.94.241.251: bytes=1024 time=91ms TTL=50

Reply from 82.94.241.251: bytes=1024 time=90ms TTL=50

Reply from 82.94.241.251: bytes=1024 time=91ms TTL=50

Reply from 82.94.241.251: bytes=1024 time=91ms TTL=50

Reply from 82.94.241.251: bytes=1024 time=90ms TTL=51

Reply from 82.94.241.251: bytes=1024 time=91ms TTL=51

Reply from 82.94.241.251: bytes=1024 time=91ms TTL=51

Reply from 82.94.241.251: bytes=1024 time=91ms TTL=50

Reply from 82.94.241.251: bytes=1024 time=90ms TTL=50

Reply from 82.94.241.251: bytes=1024 time=90ms TTL=50

Reply from 82.94.241.251: bytes=1024 time=91ms TTL=51

Reply from 82.94.241.251: bytes=1024 time=90ms TTL=50

Reply from 82.94.241.251: bytes=1024 time=90ms TTL=51

Reply from 82.94.241.251: bytes=1024 time=90ms TTL=51

Reply from 82.94.241.251: bytes=1024 time=90ms TTL=51

Reply from 82.94.241.251: bytes=1024 time=90ms TTL=51

Reply from 82.94.241.251: bytes=1024 time=90ms TTL=51

Reply from 82.94.241.251: bytes=1024 time=91ms TTL=51

Reply from 82.94.241.251: bytes=1024 time=90ms TTL=51

Request timed out.

Reply from 82.94.241.251: bytes=1024 time=91ms TTL=51

Reply from 82.94.241.251: bytes=1024 time=90ms TTL=50

Reply from 82.94.241.251: bytes=1024 time=91ms TTL=51

Reply from 82.94.241.251: bytes=1024 time=91ms TTL=51

Reply from 82.94.241.251: bytes=1024 time=90ms TTL=50

Reply from 82.94.241.251: bytes=1024 time=90ms TTL=51

Reply from 82.94.241.251: bytes=1024 time=90ms TTL=51

Reply from 82.94.241.251: bytes=1024 time=91ms TTL=50

Reply from 82.94.241.251: bytes=1024 time=91ms TTL=51

Request timed out.

Reply from 82.94.241.251: bytes=1024 time=91ms TTL=51

Reply from 82.94.241.251: bytes=1024 time=91ms TTL=51

Reply from 82.94.241.251: bytes=1024 time=91ms TTL=51

Reply from 82.94.241.251: bytes=1024 time=91ms TTL=50

Reply from 82.94.241.251: bytes=1024 time=90ms TTL=51

Reply from 82.94.241.251: bytes=1024 time=91ms TTL=51

Reply from 82.94.241.251: bytes=1024 time=91ms TTL=51

Reply from 82.94.241.251: bytes=1024 time=90ms TTL=50

Reply from 82.94.241.251: bytes=1024 time=90ms TTL=50

Request timed out.

Reply from 82.94.241.251: bytes=1024 time=90ms TTL=50

Reply from 82.94.241.251: bytes=1024 time=90ms TTL=51

Reply from 82.94.241.251: bytes=1024 time=90ms TTL=50

Reply from 82.94.241.251: bytes=1024 time=90ms TTL=50

Reply from 82.94.241.251: bytes=1024 time=90ms TTL=51

Reply from 82.94.241.251: bytes=1024 time=91ms TTL=50

Reply from 82.94.241.251: bytes=1024 time=90ms TTL=50

Reply from 82.94.241.251: bytes=1024 time=90ms TTL=50

Reply from 82.94.241.251: bytes=1024 time=91ms TTL=51

Reply from 82.94.241.251: bytes=1024 time=90ms TTL=51

Reply from 82.94.241.251: bytes=1024 time=90ms TTL=50

Reply from 82.94.241.251: bytes=1024 time=90ms TTL=50



Ping statistics for 82.94.241.251:

    Packets: Sent = 60, Received = 56, Lost = 4 (6% loss),

Approximate round trip times in milli-seconds:

    Minimum = 90ms, Maximum = 91ms, Average = 90ms

Tue 05/27/2008 - 15:36:51.39 


Tracing route to unreal.pyrii.net [82.94.241.251]

over a maximum of 30 hops:

  0  SmantsComp.lasell.edu [10.2.177.17] 

  1  10.0.32.1 

  2  host61.lasellcollegeip.l.subnet.rcn.com [209.122.107.61] 

  3  vl663.aggr2.sbo.ma.rcn.net [208.59.92.105] 

  4  ge3-0.core2.sbo.ma.rcn.net [207.172.15.130] 

  5  pos5-0.core2.nyw.ny.rcn.net [207.172.19.37] 

  6  tge1-2.core1.nyw.ny.rcn.net [207.172.15.66] 

  7  tge1-1.border1.nyw.ny.rcn.net [207.172.19.103] 

  8  nyiix.he.net [198.32.160.61] 

  9  10gigabitethernet1-1.core1.nyc4.he.net [72.52.92.45] 

 10  10gigabitethernet3-1.core1.ams1.he.net [216.66.24.154] 

 11  ams-ix.sara.xs4all.net [195.69.144.48] 

 12  0.so-1-0-0.xr3.3d12.xs4all.net [194.109.5.5] 

 13  0.so-2-0-0.cr1.3d12.xs4all.net [194.109.5.74] 

 14  unreal.pyrii.net [82.94.241.251] 



Computing statistics for 350 seconds...

            Source to Here   This Node/Link

Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address

  0                                           SmantsComp.lasell.edu [10.2.177.17] 

                                0/ 100 =  0%   |

  1    0ms     0/ 100 =  0%     0/ 100 =  0%  10.0.32.1 

                                0/ 100 =  0%   |

  2    0ms     0/ 100 =  0%     0/ 100 =  0%  host61.lasellcollegeip.l.subnet.rcn.com [209.122.107.61] 

                                0/ 100 =  0%   |

  3    7ms     0/ 100 =  0%     0/ 100 =  0%  vl663.aggr2.sbo.ma.rcn.net [208.59.92.105] 

                                0/ 100 =  0%   |

  4    1ms     0/ 100 =  0%     0/ 100 =  0%  ge3-0.core2.sbo.ma.rcn.net [207.172.15.130] 

                                0/ 100 =  0%   |

  5    7ms     0/ 100 =  0%     0/ 100 =  0%  pos5-0.core2.nyw.ny.rcn.net [207.172.19.37] 

                                0/ 100 =  0%   |

  6   18ms     0/ 100 =  0%     0/ 100 =  0%  tge1-2.core1.nyw.ny.rcn.net [207.172.15.66] 

                                0/ 100 =  0%   |

  7   13ms     1/ 100 =  1%     1/ 100 =  1%  tge1-1.border1.nyw.ny.rcn.net [207.172.19.103] 

                                0/ 100 =  0%   |

  8   10ms     1/ 100 =  1%     1/ 100 =  1%  nyiix.he.net [198.32.160.61] 

                                0/ 100 =  0%   |

  9    7ms     1/ 100 =  1%     1/ 100 =  1%  10gigabitethernet1-1.core1.nyc4.he.net [72.52.92.45] 

                                0/ 100 =  0%   |

 10   91ms     0/ 100 =  0%     0/ 100 =  0%  10gigabitethernet3-1.core1.ams1.he.net [216.66.24.154] 

                                0/ 100 =  0%   |

 11  ---     100/ 100 =100%   100/ 100 =100%  ams-ix.sara.xs4all.net [195.69.144.48] 

                                0/ 100 =  0%   |

 12   92ms     0/ 100 =  0%     0/ 100 =  0%  0.so-1-0-0.xr3.3d12.xs4all.net [194.109.5.5] 

                                0/ 100 =  0%   |

 13   94ms     0/ 100 =  0%     0/ 100 =  0%  0.so-2-0-0.cr1.3d12.xs4all.net [194.109.5.74] 

                                0/ 100 =  0%   |

 14   89ms     0/ 100 =  0%     0/ 100 =  0%  unreal.pyrii.net [82.94.241.251] 



Trace complete.

Tue 05/27/2008 - 15:42:45.35

Some nice ping to be honest. Timo :bowdown:

pinhead · May 29, 2008

I've made up my mind, it's going down 1st of June.
I suggest the admins remove it from the league then.

Go ahead and flame me. I (my server) get enough of it in match comments anyway...
http://forums.utassault.net/showthread.php?t=78370

Clans like these obviously have nothing to blame except servers (it's actually just their lack of skill that makes them lose, but being the sore losers that they are they can't acknowledge that). Anyway, good going idiots, you whine about FREE stuff. How much lower can you get. :lol:

Put yourself in my shoes, I've got 55 ping on every server. I can never blame lag for losing, it's always my skills that make me lose a match. But I acknowledge that. Kinda sad for me isn't it? :bawling:

O well, enough ranting, have fun with 1 less server, I doubt anyone really cares anyway. :p:

Bart · May 29, 2008

Well tbh, so many servers aint needed anyway.

Back in the days as the league had 7 stdAS divisions even 5/6 servers were enough.
So no need to have 7 servers nowadays imho.

Op1uM · May 29, 2008

that guy complaining from LAG has the same ping every time no matter what sever he plays on.
talk about losers. lol

endgegner · May 29, 2008

Op1uM said:
that guy complaining from LAG has the same ping every time no matter what sever he plays on.
talk about losers. lol

Opium

endgegner · May 29, 2008

pinhead said:
I've made up my mind, it's going down 1st of June.
I suggest the admins remove it from the league then.

Go ahead and flame me. I (my server) get enough of it in match comments anyway...
http://forums.utassault.net/showthread.php?t=78370

Clans like these obviously have nothing to blame except servers (it's actually just their lack of skill that makes them lose, but being the sore losers that they are they can't acknowledge that). Anyway, good going idiots, you whine about FREE stuff. How much lower can you get.

Put yourself in my shoes, I've got 55 ping on every server. I can never blame lag for losing, it's always my skills that make me lose a match. But I acknowledge that. Kinda sad for me isn't it?

O well, enough ranting, have fun with 1 less server, I doubt anyone really cares anyway.

I dunno Pinny... I wouldn't really take anything -=LAG=- says seriously since they are a bunch of unskilled players (ex: Torp :p:

) who can't accept the fact that they don't know how to aim and blame the server instead of themselves. I've played pro wars with some of them and literally all you hear on TS is "OMFG FUCKING LAG MAN FUCKING SERVER" on every server on every map they're losing. I think the overall response is a resounding "nice server, thanks Pinhead for providing it" and the majority of people get REALLY nice ping. It's even very good for me and Tiago who are usually 120 pingers to Dutch servers. I'd really appreciate it if you'd keep it up, but since it's your own server I can't tell you what to do. I'd just strongly advise you don't take anything LAG says in their match report to heart.

Server 5 down end of month

Cenobite

Hai

The Saviour of UTA. Worship me as DJ worships sofa

?????????

Cenobite

=]????[=

Administrator

Che, Mr. Obscure

=]????[=

?????????

?????????

New Member

? taguZ! ? Pato`

.:Choda Boy:.

The Saviour of UTA. Worship me as DJ worships sofa

Cenobite

Mister Mediocre

Fakenicker!

The Saviour of UTA. Worship me as DJ worships sofa

The Saviour of UTA. Worship me as DJ worships sofa