What is MTU?
MTU (Maximum Transmission Unit) is the largest packet an interface can carry in one go. On Ethernet the default is 1500 bytes.
It looks like a minor detail, but if any link along the path uses a lower MTU the result is a distinctive fault: small requests work while large transfers stall.
- 1
The device sends a 1500-byte packet
- 2
A link on the path accepts 1400 bytes
- 3
The packet is fragmented or dropped
- 4
Small requests work, large ones stall
When ping works but file transfer or VPN stalls, this is the first thing to suspect.
The classic symptom: 'ping works but the site won't load'
Ping sends small packets, so it is unaffected by an MTU mismatch. Downloading a file, opening an application over VPN or receiving a large API response stalls on the very same path.
That is why monitoring that only pings cannot see this fault. Checks of different sizes and layers have to be read together.
- The VPN connects but the internal application never opens
- Small pages load while large files stop halfway
- The problem appears only at one site or on one link
Why MTU drops
The usual causes are transport methods that add headers to the packet: PPPoE links, VPN tunnels and some mobile connections all narrow the usable space.
A packet must fit the smallest MTU on the path. If it does not, it is either fragmented or dropped because of the do-not-fragment flag. Fragmentation is not a real fix either — it costs performance and is blocked in some setups.
Finding the right value
The method is to send pings of different sizes with fragmentation disabled and find the largest one that passes: ping -f -l on Windows, ping -M do -s on Linux and macOS. Add 28 bytes for the IP and ICMP headers to get the MTU.
In Sentry this kind of link problem becomes visible when checks at different layers are read together: an address answering while the service check times out is a clear signal. Changing MTU on a link or device is out of scope and remains an operator decision.