Poor Speeds And Dropouts

[#1]

So if I needed to replace my router what Wi-Fi router would you guys recommend in the £120 range?

[#2]

Adding some more information.

Had a couple pf periods over the last 24 hours where page loads slowed, failed to display properly and images failed to load.

Have also attached the log from my router. 

Not sure if any of this will be useful or not.

[#3]

@Anonymous , @Baldrick1 , @Dan_the_Van , @Mustrum I don't claim to be anywhere near an expert, but that log seems to indicate a local problem in the OPs home network?

Don't lke the D/S SNR either, but the WAN seems to be holding up - at the moment.

[#4]

@DerekW 

Is that the complete log file or have you edited some of it out?

The BQM graph which date does it represent?

Edit: my thinking is yesterday and today

Looking more carefully I see

2023-09-03 10:26:14 [6] Httpd: DNS 8.8.4.4 resolve a.root-servers.net succeed(0).

and a corresponding latency peak at around the same time in the graph, which could have been a disconnect.

The date/time resetting to 2016 would tend to agree with a line drop at 10:26

2016-01-01 00:01:33 [6] PPP: CHAP authentication succeeded
2016-01-01 00:01:33 [5] PPP: CHAP authentication succeeded
2016-01-01 00:01:33 [5] PPP: peer from calling number 14:7B:AC:B3:DD:19 authorized
2016-01-01 00:01:33 [5] PPP: local IP address 31.125.20.124
2016-01-01 00:01:33 [5] PPP: remote IP address 195.166.130.255
2016-01-01 00:01:33 [5] PPP: primary DNS address 212.159.6.10
2016-01-01 00:01:33 [5] PPP: secondary DNS address 212.159.6.9

[#5]

@Dan_the_Van 

The BMQ was set up yesterday, so yes the last 24 hours or so.

No I did not edit the log.

I did update the routers firmware as suggested yesterday and the log was cleared at that point

[#6]

Maybe I should mention that I do use Googles DNS and I also have a static IP

Those charts/logs etc. are gobbledygook to me

[#7]

I wonder whether it is worth moving whatever is plugged into "LAN1" and shifting the cable to another LAN port to see whether the log "link down" / "link up" notifications move to the new position,  if it does then perhaps try a different ethernet cable ?

Notice that "LAN2" goes "link up" but doesn't drop.  So it is more likely that whatever is causing the LAN drops is the thing connected to "LAN1" rather than the router (because that would likely cause all the LAN ports to glitch).

.

[#8]

@Anonymous 

I will give that a try - may even see if I have a spare cable lying around and just swap it out

[#9]

@Anonymous 

You may be onto something, switched ports and the same thing is happening, time to get a new ethernet cable and try that

[#10]

@DerekW @Anonymous 

Just remembered the TP-Link logs are in descending time ordered when exported so the oldest event of the log is at the top, plusnet hubs logs are are in reverse, newest at the top.

2023-09-03 10:38:36 [5] System: LAN1 link down
2023-09-03 10:38:38 [5] System: LAN1 link up 1000 mbps
2023-09-03 10:38:39 [5] System: LAN1 link down
2023-09-03 10:38:42 [5] System: LAN1 link up 1000 mbps
2023-09-03 10:38:57 [5] System: LAN1 link down
2023-09-03 10:39:00 [5] System: LAN1 link up 1000 mbps

So actually the LAN ports are show as going from down to up

HTH

Edit: what is connected to LAN2 ?

[#11]

@Anonymous 

So I have not changed the ethernet cable yet but things seem to have settled down somewhat, I will monitor things for the rest of the day.

Could it of been a faulty port on the router?

It it starts happening again I will switch out the cable, I may just do that anyway

[#12]

@Dan_the_Van 

LAN2 is my Ring alarm base station

[#13]

---

@DerekW wrote:

Could it of been a faulty port on the router?

It's not impossible, but I've experimented with a lot of routers, switches, and hubs over the last 20 years, and usually ALL the ports fail or become dysfunctional at the same time,  so probably not.

.

[#14]

Just thought I would ask as I have not changed out the ethernet cable yet and things "seem" to have settled down now it is plugged into a different LAN port.

I do not have a new cable on the way and will swap it out when it arrives

[#15]

Maybe it wasn't plugged in completely before, or you've disturbed some corrosion on the connector(s) by moving it ?

.