Blockcast Timing Stream

Client UTC --:--:--.---

Virtual UTC -

Source UTC -

status: idle

Packets0

Rate0.0 pps

Bitrate0.00 Mbps

Valid sync0

Path delay (1s median)-

Delay p50-

Delay p95-

Raw clock delta-

Browser queue-

Server minus client-

Calibration RTT-

Clock uncertainty-

Clock calibrationuncalibrated

Timestamp sourcecallback

Receive pathauto

Confirmed lost0

Reordered0

Last invalid-

Delay over time

waiting for samples

MoQ QUIC delay native SSM delay AMT delay kernel to browser callback, when available

Path	Latest	p50	p95	Browser queue p50	Raw loss	Lost	Reordered	Samples
Waiting for timing samples

Client UTC is the browser wall clock; Virtual UTC applies the measured server-minus-client offset without changing system time; Source UTC is the latest BCTM sender timestamp. Observations use performance.timeOrigin + performance.now() at browser callback entry. If the Direct Sockets build supplies per-datagram receiveTime, the app uses it and reports browser queueing separately. Without a BCTM clock model or GM-aligned hardware timestamps, these values remain application-path observations, not pure one-way network latency.

Events