LibrePing

What it does

Alert delivery

Failed alert sends are retried, and another hub can take over if the notifying hub goes offline; delivery is at-least-once and can produce duplicates during failover.checked 11 Oct 2026

Alert privacy

Alert destinations are encrypted to the hubs responsible for notifying the user, so other hub operators see ciphertext.checked 11 Oct 2026

Alerts

Alert integrations include ntfy, Discord, Slack, and raw webhooks, with alert destinations encrypted for the hubs responsible for sending notifications.checked 11 Oct 2026

Checks

It supports HTTP(S), TCP, DNS, TLS certificate, ICMP ping and traceroute checks.checked 11 Oct 2026

Check types

It supports HTTP(S), TCP, DNS, TLS certificate, ICMP ping, and traceroute checks.checked 11 Oct 2026

Dashboard

The dashboard includes a geographic map, network overview, and per-monitor uptime and latency timelines with location breakdowns and recent checks.checked 11 Oct 2026

Data integrity

Probes sign results and hubs verify signatures; operators can use an allowlist of trusted probes.checked 11 Oct 2026

Decentralized network

Hubs share check data through a peer-to-peer libp2p gossip mesh without a central server.checked 11 Oct 2026

Deployment

The maker provides Docker Compose setups for running a hub or a probe, and says both ship as Docker images.checked 11 Oct 2026

Federation

Hubs form a peer-to-peer libp2p gossip mesh that shares monitoring data without a central server.checked 11 Oct 2026

History limits

By default, hubs retain full-detail results for 7 days, hourly summaries for 90 days and daily summaries for 730 days; results are in memory only without a database.checked 11 Oct 2026

Integrity and trust

Probes sign results and hubs verify signatures; operators can use an allowlist, while the default policy accepts validly signed results and relies on corroboration.checked 11 Oct 2026

Intended users

The maker describes use cases including monitoring one's services across countries, contributing a probe, or hosting a federated hub.checked 11 Oct 2026

License

LibrePing is free software under AGPL-3.0, which requires sharing modifications when running a modified version as a network service.checked 11 Oct 2026

Location caveat

Probe locations are auto-detected from public IP by default but remain self-declared, with no cryptographic proof of geography.checked 11 Oct 2026

No signup

The dashboard creates an identity key in the browser, and users can save a recovery phrase to move their identity to another device.checked 11 Oct 2026

Probe limit

A probe defaults to a hard cap of 300 checks per minute, configurable with MAX_CHECKS_PER_MINUTE.checked 11 Oct 2026

Probe limits

A probe defaults to a cap of 300 checks per minute, and ICMP and traceroute require the NET_RAW capability.checked 11 Oct 2026

Purpose

LibrePing monitors websites and services from multiple locations and displays reachability results on a live map.checked 11 Oct 2026

Retention

By default hubs retain detailed results for 7 days, hourly summaries for 90 days, and daily summaries for 730 days; older data is dropped.checked 11 Oct 2026

Self-hosting

Users can run a hub with its own dashboard or run a probe to contribute a monitoring location; both ship as Docker images.checked 11 Oct 2026

Shared checks

When multiple users add the same target, LibrePing deduplicates it so the network monitors it once and shares the result.checked 11 Oct 2026