AX11000 Throttling speeds

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

AX11000 Throttling speeds

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
AX11000 Throttling speeds
AX11000 Throttling speeds
2023-11-29 15:08:34
Model: Archer AX11000  
Hardware Version: V1
Firmware Version: 1.3.4 Build 20230906 rel.74809(5553)

We recently upgraded from 600 MB service to 1GB (940 MB guaranteed). After the update, I still couldn't break 660 MB down. I had my ISP out to check and everything was good.

 

I contacted support and they suggested a factory reset. I completed the reset and even changed the wireless SSID and PW. EVERYTHING WAS GREAT for about 20 minutes. My average speed test from the onboard app was 936 MB. It hen dropped to the 600s again.

 

I checked the log and ALG had activated. I disabled the feature and speeds popped back up to 930's. I got the same results when I enabled the router's virus scan features.

 

I contacted support again [TKID231116036] and they tried an updated firmware. It didn't fix the issue and added a new one ( I couldn't acces the router via the web browser while USB devices were attached). So, I had them roll the firmware back  and just leave all of the security features disabled.

 

My memory usage is around 40%. I streamed 3 videos and barely broke 15% CPU utilization. The "Real time rates" shown in the router definately DO NOT indicate any heavy usage.

 

Has anyone experienced this and found a fix?

  2      
  2      
#1
Options
2 Reply
Re:AX11000 Throttling speeds
2023-12-05 00:01:09

  @JK-Jim 

did 1.3.4 Build 20230906 Rel 74809 work, curious. i have 

1.3.2 Build 20221128 rel.45807(5553)

and its working for me , so im looking at all issues happening after 1.3.2 45807... 

  0  
  0  
#2
Options
Re:AX11000 Throttling speeds
2023-12-05 03:34:42

  @bhowes 

It did not.

It resolved a random DNS issue that I had been having since the July update. They had installed a 20231115 version that did not resolve it either.

 

 - Jim

  0  
  0  
#3
Options