Cable Forum - View Single Post - Can you post ping plotter image please to IP address 82.133.85.65

AmAtoL · 06-02-2008, 21:13

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Paul>ping 82.133.85.65 -n 20
Pinging 82.133.85.65 with 32 bytes of data:
Reply from 82.133.85.65: bytes=32 time=16ms TTL=53
Reply from 82.133.85.65: bytes=32 time=22ms TTL=53
Reply from 82.133.85.65: bytes=32 time=17ms TTL=53
Reply from 82.133.85.65: bytes=32 time=50ms TTL=53
Reply from 82.133.85.65: bytes=32 time=24ms TTL=53
Reply from 82.133.85.65: bytes=32 time=22ms TTL=53
Reply from 82.133.85.65: bytes=32 time=18ms TTL=53
Reply from 82.133.85.65: bytes=32 time=19ms TTL=53
Reply from 82.133.85.65: bytes=32 time=42ms TTL=53
Reply from 82.133.85.65: bytes=32 time=17ms TTL=53
Reply from 82.133.85.65: bytes=32 time=57ms TTL=53
Reply from 82.133.85.65: bytes=32 time=15ms TTL=53
Reply from 82.133.85.65: bytes=32 time=18ms TTL=53
Reply from 82.133.85.65: bytes=32 time=29ms TTL=53
Reply from 82.133.85.65: bytes=32 time=52ms TTL=53
Reply from 82.133.85.65: bytes=32 time=18ms TTL=53
Reply from 82.133.85.65: bytes=32 time=14ms TTL=53
Reply from 82.133.85.65: bytes=32 time=20ms TTL=53
Reply from 82.133.85.65: bytes=32 time=18ms TTL=53
Reply from 82.133.85.65: bytes=32 time=24ms TTL=53
Ping statistics for 82.133.85.65:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 14ms, Maximum = 57ms, Average = 25ms

That's mine from Stockport, a bit up and down, which tells more of a story than the average time at the end. A spread of over 40 isn't real good. A stable 40 is ok and a stable 14 is ok, just the up and down we can't get along with.

06-02-2008, 21:13	#23
AmAtoL Inactive Join Date: Jul 2005 Location: Stockport Services: 20 meg BB , 3 Samsung STB's, Landline, 4 Mobiles, V+ Box, UK Online 8 Meg Posts: 244	Re: Can you post ping plotter image please to IP address 82.133.85.65 Microsoft Windows XP [Version 5.1.2600] (C) Copyright 1985-2001 Microsoft Corp. C:\Documents and Settings\Paul>ping 82.133.85.65 -n 20 Pinging 82.133.85.65 with 32 bytes of data: Reply from 82.133.85.65: bytes=32 time=16ms TTL=53 Reply from 82.133.85.65: bytes=32 time=22ms TTL=53 Reply from 82.133.85.65: bytes=32 time=17ms TTL=53 Reply from 82.133.85.65: bytes=32 time=50ms TTL=53 Reply from 82.133.85.65: bytes=32 time=24ms TTL=53 Reply from 82.133.85.65: bytes=32 time=22ms TTL=53 Reply from 82.133.85.65: bytes=32 time=18ms TTL=53 Reply from 82.133.85.65: bytes=32 time=19ms TTL=53 Reply from 82.133.85.65: bytes=32 time=42ms TTL=53 Reply from 82.133.85.65: bytes=32 time=17ms TTL=53 Reply from 82.133.85.65: bytes=32 time=57ms TTL=53 Reply from 82.133.85.65: bytes=32 time=15ms TTL=53 Reply from 82.133.85.65: bytes=32 time=18ms TTL=53 Reply from 82.133.85.65: bytes=32 time=29ms TTL=53 Reply from 82.133.85.65: bytes=32 time=52ms TTL=53 Reply from 82.133.85.65: bytes=32 time=18ms TTL=53 Reply from 82.133.85.65: bytes=32 time=14ms TTL=53 Reply from 82.133.85.65: bytes=32 time=20ms TTL=53 Reply from 82.133.85.65: bytes=32 time=18ms TTL=53 Reply from 82.133.85.65: bytes=32 time=24ms TTL=53 Ping statistics for 82.133.85.65: Packets: Sent = 20, Received = 20, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 14ms, Maximum = 57ms, Average = 25ms That's mine from Stockport, a bit up and down, which tells more of a story than the average time at the end. A spread of over 40 isn't real good. A stable 40 is ok and a stable 14 is ok, just the up and down we can't get along with.