Cable Forum - View Single Post

Chrysalis · 25-06-2006, 11:46

its normal for ntl I think yeah, some lucky people wont have that varation, and for me it was much much worse I had spikes up to 3 figures.

Pinging ntlworld.com [212.250.162.47] with 32 bytes of data:

Reply from 212.250.162.47: bytes=32 time=17ms TTL=116
Reply from 212.250.162.47: bytes=32 time=17ms TTL=116
Reply from 212.250.162.47: bytes=32 time=17ms TTL=116
Reply from 212.250.162.47: bytes=32 time=17ms TTL=116
Reply from 212.250.162.47: bytes=32 time=17ms TTL=116
Reply from 212.250.162.47: bytes=32 time=17ms TTL=116
Reply from 212.250.162.47: bytes=32 time=17ms TTL=116
Reply from 212.250.162.47: bytes=32 time=17ms TTL=116
Reply from 212.250.162.47: bytes=32 time=17ms TTL=116
Reply from 212.250.162.47: bytes=32 time=17ms TTL=116
Reply from 212.250.162.47: bytes=32 time=17ms TTL=116
Reply from 212.250.162.47: bytes=32 time=17ms TTL=116
Reply from 212.250.162.47: bytes=32 time=18ms TTL=116
Reply from 212.250.162.47: bytes=32 time=17ms TTL=116
Reply from 212.250.162.47: bytes=32 time=17ms TTL=116
Reply from 212.250.162.47: bytes=32 time=16ms TTL=116
Reply from 212.250.162.47: bytes=32 time=17ms TTL=116
Reply from 212.250.162.47: bytes=32 time=18ms TTL=116
Reply from 212.250.162.47: bytes=32 time=16ms TTL=116
Reply from 212.250.162.47: bytes=32 time=17ms TTL=116
Reply from 212.250.162.47: bytes=32 time=17ms TTL=116
Reply from 212.250.162.47: bytes=32 time=16ms TTL=116
Reply from 212.250.162.47: bytes=32 time=16ms TTL=116

Ping statistics for 212.250.162.47:
Packets: Sent = 23, Received = 23, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 16ms, Maximum = 18ms, Average = 16ms

thats from nildram, but ntlworld.com is responding fine.

25-06-2006, 11:46	#9
Chrysalis cf.mega poster Join Date: Sep 2003 Posts: 12,050	Re: Is this normal .... its normal for ntl I think yeah, some lucky people wont have that varation, and for me it was much much worse I had spikes up to 3 figures. Pinging ntlworld.com [212.250.162.47] with 32 bytes of data: Reply from 212.250.162.47: bytes=32 time=17ms TTL=116 Reply from 212.250.162.47: bytes=32 time=17ms TTL=116 Reply from 212.250.162.47: bytes=32 time=17ms TTL=116 Reply from 212.250.162.47: bytes=32 time=17ms TTL=116 Reply from 212.250.162.47: bytes=32 time=17ms TTL=116 Reply from 212.250.162.47: bytes=32 time=17ms TTL=116 Reply from 212.250.162.47: bytes=32 time=17ms TTL=116 Reply from 212.250.162.47: bytes=32 time=17ms TTL=116 Reply from 212.250.162.47: bytes=32 time=17ms TTL=116 Reply from 212.250.162.47: bytes=32 time=17ms TTL=116 Reply from 212.250.162.47: bytes=32 time=17ms TTL=116 Reply from 212.250.162.47: bytes=32 time=17ms TTL=116 Reply from 212.250.162.47: bytes=32 time=18ms TTL=116 Reply from 212.250.162.47: bytes=32 time=17ms TTL=116 Reply from 212.250.162.47: bytes=32 time=17ms TTL=116 Reply from 212.250.162.47: bytes=32 time=16ms TTL=116 Reply from 212.250.162.47: bytes=32 time=17ms TTL=116 Reply from 212.250.162.47: bytes=32 time=18ms TTL=116 Reply from 212.250.162.47: bytes=32 time=16ms TTL=116 Reply from 212.250.162.47: bytes=32 time=17ms TTL=116 Reply from 212.250.162.47: bytes=32 time=17ms TTL=116 Reply from 212.250.162.47: bytes=32 time=16ms TTL=116 Reply from 212.250.162.47: bytes=32 time=16ms TTL=116 Ping statistics for 212.250.162.47: Packets: Sent = 23, Received = 23, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 16ms, Maximum = 18ms, Average = 16ms thats from nildram, but ntlworld.com is responding fine.