Weird Latency

Aly

Hello

I usually try "ping" and "tracert" commands in Windows command prompt when I am bored just to see my latencies and it has always been 450-550 ms almost to all websites except my ping to idm.net.lb it was 40ms because IDM is my ISP.
well today I was bored and entered the cmd and started to ping some major sites like bbc.co.uk and google and yahoo and youtube and idm etc.... and I had pretty surprising results :

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

D:\Documents and Settings\Administrator>ping bbc.co.uk

Pinging bbc.co.uk [212.58.224.138] with 32 bytes of data:

Reply from 212.58.224.138: bytes=32 time=127ms TTL=107
Reply from 212.58.224.138: bytes=32 time=110ms TTL=107
Reply from 212.58.224.138: bytes=32 time=105ms TTL=107
Request timed out.

Ping statistics for 212.58.224.138:
    Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
    Minimum = 105ms, Maximum = 127ms, Average = 114ms

D:\Documents and Settings\Administrator>ping google.com

Pinging google.com [74.125.53.100] with 32 bytes of data:

Reply from 74.125.53.100: bytes=32 time=107ms TTL=41
Reply from 74.125.53.100: bytes=32 time=124ms TTL=41
Reply from 74.125.53.100: bytes=32 time=108ms TTL=41
Reply from 74.125.53.100: bytes=32 time=119ms TTL=41

Ping statistics for 74.125.53.100:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 107ms, Maximum = 124ms, Average = 114ms

D:\Documents and Settings\Administrator>ping yahoo.com

Pinging yahoo.com [69.147.114.224] with 32 bytes of data:

Reply from 69.147.114.224: bytes=32 time=117ms TTL=47
Reply from 69.147.114.224: bytes=32 time=98ms TTL=47
Reply from 69.147.114.224: bytes=32 time=97ms TTL=47
Reply from 69.147.114.224: bytes=32 time=128ms TTL=47

Ping statistics for 69.147.114.224:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 97ms, Maximum = 128ms, Average = 110ms

D:\Documents and Settings\Administrator>ping nba.com

Pinging nba.com [157.166.255.10] with 32 bytes of data:

Request timed out.

Ping statistics for 157.166.255.10:
    Packets: Sent = 1, Received = 0, Lost = 1 (100% loss),
Control-C
^C
D:\Documents and Settings\Administrator>ping idm.net.lb

Pinging idm.net.lb [193.188.135.50] with 32 bytes of data:

Reply from 193.188.135.50: bytes=32 time=11ms TTL=123
Reply from 193.188.135.50: bytes=32 time=10ms TTL=123
Reply from 193.188.135.50: bytes=32 time=20ms TTL=123
Reply from 193.188.135.50: bytes=32 time=17ms TTL=123

Ping statistics for 193.188.135.50:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 10ms, Maximum = 20ms, Average = 14ms

D:\Documents and Settings\Administrator>ping visp.net.lb

Pinging visp.net.lb [88.85.65.133] with 32 bytes of data:

Reply from 88.85.65.133: bytes=32 time=83ms TTL=50
Reply from 88.85.65.133: bytes=32 time=80ms TTL=50
Reply from 88.85.65.133: bytes=32 time=78ms TTL=50
Reply from 88.85.65.133: bytes=32 time=95ms TTL=50

Ping statistics for 88.85.65.133:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 78ms, Maximum = 95ms, Average = 84ms

D:\Documents and Settings\Administrator>ping ogero.gov.lb

Pinging ogero.gov.lb [77.42.130.37] with 32 bytes of data:

Request timed out.

Ping statistics for 77.42.130.37:
    Packets: Sent = 1, Received = 0, Lost = 1 (100% loss),
Control-C
^C
D:\Documents and Settings\Administrator>ping lebgeeks.com

Pinging lebgeeks.com [209.20.78.40] with 32 bytes of data:

