Guides › Sound & time
Why your international meeting moved by an hour: the daylight saving gaps of 2026
Twice a year, recurring calls between continents quietly shift by an hour. Someone joins early, someone misses the start, and the calendar invitation looks correct to everyone. The cause is that countries switch to and from daylight saving time (DST) on different dates, and some never switch at all. We calculated every 2026 change for the regions that most often cause trouble, using the IANA time zone database through Python's zoneinfo module, the same database your phone and our time zone converter rely on.
Short answer: in 2026 the US and Europe were out of step for three weeks in spring (March 8 to March 28) and one week in autumn (October 25 to October 31). During those weeks New York was 4 hours behind London instead of 5. Korea, Japan, China and India do not use DST, so their difference to the US and Europe changes twice a year.
All 2026 clock changes we checked
| Region | Clocks forward | Clocks back |
|---|---|---|
| United States and most of Canada (e.g. New York, Los Angeles) | Sunday, March 8, 2:00 → 3:00 local | Sunday, November 1, 2:00 → 1:00 local |
| European Union and the UK (e.g. London, Berlin) | Sunday, March 29, 01:00 UTC | Sunday, October 25, 01:00 UTC |
| South-east Australia (e.g. Sydney, Melbourne) | Sunday, October 4, 2:00 → 3:00 local | Sunday, April 5, 3:00 → 2:00 local |
| Korea, Japan, China, India, Singapore | No daylight saving time | |
Two details catch people out. The US changes at 2 a.m. local time in each zone, so the switch rolls across the country over several hours. Europe changes at the same instant everywhere, 01:00 UTC, which is 1 a.m. in London and 2 a.m. in Berlin. And Australia's seasons are reversed: Sydney moves its clocks back in April, just as the northern hemisphere has moved forward.
The mismatch weeks
Because the US moves three weeks before Europe in spring and one week after Europe in autumn, the familiar transatlantic gaps change for a few weeks each year.
| Period in 2026 | New York vs London | Los Angeles vs Berlin |
|---|---|---|
| Until March 7 | 5 hours | 9 hours |
| March 8 – March 28 | 4 hours | 8 hours |
| March 29 – October 24 | 5 hours | 9 hours |
| October 25 – October 31 | 4 hours | 8 hours |
| From November 1 | 5 hours | 9 hours |
A 10:00 New York stand-up is normally 15:00 in London. During those four weeks it is 14:00 in London, unless the meeting's owner is in London, in which case it moves for the New York side instead.
A worked example from Seoul
We took a weekly call fixed at 09:00 Monday in Seoul and converted it for each 2026 date below. Seoul never changes its clocks, so every shift comes from the other side.
| Monday | New York | Los Angeles | London | Berlin | Sydney |
|---|---|---|---|---|---|
| March 2 | Sun 19:00 | Sun 16:00 | Mon 00:00 | Mon 01:00 | Mon 11:00 |
| March 16 | Sun 20:00 | Sun 17:00 | Mon 00:00 | Mon 01:00 | Mon 11:00 |
| April 6 | Sun 20:00 | Sun 17:00 | Mon 01:00 | Mon 02:00 | Mon 10:00 |
| October 26 | Sun 20:00 | Sun 17:00 | Mon 00:00 | Mon 01:00 | Mon 11:00 |
| November 2 | Sun 19:00 | Sun 16:00 | Mon 00:00 | Mon 01:00 | Mon 11:00 |
Over the spring the same Seoul call moved one hour later for Americans in March, one hour later for Europeans at the end of March, and one hour earlier for Sydney in April: three different shifts within five weeks.
How to keep recurring meetings right
- Anchor the meeting to one time zone on purpose. Calendar apps store a recurring event in the organiser's zone. Decide whose local time should stay fixed (usually the majority of attendees) and create the event from that zone.
- Write times with a city, not an abbreviation. "10:00 New York time" is unambiguous all year. "10:00 EST" is wrong for most of the year, because summer time in New York is EDT. Abbreviations such as CST also mean different things in different countries.
- Check the weeks around March and late October. Put a reminder in your calendar for the second Sunday of March and the last Sunday of October to confirm the time with the other side.
- Use a converter that knows the date. A fixed "minus 5 hours" rule fails in the mismatch weeks. Our time zone converter calculates from the date you choose, and the world clock shows the current offset at a glance.
- For deadlines, use UTC. "Submit by 23:59 UTC on Friday" means the same moment everywhere, regardless of DST.
Times that do not exist, and times that happen twice
On the morning clocks go forward, local times between 2:00 and 3:00 do not exist in the US; in Europe the missing hour is 01:00–02:00 in London and 02:00–03:00 in Berlin. On the morning clocks go back, the hour before the change happens twice. Avoid scheduling automated jobs, alarms or deliveries in those hours. If you must, store them in UTC.
Common questions
Is the EU going to stop changing the clocks?
The European Commission proposed ending seasonal clock changes in 2018, but member states have not agreed on how to implement it, so the changes continue under the existing directive. Check again each year rather than assuming.
Why does my phone show the right time but my meeting is wrong?
Your phone converts each event from the zone it was created in. If the organiser created it in a zone that did not change, or typed the time in a description instead of the event fields, the calendar cannot adjust it for you.
Do all of the US and Australia use DST?
No. Most of Arizona and Hawaii do not, and in Australia, Queensland, the Northern Territory and Western Australia do not. Always convert using a city, not a country.
References
- IANA Time Zone Database (tz database)
- Python documentation: zoneinfo, IANA time zone support
- U.S. Department of Transportation: Daylight Saving Time
- European Union: Directive 2000/84/EC on summer-time arrangements
Written and checked by Ria Kim for GlowHalo; figures without a source link come from the steps shown on this page. Companion tool: Time Zone Converter. Spotted an error? Write to help@glowhalo.org.