Latency Monitor

amkahal

Hi,
i suggest to use this post to monitor daily "Latency times" from all ISPs in lebanon.
we will ping two hosts everyday:
#1 195.50.120.69 : belongs to Level3 Network, AS3356 (London)
#2 12.118.94.97 : belongs to AT&T Network, AS7018 (somewhere in USA)
I chose these two hosts because probably these are two nodes which OGERO routes most of our internet traffic through them.

- you should ping with 0 bytes to achieve the minimum values. (ping -t 195.50.120.69 -l 0)
- give your ping a time of 3-5 min, to get an accurate minimum value, your connection should be near idle.
- you should post only the minimum values you've got.
- you should post in a way like this:

ISP: xxxxxx
195.50.120.69 : xxx ms OR #1:xxx ms
12.118.94.97 : xxx ms OR #2:xxx ms

I am waiting your results guys.

amkahal

ISP: Terranet
195.50.120.69 : 119 ms
12.118.94.97 : 179 ms

Kassem

ISP: Ogero
195.50.120.69 : 108 ms
12.118.94.97 : Request Timed Out

EDIT:
Trace route to the second address:

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

Tracing route to 12.118.94.97 over a maximum of 30 hops

1 2 ms 5 ms 2 ms 192.168.1.1
2 41 ms 46 ms 47 ms 77.42.129.26
3 44 ms 46 ms 40 ms 77.42.129.2
4 44 ms 46 ms 46 ms 192.168.101.2
5 127 ms 127 ms 127 ms so-5-0-3.edge1.london1.level3.net [212.113.12.10
5]
6 119 ms 120 ms 117 ms ae-34-52.ebr2.london1.level3.net [4.69.139.97]
7 189 ms 196 ms 189 ms ae-44-44.ebr1.newyork1.level3.net [4.69.137.78]

8 201 ms 196 ms 196 ms ae-81-81.csw3.newyork1.level3.net [4.69.134.74]

9 183 ms 185 ms 187 ms ae-3-89.edge3.NewYork1.Level3.net [4.68.16.145]

10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.

surfer12

ISP: VISP
195.50.120.69 : 102 ms
12.118.94.97 : 152 ms

belal

ISP: Ogero
195.50.120.69 : 118 ms
12.118.94.97 : Request Timed Out

Edit:
12.122.130.166 : Request Timed Out

XhacK

ISP: Sodetel Gaming Package 512
195.50.120.69: 93ms
12.118.94.97 : Request Timed Out

I guess the second blocked lebanon! :P

vengeance666

#1 : 109ms
#2 : 166ms

alot of packet loss ( request timeouts ) so i had to reping the #1 , and reping #2 like 10 times

amkahal

12.122.130.166 is an alternative for who get "timed out" on #2.

amkahal

It seems that the internet connection is stable today in lebanon :)

GreenM

ISP: Cyberia
195.50.120.69 : 366 ms
12.118.94.97 : 426 ms

crazy

Personal opinion:

I suggest making personal statistics for a month (can be more or less time period) and then post your result. Coz this is just spam...

amkahal

ISP: Terranet
195.50.120.69: 354 ms (routed on satellite after 11:00 AM)
12.118.94.97 : timed out

vengeance666

195.50.120.69 : minimum 110ms , maximum 130ms and average 118ms

12.118.94.97 : minimum 161ms , maximum 177ms and average 166ms

ISP : VISP..

kareem_nasser

The ISP IDM are blocking pinging ICMP. I guess we have discussed this before and the only way is to email them the domain and they'll ping it.

WizaRd

Everything is fried today in terms of online gaming. Starting at 8.30pm until now, unplayable!

I am on Ogero by the way.

amkahal

Please, can a terranet user with IP address (213.204.124.xxx) do a ping on 195.50.120.69, it seems they have a new route.

amkahal

8:00 PM >>
High Local latency between Terranet and me, ~400 ms
anyone are facing similar problems ?

kareem_nasser

I was able to ping though my ISP is IDM here:

Ping & Trace
Please download the following file on your desktop, extract it to then double click on ping&trace.bat to run it.
The result of the script will be saved in a new file named « result.txt » on C:\ directory
Please wait around 3 minutes for the script execution to be completed before proceeding with the other steps.