Reply from 209.20.78.40: bytes=32 time=119ms TTL=38
Reply from 209.20.78.40: bytes=32 time=126ms TTL=38
Reply from 209.20.78.40: bytes=32 time=111ms TTL=38
Reply from 209.20.78.40: bytes=32 time=165ms TTL=38

Ping statistics for 209.20.78.40:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 111ms, Maximum = 165ms, Average = 130ms

D:\Documents and Settings\Administrator>

Then I restarted my computer and router because maybe it was a sort of bug or something and I tried again :

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

D:\Documents and Settings\Administrator>ping youtube.com

Pinging youtube.com [74.125.45.100] with 32 bytes of data:

Reply from 74.125.45.100: bytes=32 time=126ms TTL=41
Reply from 74.125.45.100: bytes=32 time=122ms TTL=41
Reply from 74.125.45.100: bytes=32 time=143ms TTL=41
Reply from 74.125.45.100: bytes=32 time=117ms TTL=41

Ping statistics for 74.125.45.100:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 117ms, Maximum = 143ms, Average = 127ms

D:\Documents and Settings\Administrator>ping bbc.co.uk

Pinging bbc.co.uk [212.58.224.138] with 32 bytes of data:

Reply from 212.58.224.138: bytes=32 time=80ms TTL=107
Reply from 212.58.224.138: bytes=32 time=97ms TTL=107
Reply from 212.58.224.138: bytes=32 time=86ms TTL=107
Reply from 212.58.224.138: bytes=32 time=86ms TTL=107

Ping statistics for 212.58.224.138:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 80ms, Maximum = 97ms, Average = 87ms

D:\Documents and Settings\Administrator>ping google.com

Pinging google.com [74.125.45.100] with 32 bytes of data:

Reply from 74.125.45.100: bytes=32 time=138ms TTL=41
Reply from 74.125.45.100: bytes=32 time=121ms TTL=41
Reply from 74.125.45.100: bytes=32 time=108ms TTL=41
Reply from 74.125.45.100: bytes=32 time=86ms TTL=41

Ping statistics for 74.125.45.100:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 86ms, Maximum = 138ms, Average = 113ms

D:\Documents and Settings\Administrator>ping lebgeeks.com

Pinging lebgeeks.com [209.20.78.40] with 32 bytes of data:

Reply from 209.20.78.40: bytes=32 time=107ms TTL=38
Reply from 209.20.78.40: bytes=32 time=105ms TTL=38
Reply from 209.20.78.40: bytes=32 time=101ms TTL=38
Reply from 209.20.78.40: bytes=32 time=101ms TTL=38

Ping statistics for 209.20.78.40:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 101ms, Maximum = 107ms, Average = 103ms

D:\Documents and Settings\Administrator>ping idm.net.lb

Pinging idm.net.lb [193.188.135.50] with 32 bytes of data:

Reply from 193.188.135.50: bytes=32 time=25ms TTL=123
Reply from 193.188.135.50: bytes=32 time=29ms TTL=123
Reply from 193.188.135.50: bytes=32 time=8ms TTL=123
Reply from 193.188.135.50: bytes=32 time=9ms TTL=123

Ping statistics for 193.188.135.50:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 8ms, Maximum = 29ms, Average = 17ms

D:\Documents and Settings\Administrator>ping bbc.co.uk

Pinging bbc.co.uk [212.58.224.138] with 32 bytes of data:

Reply from 212.58.224.138: bytes=32 time=106ms TTL=107
Reply from 212.58.224.138: bytes=32 time=106ms TTL=107
Reply from 212.58.224.138: bytes=32 time=80ms TTL=107
Reply from 212.58.224.138: bytes=32 time=77ms TTL=107

Ping statistics for 212.58.224.138:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 77ms, Maximum = 106ms, Average = 92ms

D:\Documents and Settings\Administrator>

My average ping to IDM was 40 ms and now is 17 ms and my average. ping to any other website was as I said 450-550 ms and now I am getting pretty low ping on like an average of 92 ms on bbc.co.uk or 127 ms with youtube and that's really wierd because last time (2 weeks ago) I pinged to youtube it was about 463ms, but the most funny thing is that my latency in online gaming is still the same 450-550 ms.

