Guys this is Ogero(blink)256Kbps/64Kbps ping and Tracert time 8:15pm

Ping statistics for 212.58.224.138:
Packets: Sent = 80, Received = 78, Lost = 2 (2% loss),
Approximate round trip times in milli-seconds:
Minimum = 231ms, Maximum = 335ms, Average = 267ms

Tracing route to bbc.co.uk [212.58.224.138]
over a maximum of 30 hops:

1 3 ms 2 ms 2 ms 192.168.1.1
2 50 ms 49 ms 52 ms 77.42.129.93
3 44 ms 49 ms 49 ms 77.42.129.20
4 45 ms 48 ms 49 ms 192.168.111.2
5 298 ms 319 ms 319 ms cr2.n54ny.ip.att.net [12.122.130.166]
6 208 ms 210 ms 200 ms ggr4.n54ny.ip.att.net [12.122.130.33]
7 346 ms 330 ms 323 ms 192.205.34.54
8 201 ms 204 ms 226 ms nyk-bb1-link.telia.net [80.91.248.141]
9 326 ms 340 ms 341 ms ldn-bb1-link.telia.net [80.91.249.248]
10 340 ms 330 ms 339 ms ldn-b3-link.telia.net [80.91.249.170]

Tracing route to eu.logon.worldofwarcraft.com [80.239.178.110]
over a maximum of 30 hops:

1 2 ms 3 ms 3 ms 192.168.1.1
2 45 ms 47 ms 45 ms 77.42.129.93
3 46 ms 49 ms 48 ms 77.42.129.20
4 44 ms 49 ms 48 ms 192.168.111.2
5 203 ms 199 ms 203 ms 12.118.94.93
6 220 ms 229 ms 218 ms cr1.n54ny.ip.att.net [12.122.131.166]
7 198 ms 198 ms 198 ms ggr4.n54ny.ip.att.net [12.122.131.29]

this is oger tracert for WoW eu and for BBC may i know guys what ms i may have on wow ? if possible pls
9 15 pm 
C:\Windows\system32>ping bbc.co.uk -t

Pinging bbc.co.uk [212.58.224.138] with 32 bytes of data:
Reply from 212.58.224.138: bytes=32 time=203ms TTL=118
Reply from 212.58.224.138: bytes=32 time=200ms TTL=118
Reply from 212.58.224.138: bytes=32 time=194ms TTL=118
Reply from 212.58.224.138: bytes=32 time=218ms TTL=118
Reply from 212.58.224.138: bytes=32 time=215ms TTL=118
Reply from 212.58.224.138: bytes=32 time=336ms TTL=118
Reply from 212.58.224.138: bytes=32 time=539ms TTL=118
Reply from 212.58.224.138: bytes=32 time=363ms TTL=118
Reply from 212.58.224.138: bytes=32 time=254ms TTL=118
Reply from 212.58.224.138: bytes=32 time=202ms TTL=118
Reply from 212.58.224.138: bytes=32 time=194ms TTL=118
Reply from 212.58.224.138: bytes=32 time=195ms TTL=118
Reply from 212.58.224.138: bytes=32 time=203ms TTL=118
Reply from 212.58.224.138: bytes=32 time=192ms TTL=118

Ping statistics for 212.58.224.138:
    Packets: Sent = 14, Received = 14, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 192ms, Maximum = 539ms, Average = 250ms
Control-C
^C
C:\Windows\system32>tracert eu.logon.worldofwarcraft.com

Tracing route to eu.logon.worldofwarcraft.com [80.239.180.110]
over a maximum of 30 hops:

  1     2 ms     2 ms     1 ms  192.168.0.254
  2     3 ms     3 ms     4 ms  192.168.1.1
  3    40 ms    38 ms    40 ms  77.42.129.28
  4    45 ms    45 ms    41 ms  77.42.129.2
  5   774 ms   795 ms   637 ms  ge0-1.ar01.leb01.pccwbtn.net [63.218.137.1]
  6   225 ms   246 ms   236 ms  tenge13-3.br02.ldn01.pccwbtn.net [63.218.12.246]
  7   223 ms   216 ms   213 ms  ldn-tci-col2-link.telia.net [213.248.74.45]
  8   214 ms   221 ms   214 ms  ldn-b2-link.telia.net [80.91.250.213]
  9   380 ms   394 ms   424 ms  ldn-bb1-link.telia.net [80.91.250.225]
 10   405 ms   398 ms   381 ms  prs-bb1-link.telia.net [80.91.254.209]
 11   367 ms   391 ms   355 ms  prs-b4-link.telia.net [80.91.251.112]
 12   312 ms   450 ms   220 ms  prs-nant-ks51-geth0-1.telia.net [213.248.98.74]
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *     ^C
C:\Windows\system32>ping eu.logon.worldofwarcraft.com -t

Pinging eu.logon.worldofwarcraft.com [80.239.180.110] with 32 bytes of data:
Request timed out.
Request timed out.

