Daylight saving time calendar meetings go wrong in the weeks when two regions change their clocks on different Sundays, and late October 2026 is one of those periods. Europe moved back on October 25, the US moved back at 2:00 a.m. on November 1, and meetings between US and European contacts return to the usual gap from Monday, November 2. This post gives you the dates, a dated table of the gap, the exact settings in Google Calendar and Outlook, and a checklist for recurring meetings that nobody opens until they are an hour off.
Which meetings shift when US daylight saving time ends on November 1, 2026?
Any meeting that is fixed to one side's clock moves by one hour on the other side's clock, and the US and Europe have been out of step since October 25. According to NIST, daylight saving time in 2026 runs from March 8 at 2 a.m. local time to November 1 at 2 a.m. local time. Europe changes on the last Sunday of October, which was October 25, 2026 at 01:00 UTC, when Vienna and Berlin moved from 3:00 a.m. to 2:00 a.m. local time (timeanddate.com).
Here is what that does to one weekly call. Say it is fixed at 10:00 a.m. New York time. Until October 24 it landed at 4:00 p.m. in Vienna. During the week of October 25 it landed at 3:00 p.m. in Vienna, and from Monday, November 2 it is back at 4:00 p.m. Flip it: a call fixed at 4:00 p.m. in Vienna sat at 11:00 a.m. in New York last week and is at 10:00 a.m. from Monday. That is our arithmetic from the dates above, not a vendor statement, and it assumes the meeting keeps the time zone it was created in.
The 2026 DST gap: what is the US and Europe time difference in November?
New York and Vienna are six hours apart for most of the year, five hours apart for one week in October and November, and five hours apart again for two weeks in March 2027. The table below dates every window; the hour differences are our arithmetic from the change dates.
| Feature | New York to Vienna or Berlin | New York to London | What is going on |
|---|---|---|---|
| Mar 29 to Oct 24, 2026 | 6 hours | 5 hours | US and Europe both on daylight time |
| Oct 25 to Oct 31, 2026 | 5 hours | 4 hours | Europe and the UK back on standard time (Oct 25), US still on daylight time |
| Nov 1, 2026 onward | 6 hours | 5 hours | US back on standard time at 2:00 a.m. local time (Nov 1) |
| Mar 14 to Mar 27, 2027 | 5 hours | 4 hours | US on daylight time from Mar 14, Europe not until Mar 28 |
| Mar 28 to Oct 30, 2027 | 6 hours | 5 hours | Europe and the UK on summer time from Mar 28 |
| Oct 31 to Nov 6, 2027 | 5 hours | 4 hours | Europe back on Oct 31, US not until Nov 7 |
How we built it: the 2026 US dates come from NIST. The 2027 US dates (March 14 and November 7) follow NIST's second-Sunday-of-March and first-Sunday-of-November rule. The European dates follow the last-Sunday rule for March and October, and the London column assumes the UK changes on the same days. Every hour difference in the table is our arithmetic, not a vendor statement.
Do the Canadian time zone changes affect my meetings too?
Yes, if you have contacts in British Columbia, Alberta or Manitoba: they do not turn their clocks back on November 1, 2026. Microsoft Support says users in those provinces will stay on permanent daylight saving time from that date and lists British Columbia at UTC-07:00 and Manitoba at UTC-05:00. Google adds the Northwest Territories to the affected regions. On our arithmetic, Vancouver and Vienna are therefore eight hours apart after November 1, not nine.
Both vendors say that existing events may need fixing. Google says that in October 2026 Calendar will automatically shift most affected events back by one hour, covering single events and recurring events without future exceptions, but not all of them; its automated tools address only events owned by the organizer, and for meetings organized in Outlook it advises checking with the organizer and asking them to resend the invitation. Organizers see a warning banner on affected events in Calendar on the web. Microsoft asks affected users to verify events scheduled in advance and recurring meetings that continue beyond November 1, 2026, and says only the organizer can make the change.
How do you keep a Google Calendar meeting at the right time across US and Europe?
Check the time zone on the event, then show the counterpart's time zone next to your own. Google Calendar Help says an event appears in your local time zone and in the local time zones of everyone you invite, even if they are in a different time zone, so the invitation is not the place the mistake hides. The event's own time zone is.
- Your calendar's time zone: in Settings, under "General," click "Time zone," then under the "Time zone" category choose "Primary time zone."
- A second clock on the grid: check the box next to "Show additional time zones" and pick a "Secondary time zone" (optionally a "Tertiary time zone"). Additional time zones appear on the left of the calendar grid.
- A world clock: in the "World clock" section click "Show world clock," then "Add time zone."
- One event: next to the time for the event, click "Time zone." If the event starts or ends in different time zones, click "Use separate start and end time zones."
Our walkthrough of the three-zone setup is in how to show three time zones in Google Calendar.
How do you keep an Outlook meeting at the right time across US and Europe?
Set your calendar time zone, add a second time zone for the other region, and open the meeting to see which time zone it carries. The menu path depends on which Outlook you use, and Microsoft Support documents each of them.
- New Outlook: in Settings, open the Calendar View page and under View, Time zones, use the "Display my calendar in time zone" dropdown. To add a second zone, choose "Add time zone" there and search for a city under "Other time zones."
- Classic Outlook: go to File, Options, Calendar. Under Time zones choose "Show a second time zone" and, if needed, "Show a third time zone." "Swap Time Zones" changes their order.
- Outlook on the web: use the same Calendar View settings, with "Move up" and "Move down" under "Other time zones" once you have three or more zones. Microsoft says the second time zone is visible only in day or week view.
What do Google and Microsoft say about recurring meetings across a DST change?
Neither vendor page we read states the default behavior of a recurring event across a normal daylight saving change, so we are not going to state one. When we looked for that rule on November 1, 2026, the closest vendor text we found was the guidance for the Canadian change, and it contains two warnings that apply to any edit of a series.
- Microsoft: when you update the time zone of a recurring meeting series, any exceptions, for example one instance moved to a new time, are reset, and you re-create them. In new Outlook you select "Edit Series," in classic Outlook "Edit Recurrence." If the meeting has attendees, they receive an updated invitation.
- Google: custom changes to a recurring event, like attachments or different guests, can be lost if you apply a time change to "All events" or "This and following events."
Our reading: do not edit a series that has exceptions just because it looks an hour off. Check the next instance first, and write down the exceptions before you touch the series.
Our checklist for founders (our own suggestion)
This is our suggestion, not vendor guidance. It takes about ten minutes and is built for two setups: Gmail with Slack and Teams (the agency founder with clients in several time zones), and Outlook with Teams.
- Open Monday, November 2 and list every meeting with a counterpart in the other region. Compare its time with the table above.
- Set a secondary time zone (Google) or a second time zone (Outlook) to the counterpart's region for the next two weeks, so both clocks sit on the grid.
- For each recurring meeting with a counterpart, open the event and read its time zone. Check the next two instances, not the series title.
- Message the counterpart once with both clocks, for example "Mondays 10:00 New York, 16:00 Vienna." That removes the guessing in either direction.
- Before you change a series, note its exceptions, because both vendors warn that exceptions and custom changes can be lost.
- For invitations: an Outlook organizer who changes the time zone of a meeting sends attendees an updated invitation, and Google's automated fix covers only events the organizer owns, so ask an Outlook organizer to resend a corrected invitation if a meeting looks an hour off.
- Put March 14 and March 28, 2027 in your calendar now. Those are the next two Sundays that open a gap.
Where Nolario fits
Nolario does not fix a time zone, change an event or reschedule a meeting, and it never sends anything on your behalf. What it does is pull Gmail, Outlook, any IMAP mailbox, Slack, Teams and Google Calendar into one feed, score every item from 0 to 100 and rank it, so a client message about a moved meeting does not wait in the channel you opened last. If an invitation email is where the change arrived, see how to find calendar invitations in Gmail and Outlook, and for the Slack and Teams side how to check Gmail, Slack and Teams without missing clients. If you run several Outlook accounts, the Outlook unified inbox guide covers that view.
Nolario is a desktop web app, there is no mobile app, and access is by waitlist, opening May to August 2027, so it will not help with this week's change. Use the calendar settings above today. See the integrations page for the channels it connects.
