← Directory

Smokeping

Smokeping is an open-source network latency and availability monitor that pings a configured list of hosts to continuously graph response times and packet loss.

  • Home Automation
  • Monitoring & Logging
  • Network Services
  • Tools & Utilities
Smokeping is an open-source network latency and availability monitor that pings a configured list of hosts to continuously graph response times and packet loss.

Platform availability

Available on 3 of 9 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS
  • Proxmox
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

78/100 Good

Maintained
100last commit 15 days ago
Popular
53434 GitHub stars
Easy to install
553 install platforms, install notes, Docker image
Light to run
95512 MB minimum RAM, runs on ARM

Availability: platform listings confirmed today, links checked 16 days ago

GitHub stars
434
Open issues
2
Last commit
2026-09-29
Latest release
2.9.0-r0-ls185
License
GPL-3.0
Activity
declining

Checked 9 days ago - source: GitHub (linuxserver/docker-smokeping)

Resources & Compatibility

Minimum requirements: 512 MB RAM, 1 CPU core(s), 2 GB disk. ARM (e.g. Raspberry Pi) is supported.

Checked 16 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Tell SmokePing where fping lives In the Probes section of your config, set binary to the full path of fping (the ping program SmokePing uses, often /usr/bin/fping). If this path is wrong, SmokePing can’t run its ping tests and the graphs stay empty or throw errors. source
  • Add the hosts you want to graph In the Targets section, choose the FPing probe and add at least one host entry for each device you want to monitor. Without these target entries, SmokePing has nothing to measure and the dashboard won’t show any useful latency data. source
  • Make sure the startup script runs From the SmokePing directory, give the startup script execute permission (for example, chmod +x bin/smokeping) and run it. Without that, the monitor may not start at all and you’ll see a permission or command-not-found error. source

Fetched 16 days ago - each note links to its source

Alternatives (4)

  • PingInfoView - PingInfoView is a small utility that allows you to easily ping multiple host names and IP addresses, and watch the result in one table.
  • PingPlotter - PingPlotter is a graphical traceroute and ping tool that visualizes network performance in a way that makes identifying the source of probl…
  • iPerf3 - Network performance testing tool.
  • mtr - mtr combines the functionality of the 'traceroute' and 'ping' programs in a single network diagnostic tool.

Checked 14 days ago - source: AlternativeTo

Common questions

What configuration is required before SmokePing shows useful latency data?

Set the full path to fping in the Probes section and add at least one host entry for each target in the Targets section. If the fping path is wrong or no targets are present, the graphs can stay empty, throw errors, or show no useful data.

Why might the SmokePing monitor fail to start?

The startup script must be executable and run from the SmokePing directory, for example by using chmod +x bin/smokeping. Without this, the monitor may not start and may show permission or command-not-found errors.

How can I run the same measurements from several network locations?

Use a master/slave deployment where a central master supplies configuration to multiple slave nodes. This lets a single target be pinged from multiple locations.

Where does SmokePing store historical latency and packet-loss data?

SmokePing uses RRDtool to maintain a long-term data store and to draw graphs from the stored measurements.

Can SmokePing monitor both domain names and IP addresses?

A Docker-based setup can monitor common web domains as well as IP addresses. One user monitored work domains and an IP address such as 1.1.1.1.

Can Smokeping alert when latency matches a configured pattern?

Yes. It has an advanced alarm system that triggers on configurable latency patterns and supports pluggable matchers.

Answers sourced from oss.oetiker.ch, oss.oetiker.ch, oss.oetiker.ch, www.reddit.com

Community

Collected 16 days ago - public community threads