The latest articles on DEV Community by Michael Volchenkov (@mwgg). https://dev.to/mwgg https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4140987%2F5b7a0a63-27a5-4fc1-a72a-b1c7ff1047b0.png https://dev.to/mwgg en Michael Volchenkov Thu, 24 Sep 2026 10:17:50 +0000 https://dev.to/mwgg/i-built-libreping-decentralized-uptime-monitoring-on-a-libp2p-mesh-odo https://dev.to/mwgg/i-built-libreping-decentralized-uptime-monitoring-on-a-libp2p-mesh-odo <h1> I built LibrePing — decentralized uptime monitoring on a libp2p mesh </h1> <p>Commercial uptime tools are great until you care about <em>who</em> sees your check targets, or you want vantage points you actually control. I wanted something closer to a community mesh than a SaaS control plane.</p> <h2> What LibrePing is </h2> <p>LibrePing is <strong>AGPL-3.0</strong>, written in <strong>Go</strong>, and uses <strong>libp2p</strong> so hubs gossip checks and results peer-to-peer. Probes run HTTP(S), TCP, DNS, TLS cert, ICMP, and traceroute checks from wherever you put them.</p> <p>Highlights:</p> <ul> <li>No central company server for the mesh</li> <li>Deduplicated checks (same URL added by many people is monitored once and shared)</li> <li>Browser key = account (no signup); recovery phrase</li> <li>Signed everything; sealed alert destinations (ntfy / Discord / Slack / webhook)</li> <li>Probe failover across hubs</li> </ul> <p><strong>Live demo (no signup):</strong> <a href="https://nl.lp.mw.gg" rel="noopener noreferrer">https://nl.lp.mw.gg</a><br><br> <strong>Repo:</strong> <a href="https://github.com/mwgg/LibrePing" rel="noopener noreferrer">https://github.com/mwgg/LibrePing</a><br> </p> <div class="highlight js-code-highlight"> <pre class="highlight shell"><code>git clone https://github.com/mwgg/LibrePing.git <span class="nb">cd </span>LibrePing docker compose up <span class="nt">-d</span> <span class="nt">--build</span> <span class="c"># open http://localhost:8081</span> </code></pre> </div> <h2> Why libp2p </h2> <p>Gossip + anti-entropy means a hub that joins late can catch up instead of only seeing new traffic. Results are sharded across hubs so the network can grow without every node storing everything.</p> <h2> What I want feedback on </h2> <p>Probe trust / abuse resistance, alert UX, and whether hub operators would actually run public entry points. Issues and PRs welcome.</p> showdev opensource go devops Michael Volchenkov Thu, 24 Sep 2026 10:08:42 +0000 https://dev.to/mwgg/i-built-libreping-decentralized-uptime-monitoring-on-a-libp2p-mesh-nk1 https://dev.to/mwgg/i-built-libreping-decentralized-uptime-monitoring-on-a-libp2p-mesh-nk1 <p>Commercial uptime tools are great until you care about <em>who</em> sees your check targets, or you want vantage points you actually control. I wanted something closer to a community mesh than a SaaS control plane.</p> <h2> What LibrePing is </h2> <p>LibrePing is <strong>AGPL-3.0</strong>, written in <strong>Go</strong>, and uses <strong>libp2p</strong> so hubs gossip checks and results peer-to-peer. Probes run HTTP(S), TCP, DNS, TLS cert, ICMP, and traceroute checks from wherever you put them.</p> <p>Highlights:</p> <ul> <li>No central company server for the mesh</li> <li>Deduplicated checks (same URL added by many people is monitored once and shared)</li> <li>Browser key = account (no signup); recovery phrase</li> <li>Signed everything; sealed alert destinations (ntfy / Discord / Slack / webhook)</li> <li>Probe failover across hubs</li> </ul> <p><strong>Live demo (no signup):</strong> <a href="https://nl.lp.mw.gg" rel="noopener noreferrer">https://nl.lp.mw.gg</a><br><br> <strong>Repo:</strong> <a href="https://github.com/mwgg/LibrePing" rel="noopener noreferrer">https://github.com/mwgg/LibrePing</a><br> </p> <div class="highlight js-code-highlight"> <pre class="highlight shell"><code>git clone https://github.com/mwgg/LibrePing.git <span class="nb">cd </span>LibrePing docker compose up <span class="nt">-d</span> <span class="nt">--build</span> <span class="c"># open http://localhost:8081</span> </code></pre> </div> <h2> Why libp2p </h2> <p>Gossip + anti-entropy means a hub that joins late can catch up instead of only seeing new traffic. Results are sharded across hubs so the network can grow without every node storing everything.</p> <h2> What I want feedback on </h2> <p>Probe trust / abuse resistance, alert UX, and whether hub operators would actually run public entry points. Issues and PRs welcome.</p> showdev go opensource devops