sky ping with or without max delay reduced

Hi ya can some of u sky users / sky gamers post your sky pings times with and / or without the max delay reduced? please PLEASE make sure the ping time you post is from a PC connected to the router VIA an ethernet cable NOT wireless as wireless adds 10-20ms onto your ping times.....

Many thanks

Angel_Rex

Sky MID with Max_Delay at 8.

C:\Documents and Settings\Yasin>ping clarity.jolt.co.uk -n 10

Pinging clarity.jolt.co.uk [195.149.21.11] with 32 bytes of data:

Reply from 195.149.21.11: bytes=32 time=27ms TTL=57
Reply from 195.149.21.11: bytes=32 time=29ms TTL=57
Reply from 195.149.21.11: bytes=32 time=28ms TTL=57
Reply from 195.149.21.11: bytes=32 time=28ms TTL=57
Reply from 195.149.21.11: bytes=32 time=27ms TTL=57
Reply from 195.149.21.11: bytes=32 time=28ms TTL=57
Reply from 195.149.21.11: bytes=32 time=27ms TTL=57
Reply from 195.149.21.11: bytes=32 time=28ms TTL=57
Reply from 195.149.21.11: bytes=32 time=28ms TTL=57
Reply from 195.149.21.11: bytes=32 time=28ms TTL=57

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

C:\Documents and Settings\Yasin>

Taking Yaz's lead...

Sky Max with Max_Delay at 8

Pinging clarity.jolt.co.uk [195.149.21.11] with 32 bytes of data:

Reply from 195.149.21.11: bytes=32 time=25ms TTL=57
Reply from 195.149.21.11: bytes=32 time=25ms TTL=57
Reply from 195.149.21.11: bytes=32 time=25ms TTL=57
Reply from 195.149.21.11: bytes=32 time=25ms TTL=57
Reply from 195.149.21.11: bytes=32 time=26ms TTL=57
Reply from 195.149.21.11: bytes=32 time=25ms TTL=57
Reply from 195.149.21.11: bytes=32 time=25ms TTL=57
Reply from 195.149.21.11: bytes=32 time=25ms TTL=57
Reply from 195.149.21.11: bytes=32 time=25ms TTL=57
Reply from 195.149.21.11: bytes=32 time=25ms TTL=57

Ping statistics for 195.149.21.11:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 25ms, Maximum = 26ms, Average = 25ms.co.uk

That's from up near Leeds. Previous to reducing my Max Delay last week, my ping would have been about 36-38ms.

Nice one, cheers guys^^ Think i will prob order broadband through sky now I am on BT and like their pings even with interleaving i get 22-25ms (fastpath was 12-14ms). �5 sky BB is a steal 30 days till contract ends with BT then im a sky_boy

Any other ping times appreciated!!

What makes you say wireless adds 10-20ms to ping times?
The highest I've pinged to my router wirelessly is 3ms and thats not even a perfect signal.

Cheers.

i'm on Sky Max, get about 8mb only.

Before i got my delay reduced i used to get between 35-40ms pings, now i get:

D:\Documents and Settings\Zub>ping jolt.co.uk

Pinging jolt.co.uk [82.133.85.65] with 32 bytes of data:

Reply from 82.133.85.65: bytes=32 time=23ms TTL=57
Reply from 82.133.85.65: bytes=32 time=23ms TTL=57
Reply from 82.133.85.65: bytes=32 time=23ms TTL=57
Reply from 82.133.85.65: bytes=32 time=24ms TTL=57

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

Its defo worth the call to get sky to have it reduced, just a REAL hassle trying to get the tier one idiots to transfer you to tier 3 *sigh*

emunix@emunix-desktop:~$ ping  www.jolt.co.uk

PING www.jolt.co.uk (82.133.85.65) 56(84) bytes of data.

64 bytes from www.jolt.co.uk (82.133.85.65): icmp_seq=1 ttl=57 time=38.8 ms

64 bytes from www.jolt.co.uk (82.133.85.65): icmp_seq=2 ttl=57 time=29.5 ms

64 bytes from www.jolt.co.uk (82.133.85.65): icmp_seq=3 ttl=57 time=30.4 ms

64 bytes from www.jolt.co.uk (82.133.85.65): icmp_seq=4 ttl=57 time=28.5 ms

64 bytes from www.jolt.co.uk (82.133.85.65): icmp_seq=5 ttl=57 time=30.2 ms

64 bytes from www.jolt.co.uk (82.133.85.65): icmp_seq=6 ttl=57 time=29.1 ms

64 bytes from www.jolt.co.uk (82.133.85.65): icmp_seq=7 ttl=57 time=29.4 ms

64 bytes from www.jolt.co.uk (82.133.85.65): icmp_seq=8 ttl=57 time=29.4 ms

64 bytes from www.jolt.co.uk (82.133.85.65): icmp_seq=9 ttl=57 time=29.7 ms

64 bytes from www.jolt.co.uk (82.133.85.65): icmp_seq=10 ttl=57 time=29.0 ms

64 bytes from www.jolt.co.uk (82.133.85.65): icmp_seq=11 ttl=57 time=29.1 ms

A little higher than when I were with Bulldog or Pipex but not too bad, on Max product with max_delay reduced to 8ms (or so they say as it was all done by email)

it depends on the router, i think there are some generic results out there and i believe adslguide cover, in some of their routers reviews, the ping increase on wifi.

It also depends on the wifi card or device your using. My ping hard wired is 22ms, my DELL laptop pings at 38ms both through CMD both on the same connection.

Pings look ok to me a few ms higher, are they much higher than ur older isp? looks good to me, consider me a converted man^^

Not surprisingly about 8-10ms due to the max_delay setting.

Sky Max with max delay set to 8

$ ping jolt.co.uk -c 10
PING jolt.co.uk (82.133.85.65) 56(84) bytes of data.
64 bytes from secure.jolt.co.uk (82.133.85.65): icmp_seq=1 ttl=57 time=21.8 ms
64 bytes from secure.jolt.co.uk (82.133.85.65): icmp_seq=2 ttl=57 time=21.5 ms
64 bytes from secure.jolt.co.uk (82.133.85.65): icmp_seq=3 ttl=57 time=21.9 ms
64 bytes from secure.jolt.co.uk (82.133.85.65): icmp_seq=4 ttl=57 time=21.2 ms
64 bytes from secure.jolt.co.uk (82.133.85.65): icmp_seq=5 ttl=57 time=21.0 ms
64 bytes from secure.jolt.co.uk (82.133.85.65): icmp_seq=6 ttl=57 time=21.7 ms
64 bytes from secure.jolt.co.uk (82.133.85.65): icmp_seq=7 ttl=57 time=22.0 ms
64 bytes from secure.jolt.co.uk (82.133.85.65): icmp_seq=8 ttl=57 time=21.8 ms
64 bytes from secure.jolt.co.uk (82.133.85.65): icmp_seq=9 ttl=57 time=22.1 ms
64 bytes from secure.jolt.co.uk (82.133.85.65): icmp_seq=10 ttl=57 time=21.2 ms

--- jolt.co.uk ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 8998ms
rtt min/avg/max/mdev = 21.051/21.671/22.159/0.363 ms

Pings were 10ms higher before getting max delay reduced.