Latency, jitter, loss.
What's happening in your MoQ session?
MoQ Analyzer reads the mlog files from your publisher, relay, and subscribers.
It reveals metrics like pub to relay latency, intra-relay latency, object loss, jitter, and others.
It runs 100% in your browser. Your logs stay on your machine.
No logs at hand? Load a sample: 10 mlog files all vantages, or stock 2 mlog files relay only.
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 named <cid>_client.mlog or <cid>_server.mlog, plain or
gzipped.
- Relay logs alone: relay dwell, object bitrate, interarrival. Stock moq-rs works.
- Both ends of a connection: adds object loss.
-
Every host, with
reference_timeand synced clocks: adds latency per leg and end to end.
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.