Sky ping, may be looking to change.

JoeF1

JoeF1

JoeF1

Soldato
Joined
12 Jun 2012
Posts
3,918
Location
West Yorkshire
Hey guys looking for your help here.

Iv been with sky 2 year and i am receiving 10MB internet and have never had any trouble with my ping. Always around 30-40 etc.

For the past two weeks it has been going crazy. I.e so ill be in a game playing fine etc then all of a sudden it will fly to 1500-2000 and stay there until i reset the router (sometimes it drops down but stays around 300).

I have rang sky and they cant so anything to help. They have done a line test which is showing its unstable but no errors.

Im thinking of swapping providers although im not in a fibre or cable area?

Any ideas on what the issue can be, and what providers would you recommend through the phone line. Thanks.
 
I was, had a gaming dongle. Now i have the onpower ethernet adapters which plugs into the wall units. This does the same, so i tried cable to the router. Still the same.

The ethernet power sockets gave me a 10 ping gain so i thought it was the wifi, clearly wrong.
 
In there currently. The weird thing is my connection download/upload remains perfect just the ping rockets.
 
Assuming your sure its not torrents left on, or some kind of P2P throttling issue, there are 3 realistic possibilities:

1.Problem with your router or micro filters - easiest to identify and resolve. Borrow a spare router from someone (Or buy one from a place with a liberal return policy) and swap out. If you have multiple micro filters, unplug everything except the router one. If that resolves it, start putting micro filters and phones back into the system until you find the one that breaks it.
2. Problem with your physical line. Only your ISP can identify/resolve this. Swapping ISP won't help sadly.
3. Problem at Skys end. Least likely (But not impossible) as others would probably be impacted. Either wait for sky to identify and resolve, or change ISPs.
 
Linkex said:
Assuming your sure its not torrents left on, or some kind of P2P throttling issue, there are 3 realistic possibilities:

1.Problem with your router or micro filters - easiest to identify and resolve. Borrow a spare router from someone (Or buy one from a place with a liberal return policy) and swap out. If you have multiple micro filters, unplug everything except the router one. If that resolves it, start putting micro filters and phones back into the system until you find the one that breaks it.
2. Problem with your physical line. Only your ISP can identify/resolve this. Swapping ISP won't help sadly.
3. Problem at Skys end. Least likely (But not impossible) as others would probably be impacted. Either wait for sky to identify and resolve, or change ISPs.
Click to expand...

1. Cant do any other routers skys stupid policy on using their own routers wont let me set up a third party one.

2. Iv contacted them and they are insisting there is no faults on the line. But by the time it rises and i ring them, im on hold that long the lines stabilized.

There are no torrents etc, just gaming on this machine. Even turned steam off etc

Thanks.
 
JoeF1 said:
1. Cant do any other routers skys stupid policy on using their own routers wont let me set up a third party one.
Click to expand...

Plug one in to try it, they cant find out unless there testing it.

i had a similar problem and it turned out to be the router,which i changed to an old Lyksys one i had.
incidentally sky will want around 40 quid for a replacement :rolleyes:
 
MilanoChris said:
Post your router stats and some traceroutes to affected sites.
Click to expand...

ADSL Link Downstream Upstream
Connection Speed 10239 kbps 606 kbps
Line Attenuation 23.5 dB 1.6 dB
Noise Margin 8.4 dB 18.5 dB


_lecro_ said:
Plug one in to try it, they cant find out unless there testing it.

i had a similar problem and it turned out to be the router,which i changed to an old Lyksys one i had.
incidentally sky will want around 40 quid for a replacement :rolleyes:
Click to expand...

Physically cant plug it in, because sky hold your username and PW. I know theres ways of getting them, although i have the only router which isnt listed on said site. Just my luck.
 
If they are certain it is not an issue at their end, then the only option is a replacement router. If they are going to be dicks about which router you can use, then they are choosing to make it their problem, so they will need to provide it. I would phone customer service and demand a replacement be sent out immediately.
 
Okay so its doing it right now, here are some pings

Microsoft Windows [Version 6.2.9200]
(c) 2012 Microsoft Corporation. All rights reserved.

ping pingtest.net

Pinging pingtest.net [74.209.160.10] with 32 bytes of data:
Reply from 74.209.160.10: bytes=32 time=1759ms TTL=53
Reply from 74.209.160.10: bytes=32 time=1897ms TTL=53
Reply from 74.209.160.10: bytes=32 time=2227ms TTL=53
Reply from 74.209.160.10: bytes=32 time=1944ms TTL=53

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

>ping bbc.co.uk

Pinging bbc.co.uk [212.58.241.131] with 32 bytes of data:
Reply from 212.58.241.131: bytes=32 time=1418ms TTL=246
Reply from 212.58.241.131: bytes=32 time=2413ms TTL=246
Reply from 212.58.241.131: bytes=32 time=2059ms TTL=246
Reply from 212.58.241.131: bytes=32 time=2228ms TTL=246

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

