MTR
Network diagnostic tool combining traceroute and ping.
Open the official app on www.bitwizard.nl
This tool is hosted by its maintainers. Click below to open www.bitwizard.nl in a new tab — it's their official demo.
Browse network tools →What's next with MTR?
Choose how you want to get started.
Use it free
Open the official tool or demo — no account needed.
Self-host it
Run the open-source version on your own infrastructure.
What is MTR?
MTR (My TraceRoute) is a network diagnostic tool that merges the functionalities of 'traceroute' and 'ping' into a single utility. It analyzes the path between a host running MTR and a specified destination, identifying each network hop and assessing link quality through ICMP ECHO requests. This tool is primarily used by network administrators, developers, and IT professionals to troubleshoot connectivity issues, monitor network performance, and diagnose routing problems. MTR solves the problem of fragmented network diagnostics by providing real-time statistics on latency, packet loss, and hop reliability, offering a comprehensive view of network health without requiring multiple tools. Its open-source nature under the GPL-2.0 license ensures widespread accessibility and community-driven development, making it a reliable choice for both local and remote network analysis.
How it works
MTR combines traceroute's ability to map network paths with ping's capacity to measure latency and packet loss. It continuously sends ICMP ECHO requests to each hop, compiling statistics like round-trip time and packet loss rates. The tool is designed for diagnosing intermittent connectivity issues, identifying routing anomalies, and evaluating the performance of network infrastructure. Its real-time data helps users pinpoint problematic segments in the network path. MTR provides real-time metrics for each hop, including latency, packet loss, and jitter. It supports IPv4 and IPv6, and its output includes detailed hop information such as IP addresses, hostnames, and response times. The tool also allows filtering and customizing the diagnostic process through command-line options.
How to use it
- 1Install MTR via its GitHub repository or BitWizard website. 2. Run the tool with the destination host as an argument, e.g., `mtr google.com`. 3. Monitor the output, which displays hop-by-hop statistics in real time. 4. Use options like `-c` to specify the number of packets or `-w` to set a timeout for responses. Practical tips include using `mtr --help` to explore advanced options, running it on a stable network connection, and cross-referencing results with other tools like `traceroute` or `ping` for verification.
What it can do
- network diagnostics
Use cases
Assumptions and limitations
Assumptions
- source: https://github.com/traviscross/mtr
- license: GPL-2.0 — free to use
- privacy: Self-hosted — you control your data
Limitations
- Relies on ICMP ECHO requests, which may be blocked by firewalls or network security policies.
- Lacks a graphical user interface, requiring command-line proficiency for operation.
- Does not support real-time graphing or visualization of network performance trends.
- Limited to IPv4 and IPv6; does not handle other protocols like IPv5 or experimental networks.
- May not provide detailed information on non-ICMP-based network issues (e.g., TCP/UDP-specific problems).
Understanding the result
Network diagnostic tool combining traceroute and ping.
Tool details
- Clearly flagged when a network request is needed.
- No account, no sign-up, and no tracking of your content.
- Powered by (MIT).
- Built with
- (traviscross/mtr)
- License
- MIT
- Runs locally
- No — requires a network request
- Verification
- Not yet verified
- Input
- Query
- Output
- Text
Built with traviscross/mtr. OpenToolVault provides the discovery and browser interface while crediting the original project maintainers.
- Built with
- License
- MIT
Open-source project
OpenToolVault is an independent directory. We are not affiliated with or endorsed by this project.
References
- / — GitHub Repository
Upstream project · GitHub
- GPL-2.0 License
Upstream project
Frequently asked
What is MTR and how does it differ from traditional traceroute or ping tools?
MTR integrates the functions of traceroute and ping into a single tool, providing continuous real-time statistics for each network hop. Unlike traditional traceroute, which only maps the path once, MTR sends repeated packets to measure reliability and latency. Compared to ping, which only checks if a host is reachable, MTR offers detailed insights into the entire network path, making it more comprehensive for troubleshooting.
How does MTR analyze network performance?
MTR sends ICMP ECHO requests to each hop along the path to a destination host. It records metrics such as round-trip time, packet loss, and jitter for each hop. By continuously sending packets, it generates a live view of network stability and performance, allowing users to detect anomalies like latency spikes or intermittent connectivity issues.
How do I run MTR to diagnose a connectivity issue?
Install MTR from its GitHub repository or BitWizard site. Open a terminal and execute `mtr [destination]`, replacing [destination] with the host you want to test (e.g., `mtr example.com`). Observe the output for hop-by-hop statistics. Use options like `-c 100` to send 100 packets or `-w 5` to set a 5-second timeout for responses. Analyze latency and packet loss to identify problematic segments.
How does MTR compare to alternatives like traceroute or ping?
Traceroute maps the path to a destination but only provides a one-time view, while MTR offers continuous monitoring of each hop's performance. Ping checks reachability but lacks detailed path analysis. MTR's strength lies in its ability to combine both functions, making it more efficient for diagnosing complex network issues. Alternatives like `traceroute` or `ping` are simpler but less comprehensive for in-depth troubleshooting.
What should I do if MTR shows high packet loss at a specific hop?
High packet loss at a hop may indicate a congested router, a faulty link, or a firewall blocking traffic. First, verify the destination's availability using `ping` or `traceroute`. Check if the issue persists across multiple test runs. If the problem is consistent, contact your ISP or network administrator to investigate the specific hop. Use MTR's `-c` option to send more packets and confirm if the loss is random or systematic.