Latency, jitter, loss.
What's happening in your MoQ session?
MoQ Analyzer reads the mlog files your publisher, relays, and subscribers write, and shows the latency on each leg: publisher to relay, time inside the relay, and relay to subscriber. It runs 100% in your browser. Your log data doesn't leave your machine.
Some features under development.
From a real capture
One publisher, one relay, and four subscribers, each on its own AWS host. Here's where the time went.
Capture real-6pop, 227,651 object deliveries measured end to end. Clocks synced with chrony. Analyzed
2026-09-20.
What it needs from your logs
mlog files (qlog-format event logs for MoQT) from each host in the session. Each file needs a
reference_time and real stream_id values, because that's how the analyzer lines up
the same object across hosts. Not every implementation writes these yet.
Send me your mlogs
If you run a MoQ relay, publisher, or player, I'd like to test against your captures, including ones that don't load yet. Email hello@moqanalyzer.com.