My question :
The thing i posted above is some kind of an illusion or something meaningless ? or not precise ? IDM are know to have very bad latencies but this now is weird, video streaming is now faster than before but why the hell the ping is very low when I ping those sites in cmd and it is still as high as before in online gaming ?

Thank you :D

Kareem

Traceroute pls ?

Aly

I saved those traceroutes at that time :

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

D:\Documents and Settings\Administrator>tracert -d bbc.co.uk

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

  1    22 ms    30 ms    29 ms  192.168.1.254
  2    12 ms    12 ms    12 ms  10.151.144.1
  3    14 ms    14 ms    16 ms  172.50.1.4
  4    12 ms    12 ms    12 ms  10.0.1.26
  5    17 ms    21 ms    17 ms  213.175.184.193
  6    14 ms    12 ms    17 ms  212.36.211.33
  7     *        *        *     Request timed out.
  8   137 ms   131 ms   121 ms  12.118.94.93
  9   125 ms   121 ms   125 ms  12.122.130.166
 10   130 ms   138 ms   140 ms  12.122.130.29
 11   139 ms   135 ms   168 ms  192.205.34.54
 12   130 ms   131 ms   127 ms  80.91.248.145
 13   124 ms   128 ms   130 ms  80.91.248.202
 14   145 ms   143 ms   146 ms  80.91.249.170
 15   152 ms   142 ms   129 ms  213.248.104.70
 16   130 ms   139 ms   136 ms  212.58.238.133
 17   128 ms   143 ms   147 ms  212.58.224.138

Trace complete.

D:\Documents and Settings\Administrator>ping bbc.co.uk

Pinging bbc.co.uk [212.58.224.138] with 32 bytes of data:

Reply from 212.58.224.138: bytes=32 time=145ms TTL=107
Reply from 212.58.224.138: bytes=32 time=134ms TTL=107
Reply from 212.58.224.138: bytes=32 time=143ms TTL=107
Reply from 212.58.224.138: bytes=32 time=129ms TTL=107

Ping statistics for 212.58.224.138:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 129ms, Maximum = 145ms, Average = 137ms

D:\Documents and Settings\Administrator>tracert -d google.com

Tracing route to google.com [74.125.53.100]
over a maximum of 30 hops:

  1    26 ms    31 ms    30 ms  192.168.1.254
  2    14 ms    13 ms    13 ms  10.151.144.1
  3    46 ms    38 ms    38 ms  172.50.1.4
  4    20 ms    30 ms    34 ms  10.0.1.26
  5    46 ms    40 ms    49 ms  213.175.184.193
  6    18 ms    20 ms    20 ms  212.36.211.33
  7     *        *        *     Request timed out.
  8   143 ms   124 ms   150 ms  12.118.94.97
  9   156 ms   149 ms   167 ms  12.122.131.166
 10   147 ms   150 ms   151 ms  12.122.1.2
 11   173 ms   169 ms   150 ms  12.122.31.130
 12   173 ms   142 ms   141 ms  12.122.146.153
 13   149 ms   153 ms   158 ms  12.89.209.14
 14   169 ms   177 ms   173 ms  209.85.249.34
 15   173 ms   182 ms   162 ms  209.85.250.126
 16   146 ms   145 ms   151 ms  216.239.48.34
 17   180 ms     *      442 ms  64.233.174.123
 18   527 ms   333 ms   160 ms  72.14.232.6
 19   165 ms   171 ms   178 ms  74.125.53.100

Trace complete.

D:\Documents and Settings\Administrator>ping google.com

Pinging google.com [74.125.53.100] with 32 bytes of data:

Reply from 74.125.53.100: bytes=32 time=168ms TTL=41
Reply from 74.125.53.100: bytes=32 time=183ms TTL=41
Reply from 74.125.53.100: bytes=32 time=182ms TTL=41
Reply from 74.125.53.100: bytes=32 time=199ms TTL=41

