Skip to content
Week 45News, and what it means for you

Software

Part of Canada stopped changing its clocks, and software tripped over the hour

Since 1 November, British Columbia, Alberta and Manitoba no longer change their clocks. Calendars were an hour out, and in Estonia a man hacked his car’s navigation system to put its clock back an hour.

On Sunday 1 November the clocks in British Columbia, Alberta and Manitoba simply stayed put. For the people there it was a small change, but for software it turned out to be quite a job.

British Columbia announced it on 2 March: the clocks went forward one last time on 8 March and would not go back. Premier David Eby no longer wanted to wait for the neighbouring US states. Alberta and the Northwest Territories followed, and in mid-September Manitoba announced that it too would stay on summer time; Premier Wab Kinew signed the decision on 25 September. British Columbia is now on UTC−7 all year round, Alberta on UTC−6 and Manitoba on UTC−5.

On 26 October Microsoft set out what this means for its products; Windows had already received the new rules in an update. Appointments already in Outlook do not move by themselves, so meetings after 1 November could be an hour out. In a recurring series, occurrences that had been moved are lost when you change the time zone; a fix is still in the works. Until the new time zones work everywhere, Microsoft suggests a place that keeps the same time all year for products such as Power Automate and Fabric: Saskatchewan for Alberta, Arizona for British Columbia and Bogotá for Manitoba. According to The Register, one sysadmin wrote some 900 lines of PowerShell to put their users’ calendars right.

The same week, Rasmus Moorats in Estonia was wrestling with the clock in his 2014 Renault Latitude. After winter time began on 25 October it was an hour fast, and the menus had no option to set the time. That setting turned out to live on the SD card with the navigation maps, which would have cost him around €60 including shipping. Moorats, who works in security, took apart the software of the TomTom-based system and found a way to gain full control. Then he changed a single number: the offset from GPS time went from 180 to 120 minutes. His write-up scored 949 points on Hacker News.

I just want to change the damn time.

Rasmus Moorats on his blog, 2 November 2026

How software knows the time in a place

Computers count in UTC, coordinated universal time. Local time is a rule on top of that: how many hours’ difference, and when summer time starts and ends. The rules for the whole world live in the tz database, which volunteers maintain on a public mailing list and IANA publishes. Through updates to operating systems and applications they reach servers, phones and calendar servers; older devices often never get them.

That is why the maintainers ask governments to settle any change at least a year in advance. The release for Manitoba came out on 29 September, noting the short lead time. In the database Manitoba’s time is now called ‘EST’, Eastern Standard Time: New York’s winter time.

Why recurring meetings break

A one-off appointment can be stored as a single moment in UTC. A recurring one cannot: ‘every Tuesday at 10:00 in Winnipeg’ has to stay at 10:00 after a clock change. So a calendar stores such a series with its time zone and that zone’s rules. When the rules change, the software has to recalculate every future occurrence, including the exceptions, such as the one time the meeting moved to Wednesday. That is where the work lies.

Until the new zones work everywhere, the quickest way out is a place with the same offset from UTC all year. Saskatchewan has not changed its clocks since 1966, and Bogotá is on UTC−5 all year round.

It often happens at the last minute

Mexico abolished summer time in 2022: the Senate voted on 26 October, and the last clock change came four days later. Europe wanted to stop too. In 2019 the European Parliament voted by 410 to 192 to end the clock changes, but the member states have never agreed on whether summer or winter time should stay. So on 25 October the clocks went back an hour once more. That change costs most software no effort, because the rule has been fixed for years. A navigation system from 2014 is another matter.

Our analysis

Time is not a number but a rule, and rules change

A clock that does not have to go back sounds like less work. But between a decision in Winnipeg and an employee’s calendar sits a whole chain: the government, the tz database volunteers, the makers of operating systems and applications, the system administrators and finally the devices themselves. Every link has to test and roll out. With six weeks’ notice, that chain is bound to run behind, whoever is in it. Manitobans working ‘in Bogotá’ for a while is the visible result.

The Renault shows the other side. Its system knows nothing of time zones, only a fixed offset in minutes from GPS time. A fixed offset is easy to build, but then every change takes manual work. Our expectation: there will be more changes like this in the coming years, often at short notice. Quebec wants to stop changing its clocks too, and Europe keeps talking about it.

The lesson for anyone who has software built: store a moment in UTC and a recurring appointment with the name of its time zone, never with a fixed number of hours’ difference. And make sure servers, apps and devices keep receiving time zone updates. Then a new rule is simply an update.

What stands out

  • The chain got six weeks The tz database maintainers ask for at least a year’s notice. Between Manitoba’s announcement and 1 November there were about six weeks.
  • Manitoba is in Bogotá for now For Power Automate and Fabric, Microsoft advised Manitobans to pick the time zone of Bogotá, Lima and Quito, which is on UTC−5 all year.
  • 900 lines for one hour According to The Register, one sysadmin wrote some 900 lines of PowerShell to put their users’ calendars right.
  • The clock sat behind the map protection In the Renault, the clock setting lived on the SD card with the maps. A home-made card would not work, because the system checks every card; Moorats believes that is meant to stop map piracy.

What it means for you

The time in a place is an agreement that a government can change. Software built for that adapts with an update.

  • Check recurring meetings first Series that run across the date of a change are the most likely to slip by an hour. Have your colleagues check them when a country you do business with changes its rules.
  • Keep time zone data up to date Servers, apps and devices get new rules through updates. A device that no longer receives updates will be an hour out after the next change.
  • If you work across borders, follow the news A country can change its clocks with a few weeks’ notice. Mexico did it with four days.

Where we come in · Development

We build software that calculates with time zones

In custom software that works with time, such as planning in an ERP or appointments in an app, we store moments in UTC and series with their time zone, and use the tz database the operating system keeps up to date. When a country changes its clocks, that is an update, not a rebuild.

Do you work with appointments in other time zones, and what happens when the rules change?

Tell us where your software works with time. We’ll think it through with you and always reply within one working day.

More from week 45

All news

Search our services, the news and the rest of the site.