IP Change

  • 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.

i beleive reply delay from internet routers is irrevelant with u getting higher ping or lags.
it's all about how their config handle icmp.
however, hops do count as everytime a packet goes into a router, it adds delay.

anyway, here my stats :

Pretty good considering i'm from France :cool:

Réponse de 89.238.143.220*: octets=32 temps=13 ms TTL=118
Réponse de 89.238.143.220*: octets=32 temps=13 ms TTL=118
Réponse de 89.238.143.220*: octets=32 temps=13 ms TTL=118
Réponse de 89.238.143.220*: octets=32 temps=13 ms TTL=118

1 5 ms 5 ms 5 ms 82.228.44.254
2 6 ms 5 ms 5 ms 78.254.0.94
3 5 ms 5 ms 5 ms bob75-1-v900.intf.nra.proxad.net [78.254.255.9]
4 5 ms 5 ms 5 ms mna75-1-v902.intf.nra.proxad.net [78.254.255.5]
5 * * * Délai d'attente de la demande dépassé.
6 * 7 ms 6 ms bzn-crs16-1-be1004.intf.routers.proxad.net [212.27.50.173]
7 * * 13 ms londres-6k-1-po101.intf.routers.proxad.net [212.27.51.186]
8 13 ms 13 ms 13 ms 10ge.the.uk.claire.as33970.net [195.66.224.247]
9 14 ms 13 ms 13 ms the-mer.10g.lon.as33970.net [89.238.140.14]
10 13 ms 13 ms 13 ms 89.238.143.220
 
Last edited:
It gets to a busy time and this is what happens:

Reply from 89.238.143.220: bytes=32 time=73ms TTL=118
Reply from 89.238.143.220: bytes=32 time=68ms TTL=118
Reply from 89.238.143.220: bytes=32 time=76ms TTL=118
Reply from 89.238.143.220: bytes=32 time=81ms TTL=118

Tracing route to 89.238.143.220 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.0.1
2 7 ms 7 ms 7 ms 10.235.4.1
3 40 ms 26 ms 44 ms bagu-t2cam1-b-v117.inet.ntl.com [80.5.162.197]
4 10 ms 28 ms 10 ms bagu-t2core-b-ge-wan64.inet.ntl.com [195.182.175
.37]
5 9 ms 42 ms 16 ms lee-bb-b-so-710-0.inet.ntl.com [213.105.174.73]

6 19 ms 32 ms 35 ms lee-bb-a-ge-000-0.inet.ntl.com [62.253.187.185]

7 15 ms 25 ms 18 ms pop-bb-b-so-100-0.inet.ntl.com [62.253.185.238]

8 33 ms 15 ms 15 ms tele-ic-2-as0-0.inet.ntl.com [62.253.184.6]
9 14 ms 32 ms 15 ms 212.250.14.122
10 27 ms 16 ms * the-mer.10g.lon.as33970.net [89.238.140.14]
11 94 ms 70 ms 66 ms 89.238.143.220

Does not suit Virgin Media at all.
 
Code:
 C:\Users\Rasmus>tracert 89.238.143.220

Sporer rute til 8SERVER [89.238.143.220]
over et maksimum af 30 hop:

  1     1 ms     1 ms     1 ms  . [192.168.2.1]
  2     2 ms     1 ms     2 ms  ftx-158-1.sydfynsnet.dk [85.27.158.1]
  3     2 ms     3 ms     2 ms  85.27.128.74
  4     7 ms     6 ms     7 ms  sydfynsel-gw.ip.nianet.dk [83.136.88.121]
  5     6 ms     7 ms     6 ms  gi1-1-1.205.core01.cph01.atlas.cogentco.com [149
.6.83.137]
  6    12 ms    12 ms    11 ms  po9-0.core01.ham01.atlas.cogentco.com [130.117.2
.125]
  7    16 ms    16 ms    18 ms  po2-0.core01.dus01.atlas.cogentco.com [130.117.1
.189]
  8    20 ms    19 ms    20 ms  po0-0.core01.ams03.atlas.cogentco.com [130.117.1
.65]
  9    28 ms    29 ms    28 ms  po12-0.core01.lon01.atlas.cogentco.com [130.117.
0.198]
 10    29 ms    28 ms    28 ms  te1-4.mpd02.lon01.atlas.cogentco.com [130.117.1.
74]
 11    28 ms    29 ms    28 ms  10ge.the.uk.claire.as33970.net [195.66.224.247]

 12    29 ms    29 ms    29 ms  the-mer.10g.lon.as33970.net [89.238.140.14]
 13    81 ms    29 ms    28 ms  8SERVER [89.238.143.220]