Ping statistics for 80.239.180.110:
    Packets: Sent = 2, Received = 0, Lost = 2 (100% loss),
Control-C
Note that, as you can see, there is a router and im not alone on the network, so times are not very reliable. Im just assuming nobody is downloading anything right now...
it is the same thing, but you must know when pinging you are sending a roughly empty packet with no serious 'load' on it whatsoever.

So when you play WoW or any other game you will have a different latency that is usually higher because you will be sending fully loaded packets and depending on the bandwidth burst, some of them will be lost/timed out .. in other words, your ping in the game will be higher than that :)

try something like: ping -t bbc.co.uk -l 1450
Ping statistics for 212.58.224.138:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 188ms, Maximum = 198ms, Average = 193ms


Tracing route to virtual-vip.thdo.bbc.co.uk [212.58.224.138]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.1
2 44 ms 40 ms 37 ms 77.42.129.28
3 40 ms 38 ms 38 ms 77.42.129.2
4 207 ms 207 ms 208 ms ge0-1.ar01.leb01.pccwbtn.net [63.218.137.1]
5 213 ms 220 ms 222 ms tenge13-3.br02.ldn01.pccwbtn.net [63.218.12.246]
6 191 ms 196 ms 197 ms bbc-gw1-linx.prt0.thdoe.bbc.co.uk [195.66.226.103]
7 201 ms 197 ms 196 ms 212.58.238.149
8 200 ms 197 ms 197 ms virtual-vip.thdo.bbc.co.uk [212.58.224.138]

Tracing route to 80-239-178-110.customer.teliacarrier.com [80.239.178.110]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.1
2 38 ms 37 ms 39 ms 77.42.129.28
3 42 ms 39 ms 38 ms 77.42.129.2
4 214 ms 207 ms 208 ms ge0-1.ar01.leb01.pccwbtn.net [63.218.137.1]
5 210 ms 220 ms 230 ms tenge13-3.br02.ldn01.pccwbtn.net [63.218.12.246]

6 215 ms 209 ms 215 ms ldn-tci-col2-link.telia.net [213.248.74.45]
7 219 ms 219 ms 219 ms ldn-b2-link.telia.net [80.91.250.213]
8 234 ms 235 ms 231 ms ldn-bb2-link.telia.net [80.91.252.13]
9 355 ms 327 ms 339 ms prs-bb2-link.telia.net [80.91.254.211]
10 228 ms 223 ms 223 ms prs-b1-link.telia.net [80.91.250.249]
11 231 ms 233 ms 244 ms prs-tc-i1-link-telia.net [80.91.250.30]
12 * * * Request timed out.
Pinging bbc.co.uk [212.58.224.138] with 32 bytes of data:

Reply from 212.58.224.138: bytes=32 time=264ms TTL=119
Reply from 212.58.224.138: bytes=32 time=259ms TTL=119
Reply from 212.58.224.138: bytes=32 time=263ms TTL=119
Reply from 212.58.224.138: bytes=32 time=257ms TTL=119
Reply from 212.58.224.138: bytes=32 time=262ms TTL=119
Reply from 212.58.224.138: bytes=32 time=258ms TTL=119
Reply from 212.58.224.138: bytes=32 time=264ms TTL=119
Reply from 212.58.224.138: bytes=32 time=266ms TTL=119
Reply from 212.58.224.138: bytes=32 time=265ms TTL=119
Reply from 212.58.224.138: bytes=32 time=261ms TTL=119
Reply from 212.58.224.138: bytes=32 time=263ms TTL=119
Reply from 212.58.224.138: bytes=32 time=262ms TTL=119
Reply from 212.58.224.138: bytes=32 time=265ms TTL=119
Request timed out.
Reply from 212.58.224.138: bytes=32 time=265ms TTL=119
Reply from 212.58.224.138: bytes=32 time=258ms TTL=119
Reply from 212.58.224.138: bytes=32 time=264ms TTL=119
Reply from 212.58.224.138: bytes=32 time=258ms TTL=119
Reply from 212.58.224.138: bytes=32 time=276ms TTL=119
Reply from 212.58.224.138: bytes=32 time=324ms TTL=119
Reply from 212.58.224.138: bytes=32 time=265ms TTL=119
Reply from 212.58.224.138: bytes=32 time=267ms TTL=119
Reply from 212.58.224.138: bytes=32 time=257ms TTL=119

Ping statistics for 212.58.224.138:

    Packets: Sent = 23, Received = 22, Lost = 1 (4% loss),
Approximate round trip times in milli-seconds:
    Minimum = 257ms, Maximum = 324ms, Average = 265ms

Control-C
and 
Pinging bbc.co.uk [212.58.224.138] with 1450 bytes of data:

