US Clocks Fall Back on Nov 1, 2026: What Changes for Meetings With Europe and Asia
At 2:00 a.m. on Sunday, Nov. 1, 2026, most of the US sets its clocks back to 1:00 a.m. New York goes from UTC−04:00 to UTC−05:00, Los Angeles from UTC−07:00 to UTC−08:00. Europe already did the same thing on Oct. 25, and Seoul, Tokyo and Singapore don't change at all. If you run a recurring call between the US and Europe or Asia, that adds up to two separate shifts in two weeks. This page is a cheat sheet for four common meeting times. For the full list of who changes when, including Canada's new rules, see our autumn 2026 clock-change guide.
Three weeks, three sets of offsets
Each column is one ordinary Wednesday: the week before Europe changed, the gap week when only Europe had changed, and the first week after the US change.
| City | Wed, Oct 21 | Wed, Oct 28 | Wed, Nov 4 |
|---|---|---|---|
| New York | UTC−04:00 | UTC−04:00 | UTC−05:00 |
| Los Angeles | UTC−07:00 | UTC−07:00 | UTC−08:00 |
| London | UTC+01:00 | UTC+00:00 | UTC+00:00 |
| Berlin | UTC+02:00 | UTC+01:00 | UTC+01:00 |
| Seoul | UTC+09:00 | UTC+09:00 | UTC+09:00 |
| Tokyo | UTC+09:00 | UTC+09:00 | UTC+09:00 |
| Singapore | UTC+08:00 | UTC+08:00 | UTC+08:00 |
Only two things move. Europe drops one hour on Oct. 25; the US drops one hour on Nov. 1. Every change you see in a meeting time below comes from one of those two steps.
The cheat sheet
Times are local, 24-hour clock. "+1 day" means the next calendar day where you are. Bold marks a time that differs from the Oct. 21 column.
09:00 New York (9 a.m. New York)
| City | Wed, Oct 21 | Wed, Oct 28 | Wed, Nov 4 |
|---|---|---|---|
| London | 14:00 | 13:00 | 14:00 |
| Berlin | 15:00 | 14:00 | 15:00 |
| Seoul | 22:00 | 22:00 | 23:00 |
| Tokyo | 22:00 | 22:00 | 23:00 |
| Singapore | 21:00 | 21:00 | 22:00 |
The Europe side moves first: London sees this call at 2 p.m. until Oct. 24, at 1 p.m. during the gap week, then back at 2 p.m. from Nov. 1. Asia moves second: Seoul and Tokyo keep 10 p.m. until the US change and get 11 p.m. from then on.
17:00 New York (5 p.m. New York)
| City | Wed, Oct 21 | Wed, Oct 28 | Wed, Nov 4 |
|---|---|---|---|
| London | 22:00 | 21:00 | 22:00 |
| Berlin | 23:00 | 22:00 | 23:00 |
| Seoul | 06:00 (+1 day) | 06:00 (+1 day) | 07:00 (+1 day) |
| Tokyo | 06:00 (+1 day) | 06:00 (+1 day) | 07:00 (+1 day) |
| Singapore | 05:00 (+1 day) | 05:00 (+1 day) | 06:00 (+1 day) |
An end-of-day New York slot is an early-morning slot in Asia. After Nov. 1 it lands at 7 a.m. in Seoul and Tokyo instead of 6 a.m., one hour less early. London gets it at 9 p.m. for one week only.
09:00 Los Angeles (9 a.m. Los Angeles)
| City | Wed, Oct 21 | Wed, Oct 28 | Wed, Nov 4 |
|---|---|---|---|
| London | 17:00 | 16:00 | 17:00 |
| Berlin | 18:00 | 17:00 | 18:00 |
| Seoul | 01:00 (+1 day) | 01:00 (+1 day) | 02:00 (+1 day) |
| Tokyo | 01:00 (+1 day) | 01:00 (+1 day) | 02:00 (+1 day) |
| Singapore | 00:00 (+1 day) | 00:00 (+1 day) | 01:00 (+1 day) |
This is the slot that gets worse for Asia. Seoul and Tokyo move from 1 a.m. to 2 a.m., and Singapore from midnight to 1 a.m. Berlin gets it at 5 p.m. instead of 6 p.m. during the gap week only.
16:00 Los Angeles (4 p.m. Los Angeles)
| City | Wed, Oct 21 | Wed, Oct 28 | Wed, Nov 4 |
|---|---|---|---|
| London | 00:00 (+1 day) | 23:00 | 00:00 (+1 day) |
| Berlin | 01:00 (+1 day) | 00:00 (+1 day) | 01:00 (+1 day) |
| Seoul | 08:00 (+1 day) | 08:00 (+1 day) | 09:00 (+1 day) |
| Tokyo | 08:00 (+1 day) | 08:00 (+1 day) | 09:00 (+1 day) |
| Singapore | 07:00 (+1 day) | 07:00 (+1 day) | 08:00 (+1 day) |
A late-afternoon West Coast call is the classic US–Asia overlap. After Nov. 1 it reaches Seoul and Tokyo at 9 a.m., the start of a normal workday, instead of 8 a.m. Europe is asleep either way: Berlin sees it at 1 a.m. the next day (midnight during the gap week).
Why Seoul, Tokyo and Singapore never move, but their gap to the US does
Korea, Japan and Singapore don't use daylight saving time. The tz database lists Seoul and Tokyo at UTC+09:00 and Singapore at UTC+08:00 for every day of 2026, with no transitions. A time difference is just one offset minus the other, so when New York goes from UTC−04:00 to UTC−05:00, the gap from New York to Seoul grows from 13 to 14 hours, and Los Angeles to Seoul from 16 to 17 hours. Nobody in Asia touched a clock.
The direction matters. A meeting anchored in US time arrives one hour later on an Asian calendar. A meeting anchored in Asian time arrives one hour earlier on a US calendar: a Thursday 8:00 a.m. Tokyo call shows up in Los Angeles at 4 p.m. on Wednesday before the change and at 3 p.m. after it. A Thursday 8:00 a.m. Singapore call moves from 8 p.m. to 7 p.m. on Wednesday in New York.
The same logic explains the gap week. From Oct. 25 to 31, the US was still on summer time while Europe was not, so US–Europe gaps were one hour shorter (New York–London 4 hours instead of 5), while US–Asia gaps had not changed yet. You can check any specific date with the New York to London converter or the Seoul to New York converter.
The night of the change
In New York the switch happens at 06:00 UTC on Nov. 1. That is 06:00 in London, 15:00 in Seoul and Tokyo, and 14:00 in Singapore, all on Sunday. Los Angeles follows three hours later, at 18:00 on Sunday in Seoul. The hour from 1:00 to 1:59 a.m. happens twice in each US time zone: 1:30 a.m. in New York occurs first at 05:30 UTC and again at 06:30 UTC. Avoid booking anything, including deploys and scheduled jobs, inside that hour on US local time.
Not every US clock moves. Arizona (America/Phoenix in the tz database) stays on UTC−07:00 and Hawaii (Pacific/Honolulu) on UTC−10:00 all year, as federal law lets states exempt themselves. So from Nov. 1, Phoenix is no longer the same as Los Angeles; it matches Denver instead.
Recurring calendar invites
A recurring event is saved in one time zone, normally the organizer's. Everyone else's view is converted from it. That gives three cases:
- Organizer in the US: the meeting stays at the same US time, and the Europe and Asia times move exactly as in the tables above.
- Organizer in Europe: the meeting stays at the same European time. US attendees see it one hour later during the gap week only, then back at the usual US time from Nov. 1. A 2 p.m. London series shows up in New York at 9 a.m., 10 a.m., then 9 a.m.
- Organizer in Asia: the meeting stays at the same Asian time, and US attendees see it one hour earlier from Nov. 1. A 10 p.m. Seoul series moves from 9 a.m. to 8 a.m. in New York.
If the series should follow a different city than the one it was created in, change the time zone of the whole series instead of editing single occurrences, so every occurrence follows the same rule. Also open the first occurrence after Oct. 25 and after Nov. 1 and confirm the time you see, rather than trusting the series summary.
Checklist for the week of Nov. 1
- List every recurring meeting that includes both the US and Europe or Asia.
- For each one, note whose time zone it is saved in.
- Check the first occurrence on or after Nov. 2 against the cheat sheet above.
- Decide which side absorbs the hour. If the US slot now lands at 2:00 a.m. in Seoul, moving it is fairer than keeping it.
- Write the UTC offset in the invite text, for example "9:00 a.m. New York (UTC−05:00)". Offsets don't drift; abbreviations like EST and EDT get mixed up.
- Put the next date on your calendar now: the US springs forward on Mar. 14, 2027 and the EU on Mar. 28, 2027, so the spring gap lasts two weeks instead of one.
Sources
The US rule (DST ends at 2:00 a.m. local time on the first Sunday of November) is set by 15 U.S.C. § 260a and summarized by NIST. Every time and offset on this page was computed with Python's zoneinfo module against the IANA tz database (system release 2026e and Python tzdata package 2026f, with identical results).
- NIST, "Daylight Saving Time (DST)": https://www.nist.gov/pml/time-and-frequency-division/popular-links/daylight-saving-time-dst
- 15 U.S.C. § 260a, Advancement of time or changeover dates (Cornell LII): https://www.law.cornell.edu/uscode/text/15/260a
- 15 U.S.C. § 260a (U.S. Government Publishing Office, govinfo): https://www.govinfo.gov/content/pkg/USCODE-2023-title15/html/USCODE-2023-title15-chap6-subchapIX-sec260a.htm
- IANA Time Zone Database (latest release 2026f, 2026-10-27): https://www.iana.org/time-zones
- IANA tz database NEWS (release notes): https://data.iana.org/time-zones/data/NEWS
Last checked: 2026-10-30