IP Cloud clock drift

RouterOS General
1

/ip cloud appears to be getting clock drift. noticed it on some routers:

With IP cloud:

/system clock print
                  time: 06:51:41
                  date: may/15/2017
  time-zone-autodetect: no
        time-zone-name: manual
            gmt-offset: +00:00
            dst-active: no

Approx 8 minutes ahead of time

Add sntp configuration to an ntp.org pool and it’s correct:

/system clock print
                  time: 06:44:18
                  date: may/15/2017
  time-zone-autodetect: no
        time-zone-name: manual
            gmt-offset: +00:00
            dst-active: no

switch it back and it reverts back to the incorrect time. This is a pretty substantial drift so just be wary anyone who’s relying on this for schedules etc!

2

ip cloud is ONLY used to set initial time before you configure NTP. It is not a normal time source and should no be used in any time critical setup. Basically it is to avoid your year being 1970

3

Someone is bound to ask… can’t the cloud machine(s) simply run NTP client to get better time? Eight minutes is way off, it can’t happen even if you set the time manually once a month. :slight_smile:

4

I wonder why these complaints on ip cloud are here again and again. Everyone can use public time servers and ddns services reliably instead of this. It is shame that mikrotik can not keep their servers with at least somehow corresponding time.