Sporing fuldført.

C:\Users\Rasmus>tracert 89.238.143.220

Sporer rute til 8SERVER [89.238.143.220]
over et maksimum af 30 hop:

  1     1 ms     2 ms     2 ms  . [192.168.2.1]
  2     2 ms     2 ms     2 ms  ftx-158-1.sydfynsnet.dk [85.27.158.1]
  3     2 ms     2 ms     2 ms  85.27.128.74
  4     6 ms     6 ms     5 ms  sydfynsel-gw.ip.nianet.dk [83.136.88.121]
  5     5 ms     7 ms     5 ms  gi1-1-1.205.core01.cph01.atlas.cogentco.com [149
.6.83.137]
  6    13 ms    10 ms    10 ms  po9-0.core01.ham01.atlas.cogentco.com [130.117.2
.125]
  7    16 ms    17 ms    16 ms  po2-0.core01.dus01.atlas.cogentco.com [130.117.1
.189]
  8    20 ms    20 ms    21 ms  po0-0.core01.ams03.atlas.cogentco.com [130.117.1
.65]
  9    29 ms    29 ms    29 ms  po12-0.core01.lon01.atlas.cogentco.com [130.117.
0.198]
 10    29 ms    29 ms    28 ms  te1-4.mpd02.lon01.atlas.cogentco.com [130.117.1.
74]
 11    29 ms    33 ms    30 ms  10ge.the.uk.claire.as33970.net [195.66.224.247]

 12   131 ms   236 ms   227 ms  the-mer.10g.lon.as33970.net [89.238.140.14]
 13    28 ms    28 ms    29 ms  8SERVER [89.238.143.220]


Much better

Whats up with hop 12
 
Yes, VM is mostly the problem, however generally there wasn't an issue with the previous server. Or Dog customs, or Jolt servers. Or the Belgian BT server, or German servers, or NL servers (gothica not included). Generally VM has gained consistency but I have never seen such a bad response as this one has.
 
Unfortunately its NTL that sux, doing a trace from the server back to you it goes directly onto NTL's network from my hosts router, so thats server-router-NTL and yet they manage to get an average of 55-60ms ping on each hop to you, quite frankly for a UK ISP thats ridiculous and its not like it can be blamed on routing as it is solely down to NTL.


Hop12 is my hosts router, it doesnt treat ping requests as very important so you will quite often see high ping on there, same router as old IP which did the same, you were just lucky not to notice it.


DJ although you are getting a lot more hops before the ping isnt exactly terrible, on the other hand I dont understand why tut's goes from telia into tele.dk network within 1-2 hops whilst yours decides to piss around on telia network for 5-6 hops before deciding its time to join tele.dk, it would cut out a lot of hops if it just did what it was supposed to although its something that'll be looked at in a bit.
 
Finally it seems like my routing was sorted. Either its Pug server changed IP or my provider changed routers as its changed from "19" jumps to "9" yesterday. I presume its not pugserver changed ip? 35F1 and 60F6 with no pl finally....swe connections roxxor^z

:):):):)
 
be greatful dj


my current routing

