MTR Report
MTR combines traceroute and ping: it sends ten ICMP echo probes to every hop on the path and reports, per hop, how many were lost and how the round-trip time varied. That separates a router that is merely slow to answer from a path that really loses traffic, which is the evidence a network operator asks for.
- Limits No file upload · Up to 75 runs a day
- Where it runs Runs on our server; no file is uploaded.
- Cost Free, with the limits above. No account needed.
Where to find it
Every address below opens the same tool. The first address is the one to bookmark and share.
- mtr.openvibe.toolsPrimary
People also call this
What it's for: Run an MTR report from our server to any host: ten probes per hop with loss, last, best, average and worst time and jitter (StDev), plus each hop's network. IPv4 and IPv6.
What trips people up: A middle hop shows loss but the destination shows none. Is something wrong? Usually not. Routers limit how often they answer probes addressed to themselves while forwarding traffic normally. Loss that starts at a hop and carries on to every hop after it, including the destination, is real loss.
- mtr online
- mtr report
- my traceroute
- packet loss test
- network path analysis
- jitter test
Use it from code
POST https://openvibe.tools/api/v1/tools/mtr/run- Needs a token with
tools.net.probe, granted to partners only; people use the page. - It answers with the result.
curl -X POST https://openvibe.tools/api/v1/tools/mtr/run \
-H 'Authorization: Bearer $OPENVIBE_TOKEN' \
-H 'Content-Type: application/json' \
-d '{"input":{"target":"example.com"}}'Inputs: JSON Schema · OpenAPI · from JavaScript: tools.run("mtr", …) in openvibe-sdk · How the API works
Similar tools
All Network ToolsOne account works on every site. Open source and community-run.