YouTube
Continuous broadcast
Watchdog, ingest and same URL observation loading
Relay outputMeasuring
Watch YouTube ↗24/7 flight tracking · live operations
Live skies. Clear signals.
Your view of the Tokyo skies, with YouTube and Twitch status, reliability history and relay health in one place.
Loading the latest observations…
Right now
Two destinations. One live feed.
Twitch
Daily session renewal
Provider observation loading
Relay outputMeasuring
Watch Twitch ↗History & engineering objectives
Broadcast reliability
Operational reliability
Windowed observations, engineering references and measurement coverage. Each indicator retains its own definition.
measurement loading
Each card shows its own measurement window (for example, rolling 7 days).
Measurement data ↗Twitch session reliability
Windowed observations, engineering references and measurement coverage. Each indicator retains its own definition.
measurement loading
Window7 days · primary assessment window
Measurement data ↗Measurement history
currentMeasurement history loading
Provider LIVE history · last 24 hours
Provider LIVE · last 24 hours
Each bar = one hourLIVEOFFLINEUnknown / missingOlder → latest
How these indicators are measured
One source observation is assigned to its original minute. Cached responses never add successful minutes. Missing or failed observations stay visible. Daily planned reconnects count as downtime in the availability and relay indicators.
7 days is the primary SLO window; 24 hours provides early feedback. An assessment needs a complete window and at least 99% known observations. Conservative availability counts only confirmed good minutes over all expected minutes. A high observed value alone does not establish that the objective was met.
The daily renewal objective is 100%: the API must observe OFFLINE followed by LIVE with a different stream ID and a new start time, within 600 seconds of 00:00 JST. Unobserved earlier renewals remain unknown.
The APIs report provider state and relay counter progress. Playback, audio quality and visual correctness require separate receiver checks. YouTube retains its existing measurement definitions and history in its reliability tab.
Download the public measurement data ↗Current Twitch session & last playback check
Delivery & infrastructure
One feed through the relay
Measured transport · OCI resources · session schedule
The broadcast path
Normally, Dell uploads one feed to OCI, which forwards it to YouTube and Twitch. If the relay path fails, Dell automatically starts a direct feed to YouTube and stops it after 5 minutes of healthy relay.
DellEncoder + sender
↓ Not observed
OCI VMSingle input relay
↓ Not observed
YouTubeRelay output
↓ Not observed
TwitchRelay output
DellDirect backup
↓ Route not observed
YouTubeBypasses OCI
Observed link progressStandby or unobservedInferred direct delivery
Current route is not confirmed until fresh observations arrive.
Relay infrastructure
OCI VM
UnknownCPU usage—
Memory usage—
Disk free—
Relay processUnknown
Outputs progressing— / 2
Relay service restarts—
Relay observation loading
Detailed operations & evidence
Decision checks
-
Guardrails
home line / API / ADS-B freshness
24h trends
-
Evidence checks
-
Recent events
-