Microsoft Windows [Version 6.2.9200]
(c) 2012 Microsoft Corporation. All rights reserved.

>ping pingtest.net

Pinging pingtest.net [74.209.160.10] with 32 bytes of data:
Reply from 74.209.160.10: bytes=32 time=1759ms TTL=53
Reply from 74.209.160.10: bytes=32 time=1897ms TTL=53
Reply from 74.209.160.10: bytes=32 time=2227ms TTL=53
Reply from 74.209.160.10: bytes=32 time=1944ms TTL=53

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

>ping bbc.co.uk

Pinging bbc.co.uk [212.58.241.131] with 32 bytes of data:
Reply from 212.58.241.131: bytes=32 time=1418ms TTL=246
Reply from 212.58.241.131: bytes=32 time=2413ms TTL=246
Reply from 212.58.241.131: bytes=32 time=2059ms TTL=246
Reply from 212.58.241.131: bytes=32 time=2228ms TTL=246

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

>ping overclockers.co.uk

Pinging overclockers.co.uk [91.151.218.10] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 91.151.218.10:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

f>ping forums.overclockers.co.uk

Pinging forums.overclockers.co.uk [91.151.218.11] with 32 bytes of data:
Request timed out.

Ping statistics for 91.151.218.11:

>ping google.co.uk

Pinging google.co.uk [74.125.132.94] with 32 bytes of data:
Reply from 74.125.132.94: bytes=32 time=3406ms TTL=49
Reply from 74.125.132.94: bytes=32 time=3575ms TTL=49
Request timed out.
Reply from 74.125.132.94: bytes=32 time=3388ms TTL=49

Ping statistics for 74.125.132.94:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 3388ms, Maximum = 3575ms, Average = 3456ms
 
Microsoft Windows [Version 6.2.9200]
(c) 2012 Microsoft Corporation. All rights reserved.

>tracert www.bbc.co.uk

Tracing route to www.bbc.net.uk [212.58.244.70]
over a maximum of 30 hops:

1 7 ms 73 ms 6 ms SkyRouter.Home [192.168.0.1]
2 867 ms 1023 ms 865 ms 5ad71fbe.bb.sky.com [90.215.31.190]
3 * * * Request timed out.
4 1770 ms 1789 ms 1598 ms te0-0-0-3.pr0.bllon.ov.easynet.net [89.200.135.1
66]
5 1698 ms 1603 ms 1528 ms 02780863.bb.sky.com [2.120.8.99]
6 1910 ms 2125 ms 1932 ms ntl-ge2-9.prt0.rbsov.bbc.co.uk [212.58.238.189]

7 * * * Request timed out.
8 * * * Request timed out.
9 2193 ms 2110 ms 2238 ms ae0.er01.telhc.bbc.co.uk [132.185.254.109]
10 2270 ms 1961 ms 2262 ms 132.185.255.148
11 1440 ms 2072 ms 1862 ms bbc-vip115.telhc.bbc.co.uk [212.58.244.70]

Trace complete.



Apologies.
 
According to your downstream attenuation of 23.5dB you should be getting around 19Mbit.

Upstream attenuation is generally around half of the downstream attenuation, but in your case it's way off.

As an estimate based on your upstream your line is just a few hundred metres long but if we go by the downstream it's 1700M.

Your upstream speed is lower than you'd expect for a short line.

Not sure whether you can trust this information provided by the router though but it certainly shows some conflicts.

What router is it?
Netgear? Sagem?
Are you connected my MER or PPPoA?
 
The router is a sagem F@ST2504n (the grey top, black/blue bottom) one.

It is a MER connection.

Thanks.
 
Ah MER is a bit of a pain. Not sure if there's a way to spoof MAC addresses and get a third party router connected via MER.

So the slow latency might not be related to the line and more to do with Sky'd network but I'd certainly be concerned with your stats.

If you are getting that in the test socket then it might be worth monitoring the line speed with routerststatslite and look for changes in noise margin and errors, if it supports your router. I can't help thinking that you may have an issue with your line, possibly with the lower end of the frequency range. It could have course be a problem with your router and for this reason I might be tempted to shove any old asdl modem router on the line and compare Sync rates and noise margins between the two. You won't be able to get a PPP session with an alternate router but it should Sync with the exchange ok.

Also do all the usual stuff like swapping microfilters, testing without a telephone or other voiceband device on the line. Just basically make sure you aren't causing the drop in expected speeds and you can get Openreach out to investigate. Just because Sky say there isn't a problem doesn't mean there is no problem.
 
Last edited:
As I've said I think this is a router (modem specifically) issue, you really need to try another one. If it doesn't clear the fault I'd be booking a fault out to Openrech via Sky to get the line checked.
 
You must log in or register to reply here.
Back
Top Bottom