orf/gping

Ping, but with a graph

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 4 minutes ago
Added to GitGenius on September 4th, 2026
Created on October 17th, 2015
Open Issues & Pull Requests: 38 (+0)
GitHub issues: Enabled
Number of forks: 365
Total Stargazers: 12,672 (+0)
Total Subscribers: 81 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 59.6 days
Mean response time: 148.1 days
90th percentile: 357.7 days
Tracked items: 25

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 18
New in 7 days: 1
Closed in 7 days: 3
Avg open age: 664 days
Stale 30+ days: 16
Stale 90+ days: 15

Recent activity

Opened in 7 days: 1
Closed in 7 days: 1
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • enhancement (6)
  • bug (5)
  • Moreinfo (1)

Detailed Description

gping is a command-line network monitoring tool that visualizes ping latency as a real-time graph.

The tool solves the problem of understanding network latency patterns at a glance rather than reading raw ping output. Instead of displaying individual ping responses line by line, gping plots response times on a continuously updating graph, making it easy to spot trends, spikes, and degradation over time. It works by sending ping requests to specified hosts and rendering the results in a terminal-based graph with customizable colors.

gping suits developers and operators who need quick visual feedback on network health during troubleshooting or monitoring. It works well for comparing latency across multiple hosts simultaneously and for tracking command execution times via the --cmd flag, which graphs how long arbitrary commands take to run rather than just network latency. The tool runs on Windows, macOS, and Linux. The README does not compare gping to alternative tools, so no comparative positioning is possible.

The project maintains active cross-platform support with builds available for multiple Linux distributions, macOS package managers, Windows installers, and FreeBSD. Development includes responsiveness to packaging requests across diverse ecosystems, as evidenced by availability through Homebrew, Scoop, Chocolatey, Fedora COPR, Arch, Alpine, Debian, and other package managers. The codebase is written in Rust and requires a reasonably recent compiler version, indicating ongoing maintenance of dependencies and build tooling.