Microsoft’s Canada timezone troubles leave admins fixing calendars, pretending they’re in Bogota

image c/o theregister.com
image c/o theregister.com

Microsoft has discovered once again that few things strike fear into the heart of a software engineer quite like a government deciding to fiddle with the clocks. Parts of Canada stopped observing seasonal clock changes on November 1, leaving affected areas of British Columbia, Alberta, and Manitoba permanently on UTC-07:00, UTC-06:00 and UTC-05:00 respectively. Unfortunately, Microsoft's sprawling software empire hasn't entirely caught up. Outlook users have been left with the most homework. Switching to the new Canadian time zones won't automatically update existing calendar entries, meaning that meetings scheduled after November 1 are potentially an hour out of whack.

https://www.theregister.com/software/2026/11/02/microsofts-canada-timezone-troubles-leave-admins-fixing-calendars-pretending-theyre-in-bogota/5306934

RIP Leap Second: Time Fix to Be Scrapped by 2035

(Credit: Getty Images/Olena Ruban)

Though unnoticed by most people, the occasional one-second adjustment can cause problems for systems that require an exact, uninterrupted flow of time.

Reddit, for instance, was down for 40 minutes in 2012 when a leap second confused the company’s servers; four years later, Cloudflare’s DNS services were interrupted due to the miniscule time change.

https://www.pcmag.com/news/rip-leap-second-time-fix-to-be-scrapped-by-2035