Barq Meet
Create your free link

Daylight saving time dates 2026-2027 by country

On this page

Those dates come from the checked 2027 spring and autumn listings, as of 17 Nov 2026. Coverage is limited to verified regions, not every country in the world. Our cross-zone scheduling guide covers the booking setup after you've checked the dates.

Which daylight saving time dates apply in 2026 and 2027?

The dates below describe clock changes in the regions named, with country exceptions retained. They aren't nationwide promises. "Starts" means moving into daylight time; "ends" means returning from it, which reverses the calendar order in southern-hemisphere rows.

Country or region2026 dates2027 datesCoverage note
United States, observing locationsStarts 8 March; ends 1 NovemberStarts 14 March; ends 7 NovemberUse the location's rules; not a nationwide rule
Canada, where still observedStarts 8 March; ends 1 NovemberStarts 14 March; ends 7 NovemberSee the Canadian rule changes below
United KingdomStarts 29 March; ends 25 OctoberStarts 28 March; ends 31 OctoberSpring at 01:00 local; autumn at 02:00 local
European Union, observing zonesStarts 29 March; ends 25 OctoberStarts 28 March; ends 31 OctoberTransition at 01:00 UTC; local hour varies
Australia, observing statesEnds 5 April; starts 4 OctoberEnds 4 April; starts 3 OctoberLord Howe Island changes by 30 minutes
New ZealandEnds 5 April; starts 27 SeptemberEnds 4 April; starts 26 SeptemberChatham Islands use different local transition hours
Chile, most locationsEnds 5 April; starts 6 SeptemberEnds 4 April; starts 5 SeptemberEaster Island changes on the preceding Saturday
Mexico, some locationsStarts 8 March; ends 1 NovemberStarts 14 March; ends 7 NovemberThese dates don't describe most of Mexico
CubaStarted 8 March; no 1 November fall-backEnd listed for 7 NovemberLatest research overrides older seasonal predictions
MoroccoPermanent UTC+00 from 20 SeptemberNo seasonal change under the checked ruleDon't extend an older seasonal table into 2027

Sources, as of 17 Nov 2026: timeanddate's 2026 spring, 2026 autumn, 2027 spring and 2027 autumn listings. Cuba and Morocco corrections follow IANA release notes. The listings warn that future dates might not be final.

Chile's April date names the midnight transition boundary. A clock moving back at 00:00 returns to the previous civil date, so the last displayed time before the change can carry Saturday's date. Don't move a meeting by a day to "correct" that label.

When do US and European meeting times drift apart?

The US-Europe mismatch lasts from the US spring change until Europe's spring change, then from Europe's autumn change until the US autumn change. New York and London are four hours apart during these intervals instead of their usual five. Check the Sunday instants. For a conversation spanning dated Chicago and London hours, check the shared workday before repeating a familiar start in another season. For a conversation spanning dated New York and Riyadh hours, check the shared workday before repeating a familiar start in another season.

YearSpring mismatch, between transitionsAutumn mismatch, between transitionsTypical New York 09:00 in London
20268 March to 29 March25 October to 1 November13:00 during mismatch; otherwise 14:00
202714 March to 28 March31 October to 7 November13:00 during mismatch; otherwise 14:00

Method: computed with Luxon for America/New_York and Europe/London using the installed IANA-derived rules, and checked against the dated listings above. The intervals begin and end at the actual transitions, not at midnight across both cities. For weekday planning, 2027's affected workweeks are 15 to 26 March and 1 to 5 November.

New York 09:00 appears an hour earlier in London during the 2027 mismatch weeks
  1. 1

    12 March 2027

    London 14:00

    Before the US spring change.

  2. 2

    15 March 2027

    London 13:00

    US clocks have changed; UK clocks haven't.

  3. 3

    29 March 2027

    London 14:00

    Both locations now use summer offsets.

  4. 4

    1 November 2027

    London 13:00

    UK clocks have changed back; US clocks haven't.

  5. 5

    8 November 2027

    London 14:00

    Both locations now use winter offsets.

New York 09:00 appears an hour earlier in London during the 2027 mismatch weeks
WhenEventDetails
12 March 2027London 14:00Before the US spring change.
15 March 2027London 13:00US clocks have changed; UK clocks haven't.
29 March 2027London 14:00Both locations now use summer offsets.
1 November 2027London 13:00UK clocks have changed back; US clocks haven't.
8 November 2027London 14:00Both locations now use winter offsets.

Figure method: Luxon converts 09:00 America/New_York on each labeled date to Europe/London. The sequence fixes the New York hour; it isn't a claim that every existing invitation automatically moves to 09:00 New York. For a conversation spanning dated New York and Singapore hours, check the shared workday before repeating a familiar start in another season. For a conversation spanning dated New York and Sydney hours, check the shared workday before repeating a familiar start in another season.

