WorldTimeSync

The two-week window when your usual time difference is wrong (autumn 2026)

Every autumn, Europe and North America turn their clocks back on different Sundays. For one week the gap between London and New York shrinks to four hours, and anyone in Seoul or Tokyo sees Europe move first and America a week later. In 2026 there is a new twist: Vancouver doesn't fall back at all.

The dates

WhereWhen (local time)What happens
UK (London)Sun 25 Oct 2026, 02:00 BSTClocks go back to 01:00 GMT (UTC+01:00 → UTC+00:00)
EU (Paris, Berlin, Madrid, Rome…)Sun 25 Oct 2026, 03:00 CESTClocks go back to 02:00 (UTC+02:00 → UTC+01:00)
US and eastern Canada (New York, Chicago, Los Angeles, Seattle, Toronto, Montréal, Halifax)Sun 1 Nov 2026, 02:00Clocks go back to 01:00
British Columbia (Vancouver)Sun 1 Nov 2026No change. BC stays on UTC−07:00 all year after its last spring-forward on 8 March 2026
Alberta, Manitoba, Saskatchewan, Yukon, Northwest Territories (Calgary, Edmonton, Winnipeg, Regina)Sun 1 Nov 2026No change. From 2026 Alberta and the Northwest Territories stay on UTC−06:00 and Manitoba on UTC−05:00 all year; Saskatchewan and Yukon already had no seasonal change
Seoul, Tokyo, Shanghai, Hong Kong, Taipei, Singapore, Dubai, Mumbai—No daylight saving time; nothing changes
SydneyAlready changed on Sun 4 Oct 2026 (forward to UTC+11:00); next change Sun 4 Apr 2027

Europe changes at the same instant everywhere (01:00 UTC), which is why London switches at 02:00 local and Paris at 03:00 local.

What that does to common gaps

PairUntil 24 Oct25 Oct – 31 OctFrom 1 Nov
London → New York5 h4 h5 h
Seoul/Tokyo → London8 h9 h9 h
Seoul/Tokyo → Paris/Berlin7 h8 h8 h
Seoul/Tokyo → New York/Toronto13 h13 h14 h
Seoul/Tokyo → Los Angeles16 h16 h17 h
Seoul/Tokyo → Vancouver16 h16 h16 h (no longer changes)
Singapore → London7 h8 h8 h
Vancouver vs Los Angelessame timesame timeVancouver 1 h ahead

Three real situations

  • A Wednesday 09:00 stand-up in Seoul. On 21 October it lands at 01:00 in London; on 28 October at 00:00 London time. New York sees it at 20:00 on the previous evening both weeks, then at 19:00 from 4 November.
  • A New York 10:00 call with London and Seoul. On 21 October it is 15:00 in London and 23:00 in Seoul. On 28 October London gets it at 14:00 while Seoul still sees 23:00. From 4 November it is back to 15:00 in London, but in Seoul it has slid to midnight, 00:00 on Thursday. If that call was "just about OK" for Seoul, November is when it stops being OK.
  • Vancouver and California. A team that used to treat Vancouver and Los Angeles as the same clock now has a one-hour gap from 1 November 2026 until the US springs forward on 14 March 2027, when they line up again. A 09:00 Los Angeles meeting is 10:00 in Vancouver this winter.

How to avoid the mistake

  1. Put the actual meeting date into the converter, not "today". The gap depends on the date.
  2. For recurring invites that cross 25 Oct or 1 Nov, check the first occurrence after each change; most calendar apps keep the organizer's local time fixed, so everyone else's time moves.
  3. Write the UTC offset in the invite ("10:00 New York, UTC−05:00"). An offset can't drift; "EST" and "PST" often get mixed up.
  4. If you work with Vancouver, check that your phone or laptop has had a recent system update. Time-zone rules ship inside operating systems and browsers, and a device with outdated rules can wrongly move Vancouver back an hour on 1 November 2026. If Vancouver still shows UTC−08:00 after that date, the device needs an update.

Sources

Meeting time cheat sheet

For converted times of common recurring meetings (9:00 and 17:00 New York, 9:00 and 16:00 Los Angeles) in London, Berlin, Seoul, Tokyo and Singapore before, during and after the gap week, see US clocks fall back on Nov 1, 2026: what changes for meetings.

← Guide

Open the converter →