Be Careful with MikroTik RouterOS Updates These Days
May 30, 2026
If you are using MikroTik routers in production environments, I recommend being cautious with RouterOS updates at the moment. Recently, I have noticed a significant decline in software quality, even in the Stable release branch.
Here are two issues I have personally encountered in my daily work.
Issue #1: Apple Devices Unable to Connect to Wi-Fi (RouterOS 7.22.2)
After upgrading CAPsMAN-based wireless networks to RouterOS 7.22.2, Apple devices that had previously connected to the Wi-Fi network continued to work normally. However, new iPhones attempting to join the network were unable to connect.
Unfortunately, this problem cannot be fixed through the WinBox graphical interface. The workaround requires using the command line and running the following command:
/interface wifi configuration set "YOUR CONFIG PROFILE NAME HERE" !interworking.realms-raw
The issue has been discussed extensively in the MikroTik community forum.
According to reports, MikroTik appears to have fixed this problem in RouterOS 7.22.3.
Issue #2: IPv6 Problems in RouterOS 7.23.0
Shortly after the previous issue was resolved, RouterOS 7.23.0 introduced another serious problem affecting IPv6 clients that obtain SLAAC IPv6 addresses from an Internet provider.
In my case, the issue appeared on Xfinity connections.
The symptoms are somewhat confusing:
Devices successfully receive IPv6 addresses from the router.
IPv6 connectivity appears to be present.
However, applications and services fail to load content properly.
For example, a Smart TV may obtain a valid IPv6 address, but YouTube videos fail to load.
The problem is currently being discussed here
At the time of writing, there is no universally accepted solution that works for all affected devices.
My Recommendation
For customer installations, I have temporarily switched back to the Long-term release branch. At the moment, the latest Long-term version available is RouterOS 7.21.4.
Until MikroTik improves the testing and quality control of new releases, I recommend that administrators carefully evaluate updates before deploying them to production networks. If your existing configuration is working reliably, it may be wise to remain on the Long-term branch and avoid upgrading immediately after a new Stable release becomes available.
Here are two issues I have personally encountered in my daily work.
Issue #1: Apple Devices Unable to Connect to Wi-Fi (RouterOS 7.22.2)
After upgrading CAPsMAN-based wireless networks to RouterOS 7.22.2, Apple devices that had previously connected to the Wi-Fi network continued to work normally. However, new iPhones attempting to join the network were unable to connect.
Unfortunately, this problem cannot be fixed through the WinBox graphical interface. The workaround requires using the command line and running the following command:
/interface wifi configuration set "YOUR CONFIG PROFILE NAME HERE" !interworking.realms-raw
The issue has been discussed extensively in the MikroTik community forum.
According to reports, MikroTik appears to have fixed this problem in RouterOS 7.22.3.
Issue #2: IPv6 Problems in RouterOS 7.23.0
Shortly after the previous issue was resolved, RouterOS 7.23.0 introduced another serious problem affecting IPv6 clients that obtain SLAAC IPv6 addresses from an Internet provider.
In my case, the issue appeared on Xfinity connections.
The symptoms are somewhat confusing:
Devices successfully receive IPv6 addresses from the router.
IPv6 connectivity appears to be present.
However, applications and services fail to load content properly.
For example, a Smart TV may obtain a valid IPv6 address, but YouTube videos fail to load.
The problem is currently being discussed here
At the time of writing, there is no universally accepted solution that works for all affected devices.
My Recommendation
For customer installations, I have temporarily switched back to the Long-term release branch. At the moment, the latest Long-term version available is RouterOS 7.21.4.
Until MikroTik improves the testing and quality control of new releases, I recommend that administrators carefully evaluate updates before deploying them to production networks. If your existing configuration is working reliably, it may be wise to remain on the Long-term branch and avoid upgrading immediately after a new Stable release becomes available.
