# 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. It is open source and self-hosted, installable on Proxmox, ZimaOS, Unraid and Docker Hub.

Canonical page: https://ourlocalhost.com/app/357/smokeping

## Description

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, ZimaOS, Proxmox.

## Health score

78/100 (Good), based on 4 of 4 factors.
- Maintained: 100 (last commit 23 days ago)
- Popular: 53 (434 GitHub stars)
- Easy to install: 55 (3 install platforms, install notes, Docker image)
- Light to run: 95 (512 MB minimum RAM, runs on ARM)

## Links

- Proxmox: https://community-scripts.github.io/ProxmoxVE/scripts?id=smokeping
- ZimaOS: https://github.com/IceWhaleTech/CasaOS-AppStore/tree/main/Apps/Smokeping
- Unraid: https://ca.unraid.net/apps/smokeping-15lxh1x0670f6p?q=smokeping
- Official website: https://oss.oetiker.ch/smokeping/
- GitHub: https://github.com/linuxserver/docker-smokeping
- Docker Hub: https://hub.docker.com/r/linuxserver/smokeping
- Documentation: https://oss.oetiker.ch/smokeping/doc/index.en.html

## 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.

## Alternatives

- 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: Iperf3 is a lightweight container that runs the iperf3 bandwidth measurement tool for testing TCP, UDP, and SCTP throughput between network…
- mtr: mtr combines the functionality of the 'traceroute' and 'ping' programs in a single network diagnostic tool.

---
Source: Our Local Host (https://ourlocalhost.com/app/357/smokeping), the self-hosted and open-source app directory.