Packet loss is one of the most frustrating network issues. It causes jitter in VoIP calls, lag in applications, and slow file transfers. A simple ping test tells you that packets are being lost, but not where.

To determine whether the problem lies within your own network, the signetbreedband network, or with a third party, use MTR (My Traceroute). MTR combines the functionality of ping and traceroute to provide a real-time overview of every node (hop) on the path to your destination.


What is MTR?
While a traceroute is a snapshot in time, MTR continuously sends packets. This allows you to see trends and percentages, making it possible to distinguish between an occasional glitch and a structural problem.

Installing and using MTR

Depending on your operating system, you will use a different tool, although the functionality is identical.

Windows

Use WinMTR.

  1. Download WinMTR.
  2. Run as Administrator.
  3. Enter the host and click Start.

macOS

Use Homebrew.

  1. Open Terminal.
  2. brew install mtr
  3. sudo mtr 8.8.8.8

Linux

Via the repository.

  1. sudo apt install mtr
  2. mtr 8.8.8.8
Crucial for reliability:
Let the test run for at least 100-200 cycles (Sent). A test of only 10 packets is statistically irrelevant and leads to incorrect diagnoses.

Interpreting the output

Reading an MTR report is where most mistakes occur. The golden rule is: Always look at the final hop.


ICMP Rate Limiting
Many routers prioritize data traffic over ICMP (MTR). A router may drop MTR packets (showing loss) while forwarding normal traffic perfectly. This is not packet loss, but a router security setting.


Visual scenario analysis

Use the scenarios below to determine where the fault lies. Pay close attention to the progression of the Loss % column.

Scenario A: Issue in local network

Characteristic: Packet loss starts immediately at the first hop (your own router/gateway) and persists or increases toward the endpoint.

Diagnosis: Defective cable, overloaded switch, or malfunctioning router within your premises.

1. 192.168.1.1   [ 15% Loss ]
2. 80.x.x.x      [ 15% Loss ]
3. 10.x.x.x      [ 16% Loss ]
...
10. 8.8.8.8      [ 15% Loss ]
Loss persists from start to finish
Scenario B: ICMP Rate Limiting (False alarm)

Characteristic: You see packet loss on an intermediate hop, but subsequent hops (including the endpoint) show 0% loss.

Diagnosis: The router at that specific hop is ignoring MTR packets. There is no actual outage.

1. 192.168.1.1   [ 0% Loss ]
2. 80.x.x.x      [ 0% Loss ]
3. 10.x.x.x      [ 40% Loss ]
4. 10.x.x.y      [ 0% Loss ]
...
10. 8.8.8.8      [ 0% Loss ]
Loss is isolated to a single hop
Scenario C: Issue in signetbreedband network

Characteristic: The first hops (local network) are clean, but loss begins consistently once traffic enters our network.

Diagnosis: There is an issue in the transport layer or at the signetbreedband peering point.

1. 192.168.1.1   [ 0% Loss ]
2. 80.x.x.x      [ 0% Loss ]
3. signet-core-1   [ 10% Loss ]
4. signet-edge-1   [ 12% Loss ]
...
10. 8.8.8.8      [ 11% Loss ]
Loss starts at provider and continues

Next steps

Have you determined that the packet loss consistently starts within our network and continues to the destination? Please open a ticket. To accelerate the resolution, provide the following information:

  • A screenshot or text export of the complete MTR session.
  • The number of packets sent (minimum 100).
  • The destination IP address you tested.

Sources