Question if i should buy this router or not

Question if i should buy this router or not

Question if i should buy this router or not
Question if i should buy this router or not
2024-08-23 02:21:46
Tags: #Question
Model: Archer AX55   Archer AX6000  
Hardware Version: V1
Firmware Version:

I’m deciding between the TP-Link Archer AX55 and the Archer AX6000. I don’t have a strict budget, so I could purchase either or both if needed.

I’ve had the Archer AX55 before, but it frequently disconnected randomly, with downtime lasting up to a minute before reconnecting. Given that I have many devices connected to my network and live in a densely packed neighborhood with interconnected houses, I’m concerned that this might be contributing to the issues.

Given these challenges, should I stick with the AX55 or upgrade to the Archer AX6000, even though it’s an older model?

  0      
  0      
#1
Options
1 Reply
Re:Question if i should buy this router or not
2024-08-23 13:12:13

  @Lordalpha 

 

If it were me, I would spend a bit of time trying to see if I can find the cause of the issue as it may be not the router.

 

Is firmware up to date,

 

Do you lose both WIFI and Ethernet? If so then the issue could be with something other than the router.

 

Do the logs (modem and router if they have them) show anything at the time of the failure?

 

At the time of the fail, what are the lights on the modem and router doing differenty than normal operation.

 

Are you using an UPS? Is the battery in it good? Does it support both the modem and the router? Power surge/brown out affects electronic equipment in many different ways.

 

Did the issue start when new devices were added to the system?

 

If you are using a cable company that also provides TV, did anything change there such add or remove TVs?

 

Are you using the USB ports on the router? Try without them attached.

 

Try disconnecting each Eithernet device to see if one of them is causing an issue.

 

If you get another router, get it from someone with a good return policy in case you still have the same issue. 

 

 

 

  0  
  0  
#2
Options