IANA’s Moldova correction shows why the transition hour matters
The 2026a release corrects how software represents clock changes dating from 2022.
A data correction, not a new October law
IANA’s 2026a release states that Moldova has used EU transition times since 2022. The correction places the spring change at 03:00 rather than 02:00, and the autumn change at 04:00 rather than 03:00. This is a correction to software’s representation of past and future rules, not a claim that Moldova introduced a new policy on the date of this article. That distinction is important when reporting database updates.
Why one transition hour matters
For a daytime appointment in Chișinău, an outdated and updated database may often produce the same answer. Around the overnight transition, however, the exact instant can determine which offset applies. A one-hour discrepancy can affect the order of recorded events or the interpretation of a local timestamp. Looking only at a city’s ordinary winter and summer offsets would miss this particular correction.
Historical records need context
When reconciling older logs, preserve their original timestamp and any recorded UTC offset. Do not overwrite historical evidence solely because a newly updated display looks different. Compare the underlying instant, the location and the database version used for conversion. A displayed local time is the result of applying rules to an instant; changing those rules can alter the display without changing what actually happened. See the timestamp guide for that distinction.
A lesson for future scheduling
Teams maintaining scheduling software should read release notes rather than treating time-zone updates as cosmetic. Test dates immediately around affected transitions and check ambiguous overnight times explicitly. For ordinary users, keep systems updated and provide a date and location when reporting a discrepancy. Our guide to clock gaps and overlaps explains the human-facing problem, while the update guide traces how a correction reaches applications.