Ping statistics for 74.125.53.100:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 168ms, Maximum = 199ms, Average = 183ms

D:\Documents and Settings\Administrator>

belal

That's because i left IDM to ogero!lol but i admit online gaming(ps3) is working like a charm.

rolf

Did some research, see below...

Aly wroteMicrosoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

D:\Documents and Settings\Administrator>tracert -d bbc.co.uk

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

LOCAL
1 22 ms 30 ms 29 ms 192.168.1.254
2 12 ms 12 ms 12 ms 10.151.144.1
3 14 ms 14 ms 16 ms 172.50.1.4
4 12 ms 12 ms 12 ms 10.0.1.26
IDM (Source: RIPE)
5 17 ms 21 ms 17 ms 213.175.184.193
6 14 ms 12 ms 17 ms 212.36.211.33
??
7 * * * Request timed out.
AT&T WorldNet Services ATT (Source: APNIC)
8 137 ms 131 ms 121 ms 12.118.94.93
9 125 ms 121 ms 125 ms 12.122.130.166
10 130 ms 138 ms 140 ms 12.122.130.29
AT&T Services, Inc (Source: APNIC)
11 139 ms 135 ms 168 ms 192.205.34.54
TeliaSonera International Carrier (Source: RIPE)
12 130 ms 131 ms 127 ms 80.91.248.145
13 124 ms 128 ms 130 ms 80.91.248.202
14 145 ms 143 ms 146 ms 80.91.249.170
TeliaSonera International Carrier (Source: RIPE)
15 152 ms 142 ms 129 ms 213.248.104.70
16 130 ms 139 ms 136 ms 212.58.238.133
17 128 ms 143 ms 147 ms 212.58.224.138

Trace complete.

Kareem

C:\Documents and Settings\be1mk307>ping 74.125.53.100

Pinging 74.125.53.100 with 32 bytes of data:

Reply from 74.125.53.100: bytes=32 time=103ms TTL=51
Reply from 74.125.53.100: bytes=32 time=109ms TTL=51
Reply from 74.125.53.100: bytes=32 time=110ms TTL=51
Reply from 74.125.53.100: bytes=32 time=108ms TTL=51

...

elchebib

This is really weird Aly.
Gotta try the ping and traceroute once I get back home to check it out....

nuclearcat

Can you try please
https://www.whatismyip.com/
Just interesting what is real ip address they are using

nourberro

elchebib wroteThis is really weird Aly.
Gotta try the ping and traceroute once I get back home to check it out....

@ elchebib fell free to welcome your self in the ( new member introductions)

elchebib

I don't know Aly on what link were you put by IDM when you got those numbers but these are my results:

Ping has started ...

PING bbc.co.uk (212.58.224.138): 56 data bytes
64 bytes from 212.58.224.138: icmp_seq=0 ttl=114 time=457.192 ms
64 bytes from 212.58.224.138: icmp_seq=1 ttl=114 time=453.078 ms
64 bytes from 212.58.224.138: icmp_seq=2 ttl=114 time=448.552 ms
64 bytes from 212.58.224.138: icmp_seq=3 ttl=114 time=446.121 ms

--- bbc.co.uk ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max/stddev = 446.121/451.236/457.192/4.250 ms

Aly

@ Rolf thanks for taking the time to do a search about resolving those IPs and as far as I know TeliaSonera is the major fiber optic network that links Europe to America and it must be a wicked fast network imo.

Kareem wroteC:\Documents and Settings\be1mk307>ping 74.125.53.100

Pinging 74.125.53.100 with 32 bytes of data:

Reply from 74.125.53.100: bytes=32 time=103ms TTL=51
Reply from 74.125.53.100: bytes=32 time=109ms TTL=51
Reply from 74.125.53.100: bytes=32 time=110ms TTL=51
Reply from 74.125.53.100: bytes=32 time=108ms TTL=51

...

