Home / i-Tracker / Jitter and packet loss

i-TrackerNetwork bandwidth performance monitoring and tracing

Measure jitter and packet loss, not just once.

Calls drop, the video conference stutters, but the speed test shows full bandwidth. Voice and video depend on other values: how evenly the packets arrive and how many get lost on the way. i-Tracker measures both via UDP on a schedule and keeps every result.

01BackgroundWhat disturbs voice and video

Bandwidth does not help when packets are missing.

Voice and video calls send their data via UDP. A lost packet is not resent, it is simply missing: the voice sounds choppy, the picture freezes. Jitter is the variation in transit time. If packets arrive unevenly, the receiver has to buffer, the conversation lags and late packets are dropped.

iperf3 measures both in UDP mode: it sends at a fixed rate and counts what arrives and how. For example 30 seconds at 10 Mbit/s from the server to your own machine:

iperf3 -c iperf.example.net -u -b 10M -t 30 -R
Jitter
Variation in transit time between packets, in milliseconds.
Packet loss
Share of UDP packets that do not arrive, in percent.
UDP bandwidth
Without a value, iperf3 only sends 1 Mbit/s. Measure at the rate your calls really need.
Timing
A single measurement only shows the moment. Problems at certain times of day only show up in a series of measurements.
02With i-TrackerScheduled UDP measurement

Every measurement kept with jitter and packet loss.

In i-Tracker you create a server profile per endpoint, with UDP as the protocol and the desired UDP bandwidth. It measures at the configured interval, every 30 minutes by default, and stores every result. The details of a measurement show jitter and packet loss per direction, the dashboard the averages per server.

Optionally it also records the route to the target after every measurement. That shows which networks a poor measurement went through, see traceroute on a map.

Measurement
UDP in download, upload or both at once, 1 to 300 seconds, with a selectable UDP bandwidth.
Values
Jitter in milliseconds and packet loss in percent per direction, plus the raw iperf3 output.
Schedule
A separate interval per server. Only one measurement runs at a time, so measurements do not distort each other.
Endpoint
iperf3 as a server where the calls go: data center, branch office, cloud region.
Guest view
Without sign-in a read-only view of the results, for example for a screen in the office. Can be switched off.
03SetupSet up once, then it measures on its own
  1. 01

    Start the endpoint

    On a machine at the other end, iperf3 as a server: iperf3 -s.

  2. 02

    Install i-Tracker

    On Windows as a service, on Linux with Docker.

  3. 03

    Create a server profile

    Address, protocol UDP, UDP bandwidth and interval.

  4. 04

    Analyze

    Jitter and packet loss on the dashboard and in every measurement, with a growing history.

04FAQFrequently asked questions about jitter and packet loss

How do I measure jitter and packet loss?

With iperf3 in UDP mode between two points: iperf3 -s on one side, iperf3 -c with -u and a bandwidth on the other. i-Tracker runs this measurement on a schedule and stores every result.

Which UDP bandwidth should I set?

Roughly as much as voice and video really use at the same time. Without a value, iperf3 only sends 1 Mbit/s. Set too high, the measurement fills the line itself and then causes the packet loss it is meant to measure.

Why does a TCP measurement show no packet loss?

TCP resends lost packets. There, loss only shows up as lower throughput. That is why iperf3 measures jitter and packet loss only with UDP.

Does i-Tracker alert on high packet loss?

No, it does not send notifications. The values are on the dashboard and in every measurement, and the guest view shows them without sign-in, for example on a screen in the office.

What does i-Tracker cost?

Nothing. i-Tracker is free and open source (AGPL-3.0).