If you've written "EST" on a summer invitation, start with the EST and EDT distinction. A fixed abbreviation can conceal the exact seasonal change you're trying to explain.

Do Australia and New Zealand change on the same weekend?

No. In both years, New Zealand enters daylight time one week before the listed Australian observing states, although their April end dates match. The difference matters for meetings arranged across the September-to-October gap. A shared season isn't a shared transition day. For a conversation spanning dated New York and Karachi hours, check the shared workday before repeating a familiar start in another season. For a conversation spanning dated New York and India hours, check the shared workday before repeating a familiar start in another season.

For Sydney, the 2027 change back is 4 April at 03:00 daylight time, returning to 02:00. Auckland changes back on 4 April at 03:00 daylight time too, but those local hours occur at different UTC instants. Luxon gives Auckland's transition as 3 April 14:00 UTC and Sydney's as 3 April 16:00 UTC.

These are named-city calculations, not exceptions erased from a country table. Lord Howe's 30-minute shift and Chatham's different transition hours remain separate cases in the checked 2027 listings, as of 17 Nov 2026. Don't copy Sydney's wall-clock instructions onto every Australian island.

A label such as "summer time" also needs a location. Use the time-zone abbreviation reference to replace an uncertain shorthand with a named zone and a date.

Which recent clock changes make older DST lists unreliable?

The checked IANA research records 2026 rule changes affecting several Canadian regions, Cuba and Morocco. Older lists need revision. These updates matter even when a previously printed March or November date looked plausible for the country as a whole.

According to IANA release notes, as of 17 Nov 2026, British Columbia moved to permanent UTC-07 in March, Alberta to UTC-06 in June, the Northwest Territories to UTC-06 in August, and Manitoba to UTC-05 in October. Northwestern Ontario areas aligned with Winnipeg follow its change. Keep these exceptions beside any Canadian dates you reuse.

The same research records Cuba skipping its 1 November 2026 fall-back and Morocco moving to permanent UTC+00 on 20 September. A missing fall-back matters. It changes the gap to a colleague whose city still follows its earlier seasonal schedule. The BST explanation keeps London's seasonal clock separate from the fixed zero-offset reference used by UTC and GMT.

The permanent-offset examples above aren't a complete no-DST country list. Paraguay's status wasn't reverified in the allowed research, so we leave it out instead of repeating an older claim.

How were these dates checked, and what remains uncertain?

We compared the permitted platform research with calculations for named zones and explicit dates. We didn't use a fixed offset for an entire country. The research records IANA 2026f as its latest release, while this draft's local Node runtime reports tzdata 2026a.

Version matters here. That gap is why recent Canadian, Cuban and Moroccan corrections above are attributed to the research, not presented as results of the older runtime. The New York/London, Sydney and Auckland examples were calculated with Luxon under 2026a and agree with the checked date tables.

This Markdown reference is a dated snapshot; it doesn't automatically regenerate when tzdata changes. Its next editorial check should accompany the next tzdata release, or the December 2026 monthly review if that comes first. A complete table of every country requires a fresh verified global dataset, which the available research doesn't supply.

How should I offer appointments across a clock-change week?

Set availability in the named zone whose local hours you intend to keep, then inspect a date on each side of the change from the guest's zone. Don't test only today. A correct slot before the transition doesn't prove next month's local hour will be convenient.

We give Barq Meet guests a time-zone selector while the host's availability schedule supplies the offered hours. We check selected Google calendars again when a booking is confirmed. Those are separate checks: the right local hour can still be busy.

We support one host's booking availability, without combining colleagues into a collective schedule. Compare the working-hours overlap first if several people must attend, then agree an hour before circulating one person's link.

Review the account features and calendar limits, then offer a dated cross-zone appointment after checking both local labels.

Frequently asked questions

Do these dates guarantee that a future government will keep the rule?

No. Future clock rules can change after publication. The dates describe the checked research and named-zone calculations, so reconfirm the actual location and appointment date before relying on a long-range series of international meetings. Recheck a future appointment close to its date when rules matter, and retain a named zone so conversions follow the location instead of a manually copied offset.

Does a one-hour clock change make a thirty-minute meeting longer?

No. A thirty-minute appointment still needs thirty elapsed minutes. Its local-clock labels can cross a missing or repeated hour, so compare the booked start and end instants instead of subtracting wall-clock labels during the transition. Inspect the confirmed start and end as instants, keeping duration separate from a change to the local clock labels used to display them.

Why does one country have several daylight-saving exceptions?

A country can contain regions with different clock rules. Country names are therefore a starting point for this reference, while a dated location such as America/New_York identifies the rules needed to convert an appointment accurately. Choose the participant's actual location before converting, instead of applying one national clock-change date to every region and expecting identical seasonal rules.

Create your free booking link

Sign in with Google, create an event and share your link.

Create your free link