Trippy — A Network Diagnostic Tool Combining traceroute and ping
Trippy is a modern TUI network diagnostic tool that fuses traceroute and ping into one live view, supporting ICMP/UDP/TCP, IPv6, GeoIP, and CSV/JSON export.
What it is
Trippy is a modern terminal-based network diagnostic tool that combines the functionality of traceroute and ping into a single interactive interface. It displays network hops, round-trip latency, jitter, and packet loss in a continuously updated TUI (terminal user interface). Trippy supports ICMP, UDP, and TCP probes and renders the data as a live table or chart.
Network engineers, DevOps teams, and developers debugging connectivity issues benefit most. Trippy replaces the workflow of running traceroute and ping separately, then correlating the output manually.
How it saves time or tokens
Traditional network diagnostics require running traceroute to find the path, then pinging specific hops to measure latency. Trippy does both simultaneously and continuously. The live TUI updates in real time, so you can spot intermittent packet loss or latency spikes as they happen rather than parsing static output. The single-command workflow saves the overhead of running and comparing multiple tools.
How to use
- Install Trippy:
# macOS
brew install trippy
# Linux (Debian/Ubuntu)
sudo apt install trippy
# Cargo
cargo install trippy
- Run a basic trace:
trip example.com
- The TUI displays each hop with live latency, jitter, loss percentage, and AS number. Press
hfor help,qto quit.
Example
# Use TCP SYN probes on port 443 (useful when ICMP is blocked)
trip --protocol tcp --target-port 443 example.com
# UDP probes with custom payload size
trip --protocol udp --packet-size 512 example.com
# Generate a report after 60 seconds
trip example.com --report-cycles 60
# Output as JSON for automation
trip example.com --mode json
Related on TokRepo
- DevOps Tools -- Infrastructure and operations tools on TokRepo
- Monitoring Tools -- Network and application monitoring resources
Common pitfalls
- Trippy requires root or CAP_NET_RAW privileges for ICMP probes. Run with
sudoor grant the capability:sudo setcap cap_net_raw+ep $(which trip). - Some networks block ICMP. Use TCP or UDP probes as fallback when ICMP-based traces show incomplete paths.
- The AS number lookup requires network access to an IP-to-ASN service. In air-gapped environments, AS information will be unavailable.
Frequently Asked Questions
Yes. Trippy supports macOS, Linux, and Windows. On macOS, install via Homebrew with 'brew install trippy'. It requires root privileges for raw socket access, so run with sudo.
Both combine traceroute and ping. Trippy offers a more modern TUI with chart visualizations, supports TCP and UDP probes in addition to ICMP, and provides JSON output for automation. mtr is more widely pre-installed on Linux systems.
Yes. Trippy continuously probes each hop and displays the loss percentage in real time. You can identify exactly which network hop is dropping packets, which is critical for diagnosing ISP or routing issues.
Yes. Trippy supports both IPv4 and IPv6 network diagnostics. Use the -6 flag or provide an IPv6 address directly. The TUI displays the same metrics for both protocol versions.
Yes. Use the --mode json flag to output results in JSON format suitable for scripting and automation. You can also use --report-cycles to generate a summary report after a specified number of probe rounds.
Citations (3)
- Trippy GitHub Repository— Trippy combines traceroute and ping in a TUI
- Trippy Official Website— Trippy supports ICMP, UDP, and TCP probes
- Trippy README— TUI network diagnostics with real-time visualization
Related on TokRepo
Discussion
Related Assets
Miniflux — Minimalist Self-Hosted Feed Reader
Miniflux is an opinionated, minimalist RSS and Atom feed reader written in Go that focuses on simplicity, speed, and content readability.
Kanboard — Minimalist Kanban Project Management
Kanboard is a free and open-source Kanban project management tool focused on minimalism, productivity, and getting things done without unnecessary complexity.
Homer — Static Server Dashboard with YAML Configuration
Homer is a dead-simple static dashboard for your server services, configured entirely through a single YAML file with no database or backend required.