Code:
|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                             192.168.1.1 -    0 |  287 |  287 |    0 |    3 |   62 |    0 |
|                           217.0.116.187 -    0 |  287 |  287 |    0 |   21 |  328 |    0 |
|                            217.0.75.162 -    0 |  287 |  287 |    0 |   19 |  328 |   16 |
|                   No response from host -  100 |  287 |    0 |    0 |    0 |    0 |    0 |
|         sl-bb26-nyc-14-3.sprintlink.net -    2 |  287 |  284 |   93 |  107 |  281 |  109 |
|         sl-bb20-nyc-15-0.sprintlink.net -    0 |  287 |  287 |   93 |  111 |  407 |   93 |
|          sl-bb23-nyc-8-0.sprintlink.net -    0 |  287 |  287 |   93 |  111 |  359 |   94 |
|         sl-bb20-par-11-0.sprintlink.net -    0 |  287 |  287 |   93 |  119 |  313 |  297 |
|         sl-bb21-fra-13-0.sprintlink.net -    0 |  287 |  287 |   93 |  119 |  297 |  109 |
|          sl-bb21-vie-3-0.sprintlink.net -    0 |  287 |  287 |  109 |  126 |  282 |  141 |
|       sl-bb20-vie-15-0-0.sprintlink.net -    0 |  287 |  287 |  109 |  123 |  328 |  125 |
|                   win-b2-link.telia.net -    0 |  287 |  287 |  109 |  133 | 1078 | 1078 |
|                  hbg-bb1-link.telia.net -    1 |  287 |  286 |  109 |  124 |  297 |  141 |
|                  ldn-bb1-link.telia.net -    0 |  286 |  286 |  125 |  133 |  281 |  125 |
|                   ldn-b1-link.telia.net -    0 |  286 |  286 |  125 |  133 |  296 |  125 |
|telia-as33970-net-ic-123529-ldn-b1.c.telia.net -    0 |  286 |  286 |  109 |  160 |  453 |  172 |
|                  no-rdns-yet.ohtele.com -    2 |  286 |  281 |  110 |  155 |  359 |  141 |
|                  no-rdns-yet.ohtele.com -    3 |  286 |  280 |  125 |  134 |  375 |  125 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR - 0.8. Copyleft @2000-2002 Vasile Laurentiu Stanimir  ( [email protected] )


:|
 
Tracing route to www.utapug.net [89.238.143.220]
over a maximum of 30 hops:

1 22 ms 99 ms 99 ms dsldevice.lan [192.168.1.254]
2 11 ms 9 ms 9 ms 87-194-20-1.bethere.co.uk [87.194.20.1]
3 * 15 ms 15 ms 10.1.2.1
4 * 15 ms 17 ms 213.161.72.69
5 24 ms 22 ms 22 ms so-0-1-0.mpr1.ams1.nl.above.net [64.125.27.221]

6 33 ms 33 ms 33 ms pos-9-1.mpr2.fra1.de.above.net [64.125.23.253]
7 33 ms 32 ms 32 ms po60.pr1.fra1.de.above.net [64.125.23.234]
8 31 ms 31 ms 30 ms ffm2nxg1.ip.tele.dk [80.81.192.16]
9 30 ms 31 ms 30 ms pos6-0.2488M.ldn2nxg2.ip.tele.dk [83.88.21.110]

10 31 ms 33 ms 31 ms te1-1.10G.ldn2nxc8.ip.tele.dk [83.88.29.162]
11 31 ms 31 ms 31 ms te2-1.10G.ldn2nxc7.ip.tele.dk [83.88.12.137]
12 31 ms 31 ms 30 ms cpe.te2-2.0xc3d76d9a.ldn2nxc7.customer.tele.dk [
195.215.109.154]
13 31 ms 30 ms 30 ms the-mer.10g.lon.as33970.net [89.238.140.14]
14 31 ms 29 ms 30 ms no-rdns-yet.ohtele.com [89.238.143.220]

Trace complete.

Almost as bad as DJs old one and I live in England :saw:
 
Last edited:
A rastrear a rota para no-rdns-yet.ohtele.com [89.238.143.220]
até um máximo de 30 saltos:

1 29 ms 31 ms 31 ms 195.245.137.23
2 31 ms 31 ms 30 ms 195.245.153.78
3 31 ms 31 ms 46 ms 195.245.164.5
4 46 ms 31 ms 31 ms pmi001.esoterica.pt [195.22.12.129]
5 31 ms 31 ms 31 ms rt7tlx-rt1tlx-b.pt.clara.net [195.22.9.177]
6 62 ms 62 ms 62 ms 195.22.9.238.pt.clara.net [195.22.9.238]
7 62 ms 62 ms 62 ms ge-3-1-t6-cr2.router.uk.clara.net [195.157.6.201]
8 62 ms 62 ms 62 ms ten0-0-0-t40-cr1.router.uk.clara.net [195.8.68.117]
9 62 ms 62 ms 62 ms ten0-0-0-t40-br3.router.uk.clara.net [195.8.68.86]
10 62 ms 62 ms 62 ms 10ge.the.uk.claire.as33970.net [195.66.224.247]
11 62 ms 62 ms 62 ms no-rdns-yet.ohtele.com [89.238.140.9]
12 62 ms 62 ms 62 ms no-rdns-yet.ohtele.com [89.238.143.220]

Rastreio concluído.
 
