topic Re: Asus BE19000AI issue after last firmware in Networking

Asus BE19000AI issue after last firmware

ghostman88ro — Sun, 05 Apr 2026 08:28:17 GMT

Hello, I have bought a ROG Rapture GT-BE19000AI about 2 weeks ago and after latest firmware 3.0.0.6.102_40480 I can see that the interface works better and multiple fixes are in place, however there is a bug on ISP and the internet starts to lag a lot and suddenly it doesn't work anymore. There aren't any red lights on it, I can connect to it but the internet is not working (all my devices are going down) and I have to reboot it. It happens like every day mostly. Also reboot doesn't work from the web interface when this thing happens and can only be done using the mobile app.

Could this be investigated?

Re: Asus BE19000AI issue after last firmware

ghostman88ro — Sun, 05 Apr 2026 08:31:13 GMT

To be more cleared, I am using a PPPoE connection and tried to switch between the DNS's provided by the router but it doesn't do anything. Currently I am using the default one.

Re: Asus BE19000AI issue after last firmware

Stevenx80 — Mon, 06 Apr 2026 01:50:04 GMT

I’m going through the same problem after this update on 3-31 I got to reset the router and continue my show or movie like every hour or so it’s so annoying the devices start to slow down and that’s when u know it’s about to just disconnect from the internet I hope they find a fix quick I hope that’s all it is this router wasn’t cheap lol

Re: Asus BE19000AI issue after last firmware

jzchen — Mon, 06 Apr 2026 17:13:12 GMT

I had about the same time problem with a bad Ethernet cable. So I am not sure if my advice may help...

Try reinstalling the firmware version. For me:

I manually installed the prior version.

Then I used the check for update option on the Web GUI, to find and update to the latest. (I assume the ASUS Router App would also do this just fine).

While this is exactly what I did, you might try just manually installing the latest right over the same version....

Re: Asus BE19000AI issue after last firmware

ghostman88ro — Mon, 06 Apr 2026 19:45:52 GMT

Thank you for the advice. For the cable I am using a cat8.1 of 0.5m which is from the fiber device to the router, which is fine, no issues there as it is mostly as new. I have tried replacing the firmware but it does the same. I've did this before writing the mesage. I thought maybe something is triggering it, like I don't know a streaming movie, youtube, etc. but no.. out of nowhere everything is getting disconnected and you have to restart it. Today for example I've let me PC opened uploading something and no issue so far. So confusing.. 🙄

Re: Asus BE19000AI issue after last firmware

jzchen — Mon, 06 Apr 2026 20:01:11 GMT

If you just recently switched to Cat 8 I'm afraid, go get the prior cable and swap it just in case. I just got a free replacement from the manufacturer of mine and I just did not try it. (They were very responsive so I asked for a replacement instead of refund)...

EDIT- Maybe 26 AWG is too thin, (which is what I saw they use for Cat 8. I think the typical is 24 AWG)...

Re: Asus BE19000AI issue after last firmware

ghostman88ro — Tue, 07 Apr 2026 12:57:42 GMT

I am using this cat 8.1 since 2022. These are its specs:

Premium 8.1 category patch network cable
Channel Cat.8 Class I tested ISO11801
Each cable comes with test report
Application: 40G Base-T, PoE +, PoE ++
Cable: 4 x 2 x 26/7 AWG copper cable
Shielding: total braided shielding, metal foil pairs (PiMF)
Cable: LSZH sheath, outer diameter 6.2 mm
Connector: RJ45, shielded, 50µ gold-plated contacts
Cable color: light gray RAL 7035
Length: 0.5 m

There were no issues with it as it stays perfectly into the port and also hadn't been bent. Prior to this router I had the RT-BE92U which didn't had any issues with it. There were other software issues there, but that is another story. Now its being used in mesh and everything is ok.
It's not because of the cable and as I can see, the new firmware for BE19000AI has been removed from ASUS website.

