Trippy CLI
Terminal diagnostics combine traceroute and ping so agents can compare routes, latency and missing probe responses.
- 8,140 ★ on the repository
- Last commit
- Apache-2.0
Extended access
Why this level
- The CLI sends probes and may require elevated network privileges; reports expose route addresses.
Install
Manual install
cargo install trippy --lockedFirst command example in the README itself; requires a working Rust/Cargo environment.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The CLI sends probes and may require elevated network privileges; reports expose route addresses.
This is third-party code. Review the repository files before installing.
What it does
Users can observe where latency rises or responses disappear along an unstable route. Trippy sends probes and updates a hop table in the terminal. Keep the window open during an outage to compare measurements before and after the connection recovers. A fixed number of rounds can produce JSON, CSV or Markdown for a support request. Select TCP, UDP or ICMP and ports at launch. An agent can interpret the report alongside application evidence; Trippy does not change routes or repair network settings.
Who it is for. Network engineers inspecting a route to their service and sharing measurements with an agent.
Good fit when
- An unstable connection needs per-hop latency comparison.
- A support report needs a fixed number of probe rounds.
- Diagnostics must use a particular interface.
- ICMP results do not explain a problem, and an engineer compares them with a TCP trace to the service port.
Not a fit when
- The task requires automatic route or firewall changes.
- Probing the chosen target is not authorized.
- One measurement will be treated as proof of an application failure’s cause.
Example request
Prepare five tracing rounds to the approved server with JSON output and explain which parameters must stay fixed for comparison.Limitations
Unprivileged tracing is macOS-only with `--unprivileged`; Windows needs an Administrator session, while Linux and BSD require separate privilege setup. Multiple targets can be traced simultaneously only with ICMP; use one target for TCP or UDP. Geographic information needs a separately supplied `.mmdb` GeoIP file. Latency and missing replies depend on protocol and measurement time; one report does not establish the cause of an application failure.
How to disable. Retain needed results before exiting Trippy. Revoke separately assigned persistent diagnostic privileges when no longer needed.
FAQ
How do I get JSON after five rounds?
Use `trip example.com -m json -C 5`, replacing the address with the approved target.
Can I choose TCP instead of ICMP?
Yes. Select `--tcp` or `-p tcp`. The guide uses `trip example.com -p tcp -P 443` for the HTTPS port; substitute your server.
How do I choose an interface?
The examples use `-I` with the interface name.
Does it change network routes?
No. It diagnoses the selected path.
Where does address geography come from?
Supply a database path with `--geoip-mmdb-file`, for example `GeoLite2-City.mmdb`. Geographic labels are unavailable without the file.
Discussion
No questions or reviews yet.
Related
CLI toolsgping is a measurement-chart CLI whose --cmd mode compares command durations by repeatedly running them on the computer.
During a network incident, an agent retrieves the route to a service while the administrator controls diagnostic access.
witr identifies the process holding a port or file and shows its startup chain, supervising service or container context.
Official Dynatrace skills for agents: DQL, traces, logs, Kubernetes, cloud and security work inside Claude Code and Cursor.
bottom displays processes, CPU load, memory, network and disks in the terminal with graphs, search and configurable widgets.
Searchable processes and configurable columns help locate CPU load, listening ports and child commands from a terminal.
README in short
Keybindings, colors and columns are configurable. Linux, BSD, macOS and Windows have platform-specific execution requirements.