01 / browser timezone probe
Canada’s clocks changed.
Did your browser catch up?
Check the 2026 Canadian timezone changes against your browser’s actual date formatting. Then inspect an invitation if a meeting still looks an hour off.
Choose a location to compare its two displays.
PINNED IANA 2026e
—
Reference offset
THIS BROWSER
—
Observed offset
Run locally. No account access or calendar upload.
Eight locations, one moment
Vancouver, Edmonton, Inuvik and Winnipeg cover the changed reference zones. Los Angeles, Toronto, Regina and Whitehorse are controls. These city zones do not represent every local exception.
| Location | Pinned display | Browser display | Difference |
|---|
The comparison runs after JavaScript loads.
Read the difference before changing a meeting
What this result tells you
A difference is a reproducible observation: this browser mapped one UTC instant to a different wall time than the pinned reference. It does not reveal the browser’s complete timezone database version, the settings of a signed-in calendar, or which time an organizer intended. A match only covers the selected instant and these eight zones.
For example, at 17:00 UTC on November 4, the reference displays 10:00 in Vancouver and 09:00 in Los Angeles. A browser that displays 09:00 for both is worth investigating. Keep that observation separate from an invitation that already stores a fixed UTC instant.
Try another date above, save the report and compare a second browser. If you use WebTraceCheck to manage a separate browser environment, open this same public probe there and compare the outputs. It is optional; we share an operator and no calendar file is passed to it.
Reference reviewed October 15, 2026. Download the pinned data and reproduce the test cases. This is a bounded diagnostic, not a continuously updated world clock.