Re: Asus BE19000AI issue after last firmware

jzchen — Tue, 07 Apr 2026 13:02:46 GMT

Thank you for clarifying and the heads up on firmware being removed.

I was unlucky and switching around cables at the same time, mine was clearly an issue with the cable, connected specifically to the BGW320-500 5 Gb Ethernet and the 2.5 Gb Ethernet port of the BE19000Ai. The BE92U has a 10 Gb port do you think the incompatibility/defect stems from 2.5 Gb link rate in my case?

Re: Asus BE19000AI issue after last firmware

ghostman88ro — Tue, 07 Apr 2026 19:31:50 GMT

In my case I am using always the largers ports, in these case 10 gb, on BE19000AI and BE92U (from 1 gb port of my ZTE ont-fiber converter device to 10 gb router's port). Even though I don't have a 10gb connection, not even 2.5 or 5 I always prefer those ones.

I don't think its an issues on your side, but you could try to switch to that port just to make a test. You could reset the router and keep the same name of the network and password so that everything that is connected now will connect again back, that way its easier to test and keep the devices binded without connecting them 1 by 1 again.

Also as a mention and off the record thing for BE92U, it had almost identical issues like BE19000AI. If you unplug it from the power socket or you perform restarts to it, it will break, like you'll see a red light on WAN and no internet. It would required a factory reset and reconfigure from scratch to have internet again and be able to access it otherwise you'll see a popup with tryng to connect to internet. I've done at least 7 firmware updates to that one and still no fix for this ugly bug. On the mesh side, it doesn't fail that often (at least 3 consecutive restarts can be done and it doesn't require factory reset :)) )

Re: Asus BE19000AI issue after last firmware

jzchen — Tue, 07 Apr 2026 21:03:32 GMT

First I swapped the LAN cable to the LAN 6 10 Gb port (10 Gb to the other 10 Gb port). I connected the new Cat 8 cable to the 10Gb port that was vacated. I went to my computer and logged in, went to -> Settings -> WAN -> Dual WAN and changed from 2.5 G to 10 G port. After clicking Apply it asks to confirm. I click OK and rush to the Ai router, unplug the end from the BGW320-500 gateway 5 G port, plugged in the new cable, and waited as it restarted.... Eventually the WAN LED changed from RED to White, (or is that a light shade of blue?). So since it is 5 G on one end and 10 G on the other the PHY should be 5 Gbps, and everything (at least with the new cable is okay).

Re: Asus BE19000AI issue after last firmware

jzchen — Tue, 07 Apr 2026 21:18:57 GMT

I have AiProtection partially on. Current signature 2.500. So Advertisements blocking and Trackers blocking are off. Do you know how long the DHCP Lease is from your ISP? (I'm actually not able to find it on the new web GUI of the BE19000AI router). I typically make the LAN DHCP server the exact same amount of time (in seconds as it requires). Also have you tried changing the WAN DHCP Query Frequency?

Re: Asus BE19000AI issue after last firmware

jzchen — Wed, 08 Apr 2026 01:13:16 GMT

I just saw the WAN LED is red, but service is still okay both IPv4 and IPv6 traceroute works...

Re: Asus BE19000AI issue after last firmware

ghostman88ro — Wed, 08 Apr 2026 06:12:54 GMT

The lease time can be found under SETTINGS > LAN > DHCP SERVER tab > LEASE TIME (seconds) in that page.

For AI Protection I have all of them on, with the same signature at version 2500. Default lease time on mine is set to 86400 and I didn't changed anything.

I didn't do any changes to WAN DHCP Query Frequency. The only thing that I've set to default is DNS Server as I've used to have google or adblock but after the latest bugged firmware it disconnects my internet.

Apart from these I've let most on them default for now as I saw that it didn't disconnected for 3 days, even though I am using the firmware which was removed from their site.

The part with WAN LED being on red might be a bug, you could try to restart it to see if it goes to white. I had that issue with BE92U as it had all sorts of anomalies like I've mentioned before.

Re: Asus BE19000AI issue after last firmware

jzchen — Wed, 08 Apr 2026 11:21:01 GMT

I used to have aDSL service and it was type PPPoE. With PPPoE you have a login credentials user and password something like that. There is a time/Lease time/DHCP Lease time from the WAN side. It is actually set by the ISP and you can not change it. I am using Automatic type but I selected PPPoE to open up the menu. I will put a box around the setting. It is actually controlled by the ISP. The default of 0 means that the router will not disconnect from the PPPoE/WAN connection, BUT I prefer to copy the ISP given time. Because the router may think it kept the connection open but the ISP already disconnect.... All ISPs set a DHCP lease time unless you have a static IPv4 Address. I also copy this time to the LAN DHCP Lease time which you reference.

Re: Asus BE19000AI issue after last firmware

jzchen — Wed, 08 Apr 2026 11:33:22 GMT

The definition of this time is the amount of time the ISP sees zero traffic before it disconnects your PPPoE connection.

If you set the router setting to 0, this means the router will try to keep this connection open, by sending out traffic before that time runs out.

For my Automatic this means sending out a DHCP Query before 1/2 the DHCP Lease is used. (This is the WAN DHCP Lease controlled by the ISP). Similar to PPPoE, there is a disconnect and the IP address will be released at the end of the Lease to the pool for others to use. To sort of transfer this knowledge to my LAN clients I copy it over to the LAN DHCP Lease time, which is completely your choice. ISP does not have any control what you put there...

Re: Asus BE19000AI issue after last firmware

jzchen — Wed, 08 Apr 2026 11:37:13 GMT

Back to the 0 setting. So your router is trying to keep the PPPoE connection open forever. But the ISP controls when it disconnects. Sometimes the ISP will ignore the Lease Time and disconnect you anyways, because it sees you are trying to keep the connection open forever, and it is trying to release your connection when you don't really need it. When it disconnects BUT your router believes it has kept the connection open, that may be when you notice you lost service.

Re: Asus BE19000AI issue after last firmware

jzchen — Wed, 08 Apr 2026 14:48:49 GMT

This is the WAN "Lease time" setting I am talking about, under Advanced Settings -> Network Map -> (Globe image to left of "Internet status"

on the right side column near the bottom:

Re: Asus BE19000AI issue after last firmware

ghostman88ro — Wed, 08 Apr 2026 19:34:50 GMT

Indeed on that interface is there but on the new one of BE19000AI it appears that is under Settings - > LAN

And that is the value default from it which I didn't changed

Re: Asus BE19000AI issue after last firmware

jzchen — Wed, 08 Apr 2026 21:34:40 GMT

There are two settings, one for the WAN side, and one for the LAN side. WAN is default "0". LAN is default "86400". What I suggest is finding out what the time the ISP gives, then change both of those to the same. Since my ISP shows 30 minutes, I change LAN DHCP from 86400 to 1800 seconds. So the client devices know when the ISP might drop the connection, because the router DHCP server will drop the local connection. PPPoE started with Dial-Up which I am afraid I am so old that I used dial-up for the internet first. Back then there was a wonderful browser I think called Mosaic.....

Re: Asus BE19000AI issue after last firmware

jzchen — Wed, 08 Apr 2026 21:30:10 GMT

So the modems/routers back then also had firmware. The WAN setting you could set any amount of time, or "0", which meant the modem/router would try to keep the connection open until you disconnect/log out manually. Both my friend and I had the exact same modem. I copied the ISP setting, my (greedy little) friend chose "0". There was a firmware update. We both downloaded it to our modems. All of a sudden his Internet stopped working. His would dial up, but never establish connection. Mine was fine, because I copied the ISP setting. (I vaguely remember 15 mins). I told him to change it because the connecting bug in the new firmware was to disconnect at 0 seconds, so immediately after connecting.