Robust reachability detection

Most ping tools ask one question: "did this packet come back?" ProbeScope asks a better one: "is this host actually reachable, and can I trust what I'm seeing?"

ICMP and TCP, automatically

ProbeScope tries privileged ICMP, falls back to unprivileged ICMP, then falls back to a TCP connection — automatically, per host, with no configuration needed. Running without root? ProbeScope still gets a real answer. Monitoring something that only speaks a specific port — a database, an internal API, a VPN endpoint? Pin it with host:tcp/5432 and check exactly that.

No false alarms from a single dropped packet

A single lost packet on a normal, healthy connection isn't an outage — but plenty of monitoring tools report it as one anyway. ProbeScope requires several consecutive failures (configurable, 3 by default) before it calls a host down, and several consecutive successes before it calls it back up. The result: a status you can trust, not a stream of noise you have to mentally filter.

ProbeScope terminal comparing fast and laggy hosts that stay up against reject/silent hosts that cross the failure threshold — Flaky 'maybe' hosts correctly told apart from a real reject/silent outage

Built for real networks, not lab conditions

Whether you're watching a home lab over Wi-Fi, a fleet of production servers, or a client's VPN tunnel, ProbeScope's probing adapts to what actually works on that network and keeps working even as conditions change.