Time Zone outdated and overriding NTP

RouterOS General
1

Hi, y’all.
I’m from Brazil, and the government has been canceled the DST from now on.
https://time.is/time_zone_news/no_dst_in_brazil_in_2019
When we use some time zones (eg. America/Sao_Paulo), Mikrotik is activating DST by default.
Is it possible to correct?

My workaround was setting the manual time zone (-3) or setting a time zone from another region.

P.S.: There are dozens of Time Zones to select, but we actually have only 4 (UTC−02:00, Noronha | UTC−03:00, Brasilia | UTC−04:00, Amazon | UTC−05:00, Acre)
:confused:

2

Same problem here.

3

Same problem…

4

This issue is fixed in the latest RouterOS versions. We updated the timezone database according to latest international standards. Upgrade your device to 6.46beta

5

I checked the changelog, but didn’t find this fix.

6

I didn’t find it in the changelog, and we only use long-term versions in our production routers.
But I’m glad you realized this config.
Thank you.

7

I guess MT won’t push out a ROS update only to include newer timezone data because probably they think it’s not that important.

Timezone setting is only relevant for RB’s internal processes (such as scheduling and logging), I’m not sure about logs sent to some syslog server, do they carry RB’s local timestamp or is it actually UTC (and get’s interpreted by syslog server to its own local time). If it’s about scheduling, it is easy to set router to UTC and then (from the top of admin’s head) add needed offset when setting run times for tasks. The same procedure is hard if local time has DST.

8

I’m making time adjustments on my microtic devices, but again, the devices suddenly go back to 1970. You need to be a time professor for log records.
I make automatic or manual adjustment of time in all of the microtic devices. He is constantly making date time according to his head.