MTU and Jumbo Frames: When It Matters

MTU is one of the most boring and most damaging silent issues. Knowing the four common cases catches most.

Why MTU matters

Wrong MTU: packets fragment; throughput collapses; intermittent latency.

Symptoms vague; root cause subtle.

Four scenarios

• 1. VPN tunnels (encapsulation overhead).
• 2. Cross-cloud links (provider MTUs differ).
• 3. Container networking overlay (additional overhead).
• 4. Jumbo frames in datacenter (gain throughput).

Diagnostic pattern

Test: ping -M do -s 1472 destination. If fails, MTU is < 1500 somewhere.

Trace: where exactly the path breaks.

Cloud defaults

AWS VPC default: 9001 (jumbo).

GCP default: 1460.

Azure default: 1500.

Mismatched MTU at cloud boundary = silent fragmentation.

Antipatterns

• Default MTU through VPN. Fragmentation.
• Jumbo frames without end-to-end support. Drops.
• Diagnosing throughput issues without checking MTU. Wasted hours.

What to do this week

Three moves. (1) Apply this pattern to your highest-risk network path. (2) Measure the failure mode rate before/after. (3) Document the change so the next incident-responder inherits the knowledge.