In a recent thread, I’d surmised about how Canadian broadcast networks
might choose to handle the new timezone landscape in the near-term:
https://lists.iana.org/hyperkitty/list/[email protected]/message/RZJ4QUR3Y4U3VXC42EUUJSHK4MUIAPWK/

On Wed, 21 Oct 2026 at 17:34, Tim Parenti <[email protected]> wrote:

> If we set aside Nunavut's misalignment for the time being and assume they
> will eventually adjust, the new colloquial understanding could actually be
> quite simple.  For example, the time scroller on CBCNN loops through the
> following times at the start of a show:
> 12:30 p.m. NT / 12:00 p.m. AT / 11:00 a.m. ET / 10:00 a.m. CT / 9:00 a.m.
> MT / 8:00 a.m. PT
> Starting 1 November, it's entirely plausible that it just says:
> 12:30 p.m. NT / 12:00 p.m. AT / 11:00 a.m. ET / 11:00 a.m. CT / 10:00 a.m.
> MT / 9:00 a.m. PT
> …with the notion that, at least for this winter, ET = CT in Canada.
> Simple enough, and those abbreviations may well be good enough, internal to
> Canada.
>

And indeed, that very maintaining of the traditional colloquial
abbreviations is more or less what CBCNN has gone with, during this
morning’s edition of *Rosemary Barton Live*, the network's first YouTube
simulcast which includes the broadcast scrollers.  The main difference from
my prediction was that an additional explicit CST reference was added
between CT and MT.
https://www.youtube.com/watch?v=kXcaIBEbziI
The clocks in the chyron didn’t appear on the stream until ~11 minutes past
the hour, right before a commercial break, but the first full loop (at
13:24 in the recording) read:
12:44 p.m. NT / 12:14 p.m. AT / 11:14 a.m. ET / 11:14 a.m. CT / 10:14 a.m.
CST / 10:14 a.m. MT / 9:14 a.m. PT

So on the national scale, CBC basically says MT = Alberta, southeastern BC,
and NWT, while PT = most of BC and Yukon.  Nunavut’s Kivalliq region can
look to Saskatchewan’s CST, but Kitikmeot region will have to adapt to
reading PT to get their MST for now.

Meanwhile, a promotional slide (at 22:30 in the recording) for special
coverage of the upcoming US midterm elections on Tuesday read “8 p.m. ET |
6 PT”.  None of the province-specific neologisms were anywhere in sight for
broadcast marketing, it seems.

* * *

CBC’s digital livestream feeds on YouTube, which have already leaned more
heavily into specific abbreviations rather than broad ones, were an
entirely different matter… and the manifestation of fairly straightforward
and common bugs amidst the transition quickly gets into the weeds.

Typically, the times shown for selected cities in the sidebars on these
platforms have used “S” in the winter for all zones, but only in the summer
for Saskatchewan’s CST and Yukon’s YST.  “D” has traditionally been omitted
when referring to daylight zones.  The changeover process has not been
without bugs over the years and has demonstrated an apparent sort of manual
switching between a “summer mode” and a “winter mode”, often back-and-forth
a bit a various points through the night.

Having scrubbed through the various feeds’ recent histories, the
traditional “summer mode” abbreviations (NT/AT/ET/CT/CST/MT/MT/PT/YST on
the national feed) were replaced last night with updated “winter mode”
abbreviations for this season (NST/AST/EST/CDT/CST/ABT/NTT/PCT/YST) that
largely *do* reflect local jurisdictional preferences.

Most of the sidebars on the various regional feeds rebooted at 04:00Z and
entered the apparent “winter mode”.  For cities in the Eastern, Atlantic,
and Newfoundland zones which had a fall back queued, the “winter mode”
applied the time change broadly, even before it should have.  This meant
that the Atlantic time zone feeds such as Nova Scotia, New Brunswick, and
PEI all appeared to fall back an hour early (12:59 a.m. AT → 12:00 a.m.
AST), and the Eastern time zone feeds such as Toronto, Ottawa, Windsor, and
Quebec all appeared to fall back two hours early (11:59 p.m. ET → 11:00
p.m. EST).   While the Atlantic regional feeds simply rolled through with
their early change, the Eastern regional feeds were brought back and forth
into and out of “winter mode” at various intervals:

03:59Z — 11:59 p.m. ET (correct)
04:00Z — 11:00 p.m. EST (an hour behind)
04:15Z — 12:15 a.m. ET (correct)
04:30Z — 11:30 p.m. EST (an hour behind)
04:45Z — 12:45 a.m. ET (correct)
05:00Z — 12:00 a.m. EST (an hour behind)
and then rolling straight through the actual clock change to
06:00Z — 1:00 a.m. EST (correct)

(As an aside, the NL feed did not have the rewind feature enabled, so I
couldn’t capture what happened there, but we can presume it may have been a
similar early change appearing at 04:00Z, i.e., 1:29 a.m. NT → 12:30 a.m.
NST.)

