Packet loss on the route to EUserv
Summary
Connections to my EUserv server and to the provider’s website lost about ten percent of their packets; the problem became visible from the network node 149.14.211.218 onwards. The measurement showed roughly ten percent packet loss. Both my own EUserv server and the website euserv.de were affected.
Ideas
- Comparison targets separate a problem of your own server from a shared network path.
- A traceroute narrows down where packet loss starts to appear.
- Measurements give hosting support a better basis than a general fault report.
- A conspicuous hop alone does not prove the cause of the packet loss.
Insights
- Network faults can be narrowed down systematically with several targets and repeated measurements.
- The first conspicuous router can be the cause, a symptom or just a poor ICMP responder.
- Short public fault reports become technically traceable through concrete measurements.
Facts
- The loss was observed from the IP address 149.14.211.218 onwards.
- The report was written on 5 April 2019.
Recommendations
- Measure problematic routes to several targets at the same time.
- Document time, source network, target, packet loss and the complete path.
- Repeat measurements before you name a single network node as the cause.
References
Links to the original source and the Web Archive open in a new tab.