Wish, O2 has oversubscribed some of Be's network which is apparently why we are being routed in a strange way, cant do anything about this.
O2/Be are purchasing an upgrade but thats likely to take a a month or so minimum, so until then routing and slightly higher ping will stay for most Be/O2 customers
 
Last edited:
i don t really understand these pings...

in my ut the f6 ping is the same for all servers, dfp (german), pug (uk) and some nl servers. ut says i got 60 f6 on all servers. f1 ping is nearly the same. around 40, a bit better on german servers but really only a bit.

did that test where u can enter ip s and ping the servers http://www.selfseo.com/ping_test.php

this test says for me : pings around : nl server 35ms, dfp server 50ms, pug server (uk) 110ms
and that s exactly how it feels when playing.

how can ut show me a 60ms f6 ping and the test says 110ms on the same server? and feelingwhise the test is right...
 
Played on the new IP for the first time last night. Felt ok, surely better than the old one!
 
how can ut show me a 60ms f6 ping and the test says 110ms on the same server? and feelingwhise the test is right...


Unless your routing runs through Florida, I wouldn't put much stock in that ping test being an accurate reflection of your own connection.

It's not supposed to show you what your routing is like to the destination, it is showing whether the test's server can see the destination.
 
Code:
Tracing route to no-rdns-yet.ohtele.com [89.238.143.220]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  10.0.32.1
  2     1 ms    <1 ms    <1 ms  host61.lasellcollegeip.l.subnet.rcn.com [209.122
.107.61]
  3     2 ms     1 ms     1 ms  vl663.aggr2.sbo.ma.rcn.net [208.59.92.105]
  4     1 ms     1 ms     1 ms  ge3-0.core2.sbo.ma.rcn.net [207.172.15.130]
  5     6 ms     6 ms     7 ms  pos5-0.core2.nyw.ny.rcn.net [207.172.19.37]
  6     6 ms     6 ms     6 ms  tge1-2.core4.nyw.ny.rcn.net [207.172.15.67]
  7     8 ms     6 ms    12 ms  tge2-1.border1.nyw.ny.rcn.net [207.172.19.109]
  8     7 ms    12 ms     8 ms  ge1-3-6.1000m.nyk2nxg2.ip.tele.dk [198.32.118.51
]
  9   121 ms     *      121 ms  pos0-0-1-0.9953m.boanqh1.ip.tele.dk [83.88.26.10
5]
 10   121 ms   121 ms   121 ms  pos4-0-0.9952m.ldn2nxg1.ip.tele.dk [83.88.12.118
]
 11   121 ms   121 ms   122 ms  te1-1.10g.ldn2nxc7.ip.tele.dk [83.88.28.102]
 12   102 ms   102 ms   102 ms  cpe.te2-2.0xc3d76d9a.ldn2nxc7.customer.tele.dk [
195.215.109.154]
 13   102 ms   103 ms   102 ms  no-rdns-yet.ohtele.com [89.238.140.9]
 14   102 ms   102 ms   102 ms  no-rdns-yet.ohtele.com [89.238.143.220]

Trace complete.
I'm a bit sketched out that I'm routing through Denmark and still have only 14 hops and ~102 ping. However, this is one of 2 cable internet lines at my school... I think I'm usually routed through a fiber optic line in UT where I get an even lower ping and don't route through Denmark.



What is the difference between F6 and F1? I know F1 is simply the ping test (as if a DOS tracer) to the server, but I think I read somewhere that F6 has some ridiculously complex format for calculating which factors in framerate and things like that.. is this the case?
 
As far as I can see from that trace you go through New York to London and nowhere near denmark :confused:

just consider F1 as a basic ping response from to server and F6 as ping response including processing time on server. Im sure someone will give an accurate description but thats good enough :P
 
What is the difference between F6 and F1? I know F1 is simply the ping test (as if a DOS tracer) to the server, but I think I read somewhere that F6 has some ridiculously complex format for calculating which factors in framerate and things like that.. is this the case?

f1 ping = dos ping + ((1000/fps) + (0.5*1000/tickrate))*0.5
f6 ping = dos ping + (1000/tickrate) + (0.5*1000/fps)

So, essentially, F1 ping is your basic dos ping plus half of the overhead of the calculations your UT client is imposing and quarter the overhead of the server, and F6 ping is the basic dos ping plus the overhead from the server and half the overhead of your client; I think what they were roughly aiming for was this:

F1 = Client -> Server (incl overheads)
F6 = Server -> Client (incl overheads)