Check-for-updates cache

RouterOS General
1

Hi!

I’m trying to install in some devices the last RouterOS update and I’m getting the “already up to date” message in some devices.
As I see on the website, and in other devices I manage, the last one it’s the 6.45.5

Obviously it should be a cache related question. That device has the web-proxy disabled and on that network I don’t have any proxy or cache. It could be a ISP cache of course, but the question I’m doing myself it’s if the http query to 159.148.172.226 RouterOS does it’s using or not the no-cache header ?

A reboot doesn’t helps.

[admin@XXX] /system package update> set channel=stable
[admin@XXX] /system package update> check-for-updates 
            channel: stable
  installed-version: 6.45.3
     latest-version: 6.45.3
             status: System is already up to date
2

Nobody has any clue about a cache on the check update process?

3

Very curious. Do the affected routers happen to be all of one non-MIPSBE architecture? I am wondering if MT screwed up the distribution repository for one architecture.

4

No I had different architectures one of they correctly getting the update in one site but in another site the other device didn’t detected the updated.

After some hours all the devices detected correctly the update. That’s why I thought about an internal cache or a restriction about it doesn’t connects to the update server if the device did a check X hours before.