Meanwhile, also at 04:00Z, the effect on the Manitoba, Edmonton, and
Calgary feeds was a simple change of abbreviations (10:59 p.m. CT → 11:00
p.m. CDT and 9:59 p.m. MT → 10:00 p.m. ABT).  While the times on the
Manitoba feed rolled on just fine from there, the Edmonton and Calgary
feeds erroneously jumped forward at 06:00Z and started showing 1:00 a.m.
ABT even though it was only 12:00am UTC−6. An hour later at 07:00Z, they
jumped back to 1:00 a.m. ABT where they were supposed to be.  This is
consistent with a bug that’s previously afflicted the Saskatchewan feed,
which also erroneously jumped forward an hour at 06:00Z (11:59 p.m. CST →
1:00 a.m. CST) and back again at 07:00Z (1:59 a.m. CST → 1:00 a.m. CST).

Perhaps unsurprisingly, then, the times on the BC feed struggled for
longer.  The only provincial feed to use multiple timezones and
designators, its sidebar similarly rebooted at 04:00Z with just
abbreviation changes (8:59 p.m. PT → 9:00 p.m. PCT for most, but
maintaining “MST” for Fort Saint John and “MT” for Cranbrook which is an
hour ahead).  But the BC feed was also brought in and out of “winter mode”
similar to the feeds out east, though at different times.  This mostly just
affected abbreviations at first, but once Toronto had fallen back at 06:00Z
it grappled with the same bug as the other western zones:

03:59Z — 8:59 p.m. PT / 8:59 p.m. MST / 9:59 p.m. MT (correct)
04:00Z — 9:00 p.m. PCT / 9:00 p.m. MST / 10:00 p.m. MT (correct)
04:15Z — 9:15 p.m. PT / 9:15 p.m. MST / 10:15 p.m. MT (correct)
04:30Z — 9:30 p.m. PCT / 9:30 p.m. MST / 10:30 p.m. MT (correct)
05:15Z — 10:15 p.m. PT / 10:15 p.m. MST / 11:15 p.m. MT (correct)
06:00Z — 12:00 a.m. PCT / 12:00 a.m. MST / 1:00 a.m. MT (an hour ahead)
07:00Z — 1:00 a.m. PCT / 1:00 a.m. MST / 1:00 a.m. MT (an hour ahead except
for Cranbrook)
08:00Z — 1:00 a.m. PCT / 1:00 a.m. MST / 2:00 a.m. MT (correct)

This starts to hint more closely at how timestamps are actually being
handled in these systems in a way that would create these multi-layered
bugs — the different “modes” likely change the number of hours being
added/subtracted from a reference time, but the math is being done on a
timezone-aware scale which has a fall back of its own, and this is all
quasi-papered over with abbreviation lookups tied to location and “mode”,
not timekeeping.

The other feeds that use multiple timezones and designators are the
national and North feeds.  The “winter mode” was activated on the national
feed ~03:15–03:30Z, ~04:00–04:30Z, and then from 05:30Z onwards; as well as
on the North feed from 04:00Z in much the same way as the other regional
fields.  When active, the “winter mode” similarly applied the change early
to zones in the east — until 06:00Z, when clocks in Toronto actually
switched — at which point, timestamps for points east were fine while those
out west which weren’t supposed to change became wrong for a bit.  Much
like the Saskatchewan, Edmonton, Calgary, and BC feeds, timestamps meant
for UTC−6 given with CST, ABT, and NTT labels were an hour ahead of where
they should have been until 07:00Z, while those meant for UTC−7 and given
with PCT or YST remained an hour ahead until 08:00Z.

The theory is supported to a few sharper “corner” cases in addition to the
common buggy ones:

Between 05:30Z and 06:00Z, when clocks should have read:
12:30 a.m. CDT / 1:30 a.m. EDT / 1:30 a.m. AST / 2:00 a.m. NST
…they instead read:
12:30 a.m. CDT / 1:30 a.m. EDT / 1:30 a.m. AST / 1:00 a.m. NST
…with Newfoundland appearing to have fallen back a second time until this
was corrected once Toronto actually did fall back.

On the other end of the spectrum, in addition to the buggy YST timestamps
persisting during the 07:00Z hour, the North feed gave:
2:00 a.m. EST for Iqaluit (correct)
1:00 a.m. CST for Rankin Inlet (correct)
1:00 a.m. MST for Cambridge Bay (right time, misleading designation)
This was also resolved an hour later once Cambridge Bay actually fell back
at 08:00Z.  The North feed had completely removed the sidebar for the
entire 06:00Z hour; if it hadn’t, something similar would likely have
happened with Rankin Inlet then, too.

And setting the implementation bugs aside, the North feed did ultimately
result in showing Kuujjuaq in Nunavik falling back to EST on UTC−5 per
their clarification last month.

Throughout the whole ordeal, only Manitoba time ticked along correctly on
both the national and Manitoba feeds.  Given that that’s just UTC−5, which
is standard time at the Toronto home base, this is perhaps not too
surprising.  Though it is a bit ironic given which jurisdictions made their
timekeeping announcements when.  And now Cranbrook — which, early in this
process, we thought could be an exception — is the only location that still
shows a two-letter abbreviation (“MT”) on any of the CBC feeds.

--
Tim Parenti

Reply via email to