RouterOS version 6.49.19 has been released in the “v6 long-term” channel!
Before an upgrade:
Remember to make backup/export files before an upgrade and save them on another storage device;
Make sure the device will not lose power during upgrade process;
Device has enough free storage space for all RouterOS packages to be downloaded.
Both the “stable” and “long-term” channels will display that a new version is available. It is almost identical to the previous release - the only change is an updated copyright notice (the year has been changed from 2025 to 2026).
Should you upgrade if you are already using 6.49.19 “stable”? The 6.49.19 “long-term” does not include any updates apart for a new build time, updated copyright notice, and discovery packets now use the “long-term” label.
What's new in 6.49.19 (2026-Jan-13 12:15):
console - updated copyright notice;
lte - added support for R11e-LTE6 v039 firmware release;
security - allow only "http:" and "https:" schemas in relevant dst fields;
system - fixed v6 to v7 upgrade from separate packages;
system - improved upgrade procedure reliability;
upgrade - the upgrade, testing, and development channels now direct to the latest long-term version of RouterOS v7;
To upgrade, click “Check for updates” at /system package in your RouterOS configuration interface, or head to our download page: http://www.mikrotik.com/download
If you experience version related issues, then please send supout file from your router to support@mikrotik.com. File must be generated while a router is not working as suspected or after some problem has appeared on the device
Please keep this forum topic strictly related to this particular RouterOS release.
#[SUP-126246]: Winbox IPv6 ND reachable time units
Regression introduced in 6.47.10 which was a long-term telease, still in 6.49.19.
Cosmetic, value correctly in seconds, just wrong label “ms” shown in Winbox.
I created a new key pair for SSH … it works right away on rb5009 with 7.19.3, but on ltAP with 6.49.19 you still need the parameter “PubkeyAcceptedKeyTypes +ssh-rsa” … is that possible?
There are several answers scattered around the forum given by the MikroTik team that allow for the clear understanding that new features will not be added to v6.
That the focus will be only on fixing bugs that compromise the operation of the equipment.
But to this day, there's no official statement or dedicated post addressing this. It always comes as a side comment.
It's obvious. Anyway it would be nice to know for how long the long-term v6 channel will live There's a lot of older but perfectly functional devices in the wild.
I have upgraded all APs and the cloud router, but a hexs (RB760iGS ) insists on continue on 6.49.1. I tried to find any reason/bug/restriction associated with that device, but I could not find any reason.
Anyone experiencing this? Or knows why this device would stick to 6.49.1?
After failed attempt to upgrade it's always good to check logs ... most often the message about failed upgrade contains pretty good indication about reason of failure.
RouterOS version 6.49.19 has been promoted to long-term.
Both the “stable” and “long-term” channels will display that a new version is available. It is almost identical to the previous release - the only change is an updated copyright notice (the year has been changed from 2025 to 2026).
Should you upgrade if you are already using 6.49.19 “stable”? The 6.49.19 “long-term” does not include any updates apart for a new build time, updated copyright notice, and discovery packets now use the “long-term” label.
tiny issue: when upgrading from 6.19.19 longterm to 7.20.7 through the upgrade channel, after upgrade it will be on stable channel instead of longterm. this doesn’t happen when i simply push the 7.20.7 file and reboot.
it’s not so bad, just not expected behavior. maybe it’s unavoidable when changing to upgrade branch?
upgrade channel in v6 was like that since it was introduced ... upgrade to v7 and set channel to stable.
I don't see how the channel setting after upgrade could be set to previous setting (long-term or stable), setting only holds one value (which was set to upgrade). Unless MT does some magic in forthcoming v6 long-term release.
@mkx it has to be possible somehow because as i noted, i get right into v7 longterm when i download and push the appropriate package by hand. so the updater would also just have to pull that package instead of the one that defaults to stable. it wouldn’t be a huge amount of magic. maybe even a checkbox “stay in longterm” yes/no
There's a lot of older but perfectly functional devices in the wild.