Results 11 to 20 of 25
bad pings
This is a discussion on bad pings within the Sky Broadband help forums, part of the Sky Broadband help and support category; Didn't notice that. It's fine if you are in NI....
- 20-07-11, 12:57 PM #11
Re: bad pings
Didn't notice that. It's fine if you are in NI.
Advertisement- 20-07-11, 04:03 PM #12
- 27-07-11, 12:32 AM #13
Re: bad pings
Ok so my speed after the 10 or so days is this:
DownStream Connection Speed 4177 kbps
UpStream Connection Speed 797 kbps
VPI 0
VCI 40
My ping to the BBC website is 54.
I am not happy with this ping cause I can't play on my favourite servers anymore.
What can I do thanks.
- 27-07-11, 12:35 AM #14
Re: bad pings
Run a few tests on the speedtest.net site and see what the ping is like.
I find that running several consecutive tests to the same server can help at times. It also helps to do them at different times of the day.
You are looking for a pattern to see not just one result, but a collection.
PlusNet Fibre since Jan 2021
Previously Sky Fibre & Sky BB since 2010.
- 27-07-11, 12:38 PM #15
Re: bad pings
Try pinging your Gateway address, this will show whether the lag is down to your distance from London or some other reason. You will find this under the ADSL Port in your Router Status.
Have you asked Sky to put you on a Gamer profile?
TomD
Please note the views and recommendations in my posts are my own and in no way reflect the views of SkyUser.
Useful Utilites
https://www.nirsoft.net/utils/wifi_information_view.html/ TCPOptimiser /Test Socket
Note - When downloading always select the Custom install or you will end up with stuff you don't want.
- 30-07-11, 06:06 PM #16
Re: bad pings
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
H:\Documents and Settings\>ping 90.209.247.62
Pinging 90.209.247.62 with 32 bytes of data:
Reply from 90.209.247.62: bytes=32 time=57ms TTL=63
Reply from 90.209.247.62: bytes=32 time=56ms TTL=63
Reply from 90.209.247.62: bytes=32 time=55ms TTL=63
Reply from 90.209.247.62: bytes=32 time=55ms TTL=63
Ping statistics for 90.209.247.62:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 55ms, Maximum = 57ms, Average = 55ms
So now what??
- 30-07-11, 11:35 PM #17
Re: bad pings
Something is seriously wrong, you appear to bee pinging your own IP address. If so the result should be 0-1ms. Could be you are on SVBN and are pinging your main server. Are you on SVBN?
Try pinging your router at 192.168.0.1.
TomD
Please note the views and recommendations in my posts are my own and in no way reflect the views of SkyUser.
Useful Utilites
https://www.nirsoft.net/utils/wifi_information_view.html/ TCPOptimiser /Test Socket
Note - When downloading always select the Custom install or you will end up with stuff you don't want.
- 01-08-11, 02:17 AM #18
Re: bad pings
1Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
H:\Documents and Settings\>ping 192.168.0.1
Pinging 192.168.0.1 with 32 bytes of data:
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Ping statistics for 192.168.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
H:\Documents and Settings\>
That is me pinging the router the other was my gateway thing that the other guy said i should ping.
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
H:\Documents and Settings\Ben lee>ping 192.168.0.1
Pinging 192.168.0.1 with 32 bytes of data:
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Ping statistics for 192.168.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
H:\Documents and Settings\>ping 90.209.247.62
Pinging 90.209.247.62 with 32 bytes of data:
Reply from 90.209.247.62: bytes=32 time=49ms TTL=63
Reply from 90.209.247.62: bytes=32 time=49ms TTL=63
Reply from 90.209.247.62: bytes=32 time=49ms TTL=63
Reply from 90.209.247.62: bytes=32 time=49ms TTL=63
Ping statistics for 90.209.247.62:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 49ms, Maximum = 49ms, Average = 49ms
H:\Documents and Settings\>
Gateway address.
Also My last ISP (Utility warehouse) pinged the BBC at 25 MS had a faster download but much slower upload.
MY question is: Why would my ping shoot up to more then double what is was when all they did was change me over to sky who use the same infrastructure (i think anyway)
- 01-08-11, 02:50 AM #19
Re: bad pings
your first hop sucks for fastpath there's some mild interleaving going on there
or impulse noise protection
fastpath would give you something like this
1 0.256 ms 0.242 ms 0.225 ms
2 7.882 ms 7.475 ms 7.339 ms
3 4.321 ms 4.605 ms 4.426 ms
4 9.384 ms 9.327 ms 9.821 ms
5 11.618 ms 11.238 ms 11.275 msLast edited by Shonk; 01-08-11 at 03:10 AM.
- 01-08-11, 11:58 AM #20
Re: bad pings
That is me pinging the router the other was my gateway thing that the other guy said i should ping.
I can see you are on Sky's SVBN and don't have a 'local' gateway as such, your connection is routed directly to the Sky servers in Scotland.
Have you asked Sky to put you on a gamer profile or reduce your delay?
TomD
Please note the views and recommendations in my posts are my own and in no way reflect the views of SkyUser.
Useful Utilites
https://www.nirsoft.net/utils/wifi_information_view.html/ TCPOptimiser /Test Socket
Note - When downloading always select the Custom install or you will end up with stuff you don't want.