Yes man your pings are low but you are with Ogero and ogero has the lowest ping, but as for me I have been with IDM for more than a year and during this time I have learned that IDM and Low pings are 2 words that will never fit together :P

nuclearcat wroteCan you try please
https://www.whatismyip.com/
Just interesting what is real ip address they are using

During all this time with IDM I always had an IP starting like that : 193.127.X.Y and I used to also check it on whatismyip.com but now my IP has changed it is now : 212.36.208.14

PS: with IDM there is like 1000 person that share this public IP, I have about 5 friends subscribed with IDM some live near me and others live also within Beirut but geographically far from me and they also have the same public IP.

elchebib wroteThis is really weird Aly.
Gotta try the ping and traceroute once I get back home to check it out....

IDM is your ISP too ? because your ping shown above is considered very low (in leb).

elchebib

This is really weird Aly.
Gotta try the ping and traceroute once I get back home to check it out....
IDM is your ISP too ? because your ping shown above is considered very low (in leb).
Yes, IDM is my ISP and I have had these pings since the first days I got my DSL connection.
Should they be lower than that? What could be the problem?

nuclearcat

Aly are you sure you check https:// ? Because if u do http - most probably you will see ip of proxy

Aly

Oh all the time when I checked my IP on whatismyip.com I used to do it with http, and I guess I never tried https so I guess nothing changed with my, and now I understood why when I pressed the link in your previous post Mozilla prompted me a message to enter on my own risk and required a certification, anyway here is it :

https :

http:

Kareem

Yeah IDM ips. But on some Ogero IPs i get a reply on google ~ 110ms and on the other 200ms.. Teo told me it was load balancing.

nuclearcat

Well this ip is routed over satellite
km33232 ~ # tracepath 212.36.208.14
1: km33232 (84.19.190.72) 0.093ms pmtu 1500
1: h-87.118.112.1.keyweb.de (87.118.112.1) 0.688ms
1: h-87.118.112.1.keyweb.de (87.118.112.1) 0.440ms
2: vl4006.c6500c1.keyweb.de (95.169.160.45) 0.504ms
3: decix-peer.zebra.lt (80.81.192.161) 36.958ms asymm 4
4: 213-190-60-93.telecom.lt (213.190.60.93) 37.058ms asymm 5
5: satgatege2-gw.zebra.lt (213.190.49.195) 37.249ms
6: 77.94.34.134.satgate.net (77.94.34.134) 37.254ms << satellite ISP starts here
7: 192.168.228.1 (192.168.228.1) 37.664ms
8: no reply
9: 194.126.24.17 (194.126.24.17) 398.632ms asymm 16
10: 212.36.211.37 (212.36.211.37) 416.327ms asymm 16
11: 194.126.21.135 (194.126.21.135) 396.918ms asymm 17
12: no reply
13: no reply
14: no reply

I guess they route ping only over fiber
Let me do similar... because some customers really believe ping is key in measuring backbone quality.

I will try to do application which will catch which ip they use for ping

rolf

lol
It makes sense, but technically ping is supposed to be used for testing connectivity, so if it is routed differently then it looses any technical utility. You may use another kind of ping/echo internally for troubleshooting connectivity.
Ping will become a measure of "how fast we could route your packets if you were paying millions".

BTW, you can send data in pings (and i think it does by default), so this can actually be exploited, if someone is willing to write the proper code.

nuclearcat

http://www.cs.uit.no/~daniels/PingTunnel/

BashLogic

nuclearcat wrotehttp://www.cs.uit.no/~daniels/PingTunnel/

heheh :) good old pingtunnel, i remember when i had to fend that 10years ago :)

battikh

rolf wrotebut technically ping is supposed to be used for testing connectivity, so if it is routed differently then it looses any technical utility.

technically, no 2 packets HAVE to take the same path. 2 consecutive packets from the same flow can take different routes depending on many factors. that's the way routing has been designed.
ping is used to test reachability, so whatever route it takes, it still serves its purpose.