ER605 Router CPU Spikes to 100% and Causes Internet Disruption + Heartbeat Misses
ER605 Router CPU Spikes to 100% and Causes Internet Disruption + Heartbeat Misses

Hello,
I’ve been encountering an issue with my TP-Link ER605 router in my Omada network setup. Over the last two Friday nights, the internet connection at my site went down completely. After investigating, I noticed that the router's CPU usage spikes to 100% before the issue occurs. The router then freezes, and all devices in the network lose internet access. I also occasionally see "heartbeat miss" notifications, though they seem to occur before the CPU spike. Rebooting the router temporarily restores the internet connection, but the issue happens again the following Friday.
Details:
- Router: TP-Link ER605
- Setup: Omada network
- Problem: For the last two Friday nights, the internet has gone down completely. The CPU usage spikes to 100% before the router freezes, causing a loss of internet access. After the issue, I see the disconnection, and rebooting restores the internet. Occasionally, I also see "heartbeat miss" notifications. The problem reoccurs every Friday night.
- Troubleshooting attempts: I’ve rebooted the router and checked for any firmware updates. The problem happens even when there are no significant changes in network usage (such as heavy traffic or large downloads). The router is running the latest firmware version.
Question:
Has anyone encountered similar issues with the ER605, particularly with CPU usage spiking to 100% and causing disconnections and heartbeat misses? What could be causing the CPU usage to hit 100% on Fridays, and how can I prevent this from happening? Any advice on how to fix this issue or specific settings to check would be greatly appreciated.
Thank you!
Hello,
I’ve been encountering an issue with my TP-Link ER605 router in my Omada network setup. Over the last two Friday nights, the internet connection at my site went down completely. After investigating, I noticed that the router's CPU usage spikes to 100% before the issue occurs. The router then freezes, and all devices in the network lose internet access. I also occasionally see "heartbeat miss" notifications, though they seem to occur before the CPU spike. Rebooting the router temporarily restores the internet connection, but the issue happens again the following Friday.
Details:
- Router: TP-Link ER605
- Setup: Omada network
- Problem: For the last two Friday nights, the internet has gone down completely. The CPU usage spikes to 100% before the router freezes, causing a loss of internet access. After the issue, I see the disconnection, and rebooting restores the internet. Occasionally, I also see "heartbeat miss" notifications. The problem reoccurs every Friday night.
- Troubleshooting attempts: I’ve rebooted the router and checked for any firmware updates. The problem happens even when there are no significant changes in network usage (such as heavy traffic or large downloads). The router is running the latest firmware version.
Question:
Has anyone encountered similar issues with the ER605, particularly with CPU usage spiking to 100% and causing disconnections and heartbeat misses? What could be causing the CPU usage to hit 100% on Fridays, and how can I prevent this from happening? Any advice on how to fix this issue or specific settings to check would be greatly appreciated.
Thank you!
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Im experiencing the same issue.
Omada Cloud
WAN FNT -> patch terminal 1
Patch Terminal 1 -> Gateway WAN port 1
- Gateway/Router: ER605v2 rel.82712
Gateway LAN port 2 -> Switch port 1
- Switch: SG1005P
Switch port 2 -> patch terminal 3
Patch terminal 3 -> EAP235-Wall WAN (1st Floor)
EAP235-Wall Port 2 -> 1 wired device
Switch port 3 -> patch terminal 4
Patch terminal -> EAP236-Wall WAN (2nd Floor)
EAP235-Wall Port 2 -> SG105 (4 wired devices)
~ 35 wireless devices
1 SSID
1 VLAN
First time in TPLink support forums; please let me know anything add'l needed, or proper decorum here.
thanks!
- Copy Link
- Report Inappropriate Content
Hi @TreyW
Thanks for posting in our business forum.
TreyW wrote
Im experiencing the same issue.
Omada Cloud
WAN FNT -> patch terminal 1Patch Terminal 1 -> Gateway WAN port 1
- Gateway/Router: ER605v2 rel.82712
Gateway LAN port 2 -> Switch port 1
- Switch: SG1005P
Switch port 2 -> patch terminal 3
Patch terminal 3 -> EAP235-Wall WAN (1st Floor)
EAP235-Wall Port 2 -> 1 wired device
Switch port 3 -> patch terminal 4
Patch terminal -> EAP236-Wall WAN (2nd Floor)
EAP235-Wall Port 2 -> SG105 (4 wired devices)
~ 35 wireless devices
1 SSID
1 VLAN
First time in TPLink support forums; please let me know anything add'l needed, or proper decorum here.
thanks!
What's your firmware version?
We have not located the reason for this. And it is basically impossible to locate, as you reboot the router, the log would be flushed as well.
You can try to reset the router and re-adopt it again.
Omada Cloud is not a proper way to say if it is a Cloud-based Controller(CBC). Or you mean the cloud access of a local controller.
- Copy Link
- Report Inappropriate Content
2.2.6 Build 20240718 Rel.82712
Omada Cloud Essentials
I was able to grab logs while the processor was being maxx'd out; happy to provide, just need to know where/how.
Appearances are this is related to a SNMP bug bc I'm seeing "bsalg: parser failed" repeat hundreds of times, and no SNMP walking in my environment.
- Copy Link
- Report Inappropriate Content
Hi @TreyW
Thanks for posting in our business forum.
TreyW wrote
2.2.6 Build 20240718 Rel.82712
Omada Cloud Essentials
I was able to grab logs while the processor was being maxx'd out; happy to provide, just need to know where/how.
Appearances are this is related to a SNMP bug bc I'm seeing "bsalg: parser failed" repeat hundreds of times, and no SNMP walking in my environment.
You can paste the log here but remove the stuff like MAC address or your public IP address.
SNMP? Do you even enable it on your device? Config status?
SNMP should not work unless you configure and set it.
CPU is maxed out, but it does not specify the reasons. It only matches the symptom you see now, which is 100% CPU usage and dead.
- Copy Link
- Report Inappropriate Content
I've PM'd you the password to the diag dump attached to this post from the gateway. At the exact moment the dump occurred, the CPU was not pegged (per the TOP output in the diag), but in the UI, I'd been seeing a pegged CPU for the past few moments when I generated the diag.
No, I do not have SNMP enabled.
Just found that your PM are locked down. Feel free to PM me and I'll provide, or I can spend some time later redacting all of the logs.
- Copy Link
- Report Inappropriate Content

Information
Helpful: 0
Views: 570
Replies: 15
Voters 0
No one has voted for it yet.