(Via IDM's Website)

My results:

Sat 01/22/2011  1:11:27.89 

Pinging 192.168.1.254 with 32 bytes of data:

Reply from 192.168.1.254: bytes=32 time=1ms TTL=64

Reply from 192.168.1.254: bytes=32 time<1ms TTL=64

Reply from 192.168.1.254: bytes=32 time<1ms TTL=64

Reply from 192.168.1.254: bytes=32 time<1ms TTL=64

Reply from 192.168.1.254: bytes=32 time<1ms TTL=64

Reply from 192.168.1.254: bytes=32 time<1ms TTL=64

Reply from 192.168.1.254: bytes=32 time<1ms TTL=64

Reply from 192.168.1.254: bytes=32 time<1ms TTL=64

Reply from 192.168.1.254: bytes=32 time<1ms TTL=64

Reply from 192.168.1.254: bytes=32 time<1ms TTL=64


Ping statistics for 192.168.1.254:

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

Approximate round trip times in milli-seconds:

    Minimum = 0ms, Maximum = 1ms, Average = 0ms


Pinging 194.126.26.66 with 32 bytes of data:

Reply from 194.126.26.66: bytes=32 time=44ms TTL=123

Reply from 194.126.26.66: bytes=32 time=43ms TTL=123

Reply from 194.126.26.66: bytes=32 time=44ms TTL=123

Reply from 194.126.26.66: bytes=32 time=45ms TTL=123

Reply from 194.126.26.66: bytes=32 time=44ms TTL=123

Reply from 194.126.26.66: bytes=32 time=43ms TTL=123

Reply from 194.126.26.66: bytes=32 time=44ms TTL=123

Reply from 194.126.26.66: bytes=32 time=44ms TTL=123

Request timed out.

Reply from 194.126.26.66: bytes=32 time=44ms TTL=123

Reply from 194.126.26.66: bytes=32 time=44ms TTL=123

Reply from 194.126.26.66: bytes=32 time=43ms TTL=123

Reply from 194.126.26.66: bytes=32 time=44ms TTL=123

Reply from 194.126.26.66: bytes=32 time=44ms TTL=123

Reply from 194.126.26.66: bytes=32 time=45ms TTL=123



Ping statistics for 194.126.26.66:

    Packets: Sent = 15, Received = 14, Lost = 1 (6% loss),

Approximate round trip times in milli-seconds:

    Minimum = 43ms, Maximum = 45ms, Average = 43ms



Tracing route to 194.126.26.66 over a maximum of 30 hops

  1     5 ms    99 ms    99 ms  192.168.1.254 

  2     *        *        *     Request timed out.

  3    44 ms    43 ms    43 ms  172.50.1.1 

  4   132 ms    91 ms   103 ms  10.0.1.6 

  5    45 ms    45 ms    44 ms  213.175.184.203 

  6    44 ms   129 ms    56 ms  194.126.26.66 

Trace complete.



Pinging 174.142.61.237 with 32 bytes of data:



Reply from 174.142.61.237: bytes=32 time=441ms TTL=104

Reply from 174.142.61.237: bytes=32 time=441ms TTL=104

Reply from 174.142.61.237: bytes=32 time=478ms TTL=104

Reply from 174.142.61.237: bytes=32 time=442ms TTL=104

Reply from 174.142.61.237: bytes=32 time=488ms TTL=104

Reply from 174.142.61.237: bytes=32 time=447ms TTL=104

Reply from 174.142.61.237: bytes=32 time=510ms TTL=104

Reply from 174.142.61.237: bytes=32 time=457ms TTL=104

Reply from 174.142.61.237: bytes=32 time=460ms TTL=104

Reply from 174.142.61.237: bytes=32 time=467ms TTL=104

Reply from 174.142.61.237: bytes=32 time=441ms TTL=104

Reply from 174.142.61.237: bytes=32 time=451ms TTL=104

Reply from 174.142.61.237: bytes=32 time=447ms TTL=104

Reply from 174.142.61.237: bytes=32 time=498ms TTL=104

Reply from 174.142.61.237: bytes=32 time=441ms TTL=104


Ping statistics for 174.142.61.237:

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

Approximate round trip times in milli-seconds:

    Minimum = 441ms, Maximum = 510ms, Average = 460ms



Tracing route to ip-174-142-61-237.static.privatedns.com [174.142.61.237]

over a maximum of 30 hops:


  1    15 ms   100 ms    99 ms  192.168.1.254 

  2     *        *        *     Request timed out.

  3    42 ms    44 ms    44 ms  172.50.1.1 

  4    42 ms    45 ms   125 ms  10.0.1.6 

  5    44 ms    43 ms    43 ms  213.175.184.193 

  6    43 ms    45 ms    43 ms  212.36.211.40 

  7     *        *        *     Request timed out.

  8     *      367 ms     *     195.50.120.69 

  9   363 ms   366 ms   381 ms  ae-34-52.ebr2.London1.Level3.net [4.69.139.97] 

 10   438 ms   450 ms   449 ms  ae-41-41.ebr1.NewYork1.Level3.net [4.69.137.66] 

 11   524 ms   461 ms   442 ms  ae-91-91.csw4.NewYork1.Level3.net [4.69.134.78] 

 12   444 ms   443 ms   439 ms  ae-92-92.ebr2.NewYork1.Level3.net [4.69.148.45] 

 13   563 ms   593 ms   519 ms  ae-5-5.car1.Montreal2.Level3.net [4.69.141.5] 

 14   718 ms   475 ms   546 ms  te6-2.cl-core05.level3.mtl.iweb.com [4.59.176.10] 

 15   442 ms   446 ms   556 ms  te8-2.v0708.cl-car08.mtl.iweb.com [67.205.127.126] 

 16   442 ms   526 ms   451 ms  ip-174-142-61-237.static.privatedns.com [174.142.61.237] 

Trace complete.