Canada · calendar time observatoryPinned IANA 2026e · Oct 2026—Feb 2027

Calendar time, explained

Google Calendar one hour off after November 1?

Keep the event’s intended time, the file’s stored time and the browser’s display separate. This worksheet helps you collect the evidence before editing.

Google acknowledges 2026 Canadian timezone-related calendar errors and describes an October correction process. Its help page covers organizer permissions, recurring-event exceptions and invitation updates. Check the current Google Calendar instructions for account-specific actions.

01

Write down the intended appointment

Use one affected event. Ask the organizer for its intended local date, time and location. Record a concrete statement such as “November 4, 09:00, Vancouver,” rather than “the morning meeting.” Keep a screenshot and the original export before experimenting.

A participant’s screenshot can show a different timezone without implying a different instant. Compare the event details and displayed location, not just the position of a block on a weekly grid.

02

Test the browser without the account

Open the timezone probe, select a date before the transition and then a date after it. Save its report. If a second browser has different results, you have evidence about the runtime. If both agree with the reference, that still leaves the event’s stored data and account settings to inspect.

Updating or changing browsers can affect the probe while leaving an already stored invitation unchanged. Re-test each layer independently.

03

Inspect the original file

Export a local ICS copy using the calendar’s own controls, then open the file checker. Look first at the classification. A UTC start fixes an instant. A TZID start refers to a location and possibly an embedded definition. A floating start lacks a location. An all-day date has no hour to move.

Compare a fresh export after the source is updated. A change from an old embedded rule to a current one is different from a change to the event’s wall time. Preserve both copies so you can tell which operation happened.

04

Verify the participants’ final view

Use a synthetic invitation first if you control the workflow. Record sender and receiver views, their timezone settings and the downloaded attachment. For a real appointment, confirm the final intended time directly with the organizer. Do not use a temporary inbox for private customer meetings or account recovery.

Our round-trip worksheet provides a reproducible, non-sensitive test. It keeps “mail arrived” separate from “the meeting time is correct.”

A report that someone can reproduce

Include the intended wall time and location, the affected date, browser version, two probe outputs and the relevant file-check result. Remove private titles, attendee addresses and meeting URLs. The checker’s redacted download omits those fields but retains dates; review it yourself before sharing.

For a recurring event, say whether the problem affects the first occurrence, later instances or one exception. The checker does not expand the series. Read the recurrence guide before applying a change across multiple appointments.