Live network lab

Live ISS stream. Three players. Three transports.

Watch live ISS camera views in your browser.

Compare QUIC, AMT, and native multicast/DIMT for a live stream from the International Space Station. Live signals show the last 60 seconds of latency, frame rate, loss, FEC, and physical multicast ingress throughput. Physical-path boundary latency stays blank until packet, decode, render, and transport attribution evidence is complete.

Play the live ISS camera views in this browser over QUIC. A verified local Blockcast bridge can expose explicit AMT or native multicast choices for a physical-path test.

Browser playback

Playback stays in this browser

Browser playback is active over QUIC while an optional local bridge is checked.

Checking player origin availability.

Live signals

Waiting for the selected player.

Publisher → media admission—

Rendered FPS—

Loss—

FEC recovered—

ABRWaiting

—

Diagnostics

Physical evidence: waiting for a selected transport.

ABR status: waiting for player telemetry.

Latency target: <33 ms.

What the <33 ms target measures

The <33 ms budget covers calibrated Blockcast publisher MMTP-send to player media admission and rendered-frame timing only. Players do not publish a versioned live-edge/buffer-distance measurement. NASA upstream HLS ingest/transcode and source-to-glass delay are excluded.

Transport comparison

p50, p95, and max combine publisher → media admission and publisher → rendered frame samples; every sample must stay strictly below 33 ms.

Transport	Samples	p50	p95	Max	Budget
QUIC	Waiting for evidence
AMT	Waiting for physical evidence
Native / DIMT	Waiting for physical evidence

Latency · ms

FPS · frames/s

Loss · %

FEC · blocks/s

Throughput · Mb/s

Waiting for the local multicast bridge.

Each player exposes aggregate playback counters through the same component contract. The rendition selector receives only catalog-derived video track names and display metadata. Physical native/DIMT and AMT ingress are counted once before player fan-out. Missing values and unproven physical-path boundary latency remain chart gaps; they are never estimated.

Browser-owned transport

Android, iOS, desktop IWA, and extension packages provide only local discovery and thewindow.multicast bridge. This tab keeps catalog resolution, decoding, rendering, and controls.

Optional local bridge

Keep watching here

Browser playback stays on explicit QUIC/MoQ by default. With a verified bridge, choose AMT or native multicast on the Shaka player when you want a physical-path test.

Android · iOS · desktop

Bridge-only packages

SDK apps, IWAs, and extensions may supply the local transport capability. They do not host a second player or require an app handoff.

Checking for the Blockcast browser bridge…

From viewer to broadcaster

This public demo is playback-only and never receives publishing credentials. Account-scoped publishing remains a roadmap item until namespace and node authorization are implemented and verified.

Planned

Publish with WHIP

Account-scoped WHIP endpoint creation is not available from this demo yet. It will ship only after signed-in namespace and node authorization are wired end to end.

Required boundary

Own your tracks

Publishing must bind track discovery, subscriptions, and revocation to the logged-in namespace. The public playback catalog does not grant that authority.

OCM

Rent topology access

Use the Open Capacity Marketplace to reserve the regional nodes and network paths that carry your live namespace to the audience.