The ITU's October 30 timing handbook update is a useful prompt for broadcasters to test the failure modes between a reference clock, an IP media network and the devices relying on it.
Why a timing handbook matters to master control
On October 30, 2026, the International Telecommunication Union released the first update since 1997 of its Handbook on Selection and Use of Precise Frequency and Time Systems. The ITU announcement highlights GNSS and terrestrial references, fiber time transfer, optical clocks, and monitoring of time services. The 2026 handbook is available free.
The handbook is not a new SMPTE ST 2110 compliance rule. Its relevance is operational: IP media production needs more than an available network path. Cameras, audio interfaces, switches and processing nodes also need a trustworthy shared timebase.
A facility may have redundant media networks yet still depend on a common timing failure point. A packet path can remain up while clock quality deteriorates. That is a different incident from lost video packets, and it requires different alarms.
The 2027 UTC change adds a second question
The 28th General Conference on Weights and Measures decided that continuous UTC becomes effective May 20, 2027. Its Resolution 5 increases the allowed difference between UTC and Earth-rotation time, enabling UTC to continue without future leap-second adjustments.
That is a change to the international time-scale policy, not an instruction to replace PTP equipment or a claim that existing systems will fail next May. Facilities should nevertheless inventory where UTC offsets, leap-second announcements, timecode and log timestamps are interpreted. In particular, test the behavior of legacy receivers and management software rather than assuming every device handles the transition identically.
Do not confuse accurate wall-clock timestamps with phase-aligned media. An NTP-synchronized monitoring server can log an incident consistently while a PTP endpoint is still out of alignment with its video or audio peers.
Five failure tests worth scheduling
- Remove the GNSS reference under controlled conditions. Record grandmaster state, holdover behavior, offset trend and how long the plant remains inside its own approved timing tolerance. Verify that alarms appear before media errors, if the system supports such warning.
- Fail the active grandmaster. Check the elected replacement, the time required to stabilize, and whether receivers change reference cleanly. Inspect priority, clock-class and best-master-selection behavior rather than trusting a green redundant-power indicator.
- Stress the timing distribution path. During a maintenance window, introduce representative media load and inspect boundary-clock performance, delay variation, dropped PTP messages and endpoint offsets. A healthy multicast video stream does not establish healthy PTP.
- Test a path or switch failure. Compare the media recovery path with the timing recovery path. SMPTE ST 2022-7 can protect eligible duplicated media streams, but it does not by itself guarantee a resilient timing hierarchy.
- Reconcile timestamps across systems. Capture a known event and compare production equipment, PTP monitoring, NOC alarms and recording metadata. Identify which systems use UTC, local time or another reference, and confirm how they handle offset and discontinuity information.
These are proposed acceptance tests, not measurements from a real broadcast plant. Set pass/fail thresholds from the equipment specifications, applicable profiles and the facility's own engineering requirements.
Ask for evidence, not a clock icon
SMPTE's discussion of PTP error conditions covers interrupted message flows, incorrect time information and degraded transfer quality. A Cisco/Panasonic IP-media validated design updated January 21, 2026 includes PTP synchronization, failure-scenario and stress testing as separate verification activities.
For a commissioning or maintenance review, ask the vendor or engineering team for a topology showing grandmasters, timing domains, boundary clocks, GNSS sources and independent failure domains. Require trend evidence before, during and after a controlled fault. Record who owns the alarm and the recovery decision.
Bottom line: Redundant IP media transport is not the same as redundant time. The ITU update is a timely reason to prove both.
Image: N. Phillips/NIST, real photograph of a ytterbium optical lattice clock, from Wikimedia Commons. U.S. federal government public-domain work. Historical laboratory image, not a broadcast facility or a depiction of the October 2026 announcement. Planned 1600×838 crop; no other edits.