Reply from 212.58.224.138: bytes=1450 time=390ms TTL=119
Reply from 212.58.224.138: bytes=1450 time=384ms TTL=119
Reply from 212.58.224.138: bytes=1450 time=376ms TTL=119
Reply from 212.58.224.138: bytes=1450 time=391ms TTL=119
Reply from 212.58.224.138: bytes=1450 time=390ms TTL=119
Request timed out.
Reply from 212.58.224.138: bytes=1450 time=386ms TTL=119
Reply from 212.58.224.138: bytes=1450 time=391ms TTL=119
Reply from 212.58.224.138: bytes=1450 time=383ms TTL=119
Reply from 212.58.224.138: bytes=1450 time=380ms TTL=119
Reply from 212.58.224.138: bytes=1450 time=381ms TTL=119
Reply from 212.58.224.138: bytes=1450 time=388ms TTL=119
Reply from 212.58.224.138: bytes=1450 time=392ms TTL=119
Reply from 212.58.224.138: bytes=1450 time=388ms TTL=119
Reply from 212.58.224.138: bytes=1450 time=387ms TTL=119
Reply from 212.58.224.138: bytes=1450 time=385ms TTL=119
Reply from 212.58.224.138: bytes=1450 time=384ms TTL=119
Reply from 212.58.224.138: bytes=1450 time=388ms TTL=119
Reply from 212.58.224.138: bytes=1450 time=387ms TTL=119
Reply from 212.58.224.138: bytes=1450 time=390ms TTL=119
Reply from 212.58.224.138: bytes=1450 time=386ms TTL=119
Reply from 212.58.224.138: bytes=1450 time=384ms TTL=119
Reply from 212.58.224.138: bytes=1450 time=390ms TTL=119
Reply from 212.58.224.138: bytes=1450 time=386ms TTL=119
Reply from 212.58.224.138: bytes=1450 time=377ms TTL=119
Reply from 212.58.224.138: bytes=1450 time=390ms TTL=119
Reply from 212.58.224.138: bytes=1450 time=381ms TTL=119
Reply from 212.58.224.138: bytes=1450 time=388ms TTL=119
Reply from 212.58.224.138: bytes=1450 time=377ms TTL=119
Reply from 212.58.224.138: bytes=1450 time=386ms TTL=119
Reply from 212.58.224.138: bytes=1450 time=382ms TTL=119
Reply from 212.58.224.138: bytes=1450 time=389ms TTL=119
Reply from 212.58.224.138: bytes=1450 time=392ms TTL=119
Reply from 212.58.224.138: bytes=1450 time=381ms TTL=119
Reply from 212.58.224.138: bytes=1450 time=383ms TTL=119
Reply from 212.58.224.138: bytes=1450 time=388ms TTL=119
Reply from 212.58.224.138: bytes=1450 time=382ms TTL=119

Ping statistics for 212.58.224.138:

    Packets: Sent = 37, Received = 36, Lost = 1 (2% loss),
Approximate round trip times in milli-seconds:
    Minimum = 376ms, Maximum = 392ms, Average = 385ms

Control-C
see the difference ?

P.S: this is 512K Ogero
oh mate yah i can send more packet but i mean how to know what is my Ms on wow ? lol am asking my friend to test for me before i get oger got my point
Lebscream, its weird how your traceroute goes through a private network after going out on the public network :D lol what the hell is that...
actually its not that wierd to have private in between public segments. often what that reffers to is that the connection is p2p hence, there arent any other segments or routes in between. the sad story as well often is, that such private segments that bridge connections could be hidden and not made vissible. its either that the segment routes and interconencts to other networks thru the private address or lack of knowledge of how to implement it properly. a bit of the same as not being able to register all router ip addresses with DNS.


what is really lame about that tracert is that it goes to the US and comes back to europe, but its not the worst that i have seen. i remember when i was in australia a while back and did a traceroute to two networks that i know reside in the same city, one went thru, asia-europe-usa, and the other went thru asia-usa, one had over 30 hops and the other had about 15. so major difference there, and the irony as well was that the one with less hops was slower!


rolf wroteLebscream, its weird how your traceroute goes through a private network after going out on the public network :D lol what the hell is that...
lol @ australia :) ... i think the internet needs a new routing protocol...
as for p2p, i thought that in this case they would create a tunnel. Thats what tunnels are for.
But I guess they have their reasons for setting up a route instead (and I hope ignorance is not one of them :D ).
It just looks weird on a traceroute...
Lebscream wrotewhat ?
That:
4 45 ms 48 ms 49 ms 192.168.111.2
is a private IP. Normally it only exists inside companies, houses, etc...
If you want, private IPs are like phone extensions inside a company, if you want to compare to phone system.
Some IP ranges - 192.168.xxx.xxx and 10.xxx.xxx.xxx (and there is at least one more range, but I forgot it) are reserved for use in private networks only, and shouldn not be accessible from the internet.
Private ip is ugly... when they are visible, and it is not your ISP.

Fact is, there is no need to put on router real ip. Mostly it must be on some routers just to help troubleshooting connection problems (for traceroute and ping). But because major providers do icmp throttling on backplane - sometimes even this reason becoming useless.