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

Calendar time, explained

Test a calendar invitation from sender to receiver

Use one fictional event and keep a small evidence sheet. This separates message delivery, file contents and calendar rendering without risking a real appointment.

Prepare a small, non-sensitive test

Use an account and application workflow you control. Create a fictional appointment with no guest names, customer data, conferencing URL or real location. Pick November 4, 2026 at 09:00 in Vancouver. Write down the intended location ID and the pinned expected UTC instant, 16:00Z.

Keep a second sample before the transition, such as October 28 at the same wall time. If both sides agree before the transition but not after it, you have a much more useful observation than “calendar broken.” Add a recurring example only after the single-event path is understood.

Follow the actual delivery path

A

Sender

Record the event’s local start and chosen timezone. Save the source export. Distinguish a newly issued invitation from a forwarded email, a downloaded file and a subscribed calendar feed. Use the path your product actually relies on.

B

Receiving inbox

For a disposable test recipient, CleanTempMail can provide a temporary receiving address. If an attachment is available, save it locally and inspect it here. If the service or sender does not expose an ICS attachment, record that limitation instead of treating a visible email body as the original calendar file.

Mail arrival demonstrates delivery to that inbox. It does not demonstrate correct timezone interpretation or a participant’s RSVP. Temporary inboxes are unsuitable for private appointments, durable ownership or recovery. CleanTempMail shares our operator; using it is optional.

C

Calendar display

Use a test calendar that you control to inspect the received event, if that is part of your workflow. Compare the displayed date, time and location with the intended appointment. Keep the source and received file copies separate; re-exporting can rewrite the timezone definitions you are trying to investigate.

Compare environments without mixing layers

Run the public browser probe in each browser used by the test. If you use WebTraceCheck for a separate browser environment, compare the same probe date there. This is an optional companion product from the same operator; the link does not carry calendar input.

Then inspect each saved file in the local checker. A browser-runtime mismatch and an embedded-file mismatch can exist independently. Do not infer one from the other.

Keep this evidence sheet

  • Intended wall time, location ID and UTC reference.
  • Sender application, chosen timezone and export method.
  • Delivery path and whether the original ICS attachment was available.
  • Receiver’s displayed time and location setting.
  • Probe date and runtime results for each browser.
  • File-check classifications and any recurrence flags.

Repeat after one change at a time. The goal is a reproducible explanation of the difference, not a green badge at any cost. Downloaded reports omit direct identifying fields, but dates can still be sensitive. Review them before sharing.