MikroTik CPU at 100%: How to Find the Cause and Fix It
Find out what is using your MikroTik router's CPU with the Profile tool, then fix the usual causes: open DNS, missing FastTrack, unused services and attacks on the router.
Problem
Your MikroTik router shows CPU at or near 100%. WinBox becomes slow, users complain about lag, and pings show packet loss.
Symptoms
- System > Resources shows CPU load at 90-100%.
- WinBox and SSH respond slowly or disconnect.
- Internet speed drops even though the ISP link is fine.
Likely causes
- The router's DNS server answers requests from the internet (
allow-remote-requests=yeswith no firewall on the WAN). Attackers use it for DNS amplification. - Brute-force login attempts or floods against the router itself.
- Firewall and mangle rules checking every packet, with no FastTrack and no "accept established" rule near the top.
- Too many simple queues or a heavy queue tree.
- Services left on: web proxy, SOCKS, bandwidth-test server, or a Torch or packet sniffer still running.
- IPsec encryption on a router without hardware acceleration.
Prerequisites
- Admin access to the router (WinBox or SSH).
- A backup before you change the firewall:
/export file=before-cpu-fix.
Solution (WinBox / CLI)
Step 1. Find what is using the CPU. The Profile tool shows CPU usage per process:
/system resource print
/tool profile duration=10sThe top lines (dns, firewall, queuing, networking, management, encrypting) tell you where to look.
Step 2. If dns is high, stop answering DNS from the internet. Turn remote requests off if the router is not the DNS server for your LAN, or keep it on and drop DNS on the WAN:
/ip dns set allow-remote-requests=no
# or keep it on for LAN and block WAN:
/ip firewall filter add chain=input in-interface-list=WAN protocol=udp dst-port=53 action=drop comment="Block DNS from WAN" place-before=0
/ip firewall filter add chain=input in-interface-list=WAN protocol=tcp dst-port=53 action=drop comment="Block DNS from WAN" place-before=0Step 3. If firewall is high, accept established traffic early and use FastTrack. The default configuration already has these two rules; add them only if they are missing:
/ip firewall filter add chain=forward action=fasttrack-connection connection-state=established,related comment="FastTrack" place-before=0
/ip firewall filter add chain=forward action=accept connection-state=established,related,untracked comment="Accept established" place-before=1Note: FastTrack traffic skips queues and mangle. If you limit users with simple queues, those limits stop working for fasttracked traffic.
Step 4. Turn off services you do not use:
/ip service print
/ip service disable telnet,ftp,www,api,api-ssl
/ip proxy set enabled=no
/ip socks set enabled=no
/tool bandwidth-server set enabled=noStep 5. Look for attacks. Watch live traffic on the WAN port and count connections:
/tool torch interface=ether1
/ip firewall connection print count-onlyIf one address sends thousands of packets, add it to an address list and drop it in the input chain.
Verification
Run /tool profile duration=10s again. CPU should drop and WinBox should respond normally. /system resource monitor shows the live CPU load.
Common errors
- Enabling FastTrack while relying on simple queues: the speed limits stop working.
- Disabling the
wwworwinboxservice while you are connected through it. - Blocking DNS on the LAN by mistake: users lose name resolution.
Rollback
Each rule above has a comment, so you can disable it quickly:
/ip firewall filter disable [find comment="FastTrack"]
/ip firewall filter disable [find comment="Block DNS from WAN"]Watch the video: How to fix 100% CPU usage on MikroTik routers
This topic is covered hands-on in MTCNA — MikroTik Certified Network Associate.
View MTCNA