We have a Mikrotik WAP AX for a month a now. We ran into out of memory problems with it. It serves about 50 WIFI clients, most of them 2.4GHz N devices, and a few 5 GHz AX devices, phones. No Capsman. We also have about 40 scripts running on it. Every 5 to 10 days the WAP AX runs out of memory, th…

[Screenshot_20251201_065305] Haven’t seen any memory leaks on any of the WAP AX’s I have running. I would test scripts first.

[image] LFi: the CPU load gets higher and higher If possible create a supout.rif when these CPU spikes start. Then inspect it using the supout.rif viewer on mikrotik.com .

We installed 7.19.6 on WAP AX, and it starts with even less free memory (26MB) than with 7.20.5 (42MB). WAP AC runs 7.20.5, and it runs fine. It has 12.2 MB free RAM out of 64 MB total RAM. It has 29 Wifi clients connected, running the same scripts as the WAP AX did.

We have tried that, unfortunately the hap ax crashed while creating the supout.rif.

[image] LFi: 64 MB total RAM Since you mention 64MB of RAM it must be the old MIPSBE Version of the wap ac. Which also means you run the “old” wireless drivers which require less ram.

My wAPs ax only have 3 bridge rules and nothing else besides being controlled by CAPsMAN. However, they always run at 87%-91% of RAM usage, which is quite high to be honest. I hope the next generation has more RAM, but also that at some point a memory profiling tool is introduced.

My wAP ax has 256MB RAM and is consuming around 220MB. It's not changing over time so I'm not worried. If device is not crashing with some sort of OOM condition, then seeing 95% of RAM used means that ROS is utilizing resources as intended. OTOH my Audience (with also 256MB RAM) uses around 130MB …

WAP AC with 7.20.5 also crashed with out of memory. It survived about 9 days. See the graphs, the same pattern as with the WAP AX, CPU load starts to grow, device starts to not respond to SNMP (resulting in the choppy memory graph), then reboot, memory usage falls back. The last known good version…

Since I am not allowed to post two pics in one post (which I was able to do in the beginning of the thread) I post the memory graph here. [mikrotik_wap_ac_memory_week]

I can see that the "CPU consumption" was going on for a whole day .... so when/if you see it again next time, check what in particular is using up the CPU cycles (run CPU profiler). And if you do see something weird, create a supout.rif and attach it to issue ticket you're going to open with MT supp…

WAP AX out of memory issues

RouterOS General

BartoszP December 23, 2025, 10:05am 28

There are a few memory leak fixes reported:

wifi - fixed possible memory leak when failing to start AP on chosen channel;