Router keeps losing internet connection

J_B

GunJack wrote: »

good result

Hmmm - just home from an evening out and ... no internet!


Ping to google and 8888 both failed
Ping to the router:-
C:\>ping 192.168.1.254

Pinging 192.168.1.254 with 32 bytes of data:
Reply from 192.168.1.254: bytes=32 time=5ms TTL=64
Reply from 192.168.1.254: bytes=32 time=9ms TTL=64
Reply from 192.168.1.254: bytes=32 time=2ms TTL=64
Reply from 192.168.1.254: bytes=32 time=1ms TTL=64

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

---

Stats as follows ...
Before reboot - no internet:-
6 - Uptime: 0 days 09:52:20
7 - Data rate: 848/5691
8 - Maximum data rate: 1020/4588
9 - Noise margin: 4.9/0.3
10 - Line attenuation: 25.6/50.0
12 - Data sent/received: 33.4M/575.7M

After reboot:-
6 - Uptime: 0 days 00:00:29
7 - Data rate: 848/5127
8 - Maximum data rate: 1024/5488
9 - Noise margin: 5.1/5.7
10 - Line attenuation: 25.3/49.5
12 - Data sent/received: 215.6K/505.0K

that

J_B wrote: »

Hmmm - just home from an evening out and ... no internet!


Ping to google and 8888 both failed
Ping to the router:-
C:\>ping 192.168.1.254

Pinging 192.168.1.254 with 32 bytes of data:
Reply from 192.168.1.254: bytes=32 time=5ms TTL=64
Reply from 192.168.1.254: bytes=32 time=9ms TTL=64
Reply from 192.168.1.254: bytes=32 time=2ms TTL=64
Reply from 192.168.1.254: bytes=32 time=1ms TTL=64

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

---

Stats as follows ...
Before reboot - no internet:-
6 - Uptime: 0 days 09:52:20
7 - Data rate: 848/5691
8 - Maximum data rate: 1020/4588
9 - Noise margin: 4.9/0.3
10 - Line attenuation: 25.6/50.0
12 - Data sent/received: 33.4M/575.7M

After reboot:-
6 - Uptime: 0 days 00:00:29
7 - Data rate: 848/5127
8 - Maximum data rate: 1024/5488
9 - Noise margin: 5.1/5.7
10 - Line attenuation: 25.3/49.5
12 - Data sent/received: 215.6K/505.0K

There is a big difference in noise margin figures, isp time again. I would suspect that noise is normally a line issue. The first two times I has something similar it was a bad connection on he overhead cable from the green box to the premises, but the final time they could not fix it, and of the opinion them calling in BT would cost them cash

I would also have a word with the neighbours and see what they get. While they may not get the exact same as you, it should not be far out especially at the bottom end even if they use a different isp, but obviously it will if they use fibre

https://www.ofcom.org.uk/phones-telecoms-and-internet/advice-for-consumers/problems/broadband-landline-faults

GunJack

J_B wrote: »

Hmmm - just home from an evening out and ... no internet!


Ping to google and 8888 both failed
Ping to the router:-
C:\>ping 192.168.1.254

Pinging 192.168.1.254 with 32 bytes of data:
Reply from 192.168.1.254: bytes=32 time=5ms TTL=64
Reply from 192.168.1.254: bytes=32 time=9ms TTL=64
Reply from 192.168.1.254: bytes=32 time=2ms TTL=64
Reply from 192.168.1.254: bytes=32 time=1ms TTL=64

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

---

Stats as follows ...
Before reboot - no internet:-
6 - Uptime: 0 days 09:52:20
7 - Data rate: 848/5691
8 - Maximum data rate: 1020/4588
9 - Noise margin: 4.9/0.3
10 - Line attenuation: 25.6/50.0
12 - Data sent/received: 33.4M/575.7M

After reboot:-
6 - Uptime: 0 days 00:00:29
7 - Data rate: 848/5127
8 - Maximum data rate: 1024/5488
9 - Noise margin: 5.1/5.7
10 - Line attenuation: 25.3/49.5
12 - Data sent/received: 215.6K/505.0K

You STILL have a line fault....as that said above it's ISP time...you need to tell them that your downstream SNRM keeps dropping to 1dB or less and causing disconnections. They need to get Openreach to sort it. It'll be hard if it's intermittent, but you need to stress this to the ISP who in turn need to stress it to OR.

