ConfigsApr 15, 2026·2 min read

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.

TL;DR
Trippy fuses traceroute and ping into a single TUI tool that visualizes network hops, latency, and packet loss in real time.
§01

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.

§02

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.

§03

How to use

  1. Install Trippy:
# macOS
brew install trippy

# Linux (Debian/Ubuntu)
sudo apt install trippy

# Cargo
cargo install trippy
  1. Run a basic trace:
trip example.com
  1. The TUI displays each hop with live latency, jitter, loss percentage, and AS number. Press h for help, q to quit.
§04

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
§05

Related on TokRepo

§06

Common pitfalls

  • Trippy requires root or CAP_NET_RAW privileges for ICMP probes. Run with sudo or 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

Does Trippy work on macOS?+

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.

How does Trippy differ from mtr?+

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.

Can Trippy detect packet loss at specific hops?+

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.

Does Trippy support IPv6?+

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.

Can I export Trippy results to a file?+

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)

Discussion

Sign in to join the discussion.
No comments yet. Be the first to share your thoughts.

Related Assets