Standard ping has been a go-to network tool for decades. But reading raw text output to spot latency spikes gets old fast. The gping command changes that by showing ping results as a live bar graph in your terminal, making it much easier to see network issues at a glance. This article covers 10 practical examples of the gping command for network latency monitoring and troubleshooting.
1. Basic gping Command Usage
The simplest way to use the gping command is to ping a single host. Unlike the standard ping tool that shows raw text, gping gives you a live bar chart of response times. It updates in real time so you can see latency spikes as they happen.
gping google.comThis will show each ping result as a vertical bar. Greens are fast responses. Yellows and reds mean higher latency. You get the same ICMP data as regular ping but in a format your eyes can process much faster.
2. Pinging Multiple Hosts with the gping Command
One thing I use the gping command for regularly is comparing latency across servers. You can ping several hosts at once by listing them all on the same line. Each one gets its own colored bar in the graph.
gping google.com cloudflare.com github.comThis is useful when you want to see which DNS resolver or CDN node responds fastest. The bars stack side by side so a quick glance tells you who is winning. No more switching between terminals or scrolling through logs.
3. The gping Command with Custom Intervals
By default, gping sends one ICMP packet per second. You can change that with the -i flag. A shorter interval gives you more data points but uses more bandwidth. A longer interval reduces noise on a stable connection.
gping -i 0.5 google.comThe value is in seconds so 0.5 means two pings per second. I keep it at 1 second for most work and only lower it when I am debugging a brief intermittent issue.
4. Setting Packet Count with the gping Command
The gping command also lets you limit how many packets it sends. Pass the -c flag followed by the count. This is helpful for scripts or when you only need a quick latency sample.
gping -c 10 google.comAfter 10 packets, gping exits and shows you the final graph. Without a count flag it runs until you press Ctrl+C. For automated checks the count option is the right call.
5. Using the gping Command with DNS Resolution
Pinging an IP address skips DNS lookup entirely. But when you use a hostname, gping resolves it first. You can control this behavior with the -4 flag which forces IPv4 or the -6 flag for IPv6.
gping -4 google.comIf your network has IPv6 issues, forcing v4 can give you a cleaner signal. I have seen cases where mixed DNS results gave inconsistent latency readings. Forcing the protocol fixed it.
6. The gping Command in Dark Mode
This is a small thing but I appreciate it. The gping command has a dark mode flag (--dark) that inverts the colors so the graph works better on dark terminal themes. Most modern terminals are dark by default and the standard light graph can be hard to read.
gping --dark google.comThe change is immediate. Bars show up in bright colors on a dark background. If you use a dark theme the switch is worth making permanent by aliasing gping to gping --dark in your shell config.
7. Piping the gping Command with Other Tools
Gping outputs to standard output by default so you can pipe it into other commands. This works best with tools that take text input. For example you can tee the output to a log file while watching the graph live.
gping google.com | tee ping_log.txtYou can also clean up the output with grep or awk if you need the raw numbers for a dashboard. The text output mode uses the --plain flag which strips the ANSI colors and graph characters.
8. The gping Command for Scripting and Automation
For scripts and monitoring tools, the gping command supports a machine-readable output mode. Use the --json or --csv flags to get structured data instead of the graph. This is a lot easier to parse than scraping text output from regular ping.
gping --json -c 5 google.comThe JSON output includes timestamps, response times in milliseconds, and success flags. You can feed this into jq or a Python script for custom alerting. Check out our jq tutorial if you need help parsing JSON on the command line.
9. Comparing Latency with the gping Command
When you are choosing between hosting providers or CDN endpoints, the gping command is a fast way to compare them. Run it with two or more hosts using the gping command and watch the bars grow in real time. The taller the bar the higher the latency.
gping 1.1.1.1 8.8.8.8 9.9.9.9Cloudflare’s 1.1.1.1, Google’s 8.8.8.8, and Quad9’s 9.9.9.9 are common DNS resolvers. Running gping against them side by side tells you which one responds fastest from your location. The answer varies by region so do your own test.
10. Why the gping Command Beats Traditional Ping
Standard ping has been around since the 1980s and it works fine for basic connectivity checks. But the gping command adds a visual layer that changes how you interpret the data. A graph shows trends over time. Raw text shows individual values you have to mentally average. For any serious network troubleshooting, the gping command gives you a clearer picture faster.
For debugging intermittent packet loss or high latency, that visual trend is the difference between seeing a problem and understanding it. Pair gping with tcpdump for deeper packet analysis or socat for testing raw connections.
The tool is open source and written in Rust so it runs on Linux, macOS, and Windows. Install it with apt install gping on Debian or Ubuntu, brew install gping on macOS, or grab the binary from the GitHub releases page. The project stays actively maintained and the README has full documentation on every flag.
If you are still using raw ping for network troubleshooting, give gping a shot. One look at that live bar graph and you will see why a visual tool beats scrolling through text output.