Good luck

J_B

that wrote: »

I would also have a word with the neighbours and see what they get. While they may not get the exact same as you, it should not be far out especially at the bottom end even if they use a different isp, but obviously it will if they use fibre

Neighbours and Fibre are two things we don't have here!!!
One neighbour is 50yards, other two are 300 yds, then one mile!

GunJack wrote: »

You STILL have a line fault....as that said above it's ISP time...you need to tell them that your downstream SNRM keeps dropping to 1dB or less and causing disconnections. They need to get Openreach to sort it. It'll be hard if it's intermittent, but you need to stress this to the ISP who in turn need to stress it to OR.

Good luck

Will reply to the ticket ... again!


Thanks all

rexel

I had them same problem router would drop out bt fitted new hub 4 still same problem fitted master socket changed line from box on street to house same problem after al least 5 visit from bt. bt engineer changed over line from box in street to exchange problem fixed

J_B

J_B wrote: »

Will reply to the ticket ... again!

Well, at least they are quite proactive and they got back to me at 1pm

Dear Mr B
As per our conversation, we have placed a modify order to Pin your SNR to stop the connection dropping.


-Internal-
Placed Modify order to hard pin the SNR.
After checking RRT it appears that the lowest the SNR was dropping down to was 4db and this was when the drops were occurring.
the line was stable between 6-9
to prevent more drops this SNR has been hard pinned.

DoaM

DoaM wrote: »

Have you tried the quiet line test? (Corded, analogue phone plugged in to the test socket behind the master socket faceplate. Dial 17020 option 2 and listen ... the line should be absolutely silent [apart from the voice saying "Quiet Line Test"]; any crackles, squeaks etc. then you have a line fault which needs to be fixed - line faults can also affect broadband).

Did you overlook this post?

If the ISP is having to force the SNR to a higher value to maintain connection stability then it suggests that there is a line noise issue.

that

J_B wrote: »

Well, at least they are quite proactive and they got back to me at 1pm

Dear Mr B
As per our conversation, we have placed a modify order to Pin your SNR to stop the connection dropping.


-Internal-
Placed Modify order to hard pin the SNR.
After checking RRT it appears that the lowest the SNR was dropping down to was 4db and this was when the drops were occurring.
the line was stable between 6-9
to prevent more drops this SNR has been hard pinned.

[/QUOTE]
Mmmm...... I think you have a line/connection problem. The algorithm that detects this automatically downgrades the line snr in an attempt to make a stable connection.

I feel that setting this manually will mask the snr issue, and you will still have problems. Think the lazy asses do not want to contact BT.

Me, i would leave my pc overnight, install piginfoview from https://nirsoft.net/utils/multiple_ping_tool.html, set the ping to every 1 second and ping both bbc.co.uk and 8.8.8.8 and in the morning you should have 0 failed, but perhaps something booted overnight, but the %failed should be low, My average ping time for bbc and Google is 19ms minimum and 91ms maximum, rather than 200ms or above. on BBC i get a 9.94% failure rate, with a 1.3% failure on google after running it for 10 mins. There is also a beep on fail function that may keep you up all night

There is nothing like downloading real data though.

J_B

DoaM wrote: »

Did you overlook this post?

If the ISP is having to force the SNR to a higher value to maintain connection stability then it suggests that there is a line noise issue.

Sorry - will investigate later ...

J_B

Me, i would leave my pc overnight, install piginfoview from https://nirsoft.net/utils/multiple_ping_tool.html, set the ping to every 1 second and ping both bbc.co.uk and 8.8.8.8 and in the morning you should have 0 failed, but perhaps something booted overnight, but the %failed should be low, My average ping time for bbc and Google is 19ms minimum and 91ms maximum, rather than 200ms or above. on BBC i get a 9.94% failure rate, with a 1.3% failure on google after running it for 10 mins.


Well, there's probably a way of copying the data here, but not sure so ...
It's done nearly 1100 pings overnight (I left it on 30 seconds) and we've had one fail on each (0.09%)

One at 22.58, one at 00.56 and one at 02.15
Average times are 19/19/20
Minimum 14/14/15
Maximum 475/477/478