Reachability checks that run from where your users are.
NetUtils runs scheduled ICMP, TCP and DNS probes from a small set of regional collectors and keeps the raw results for 30 days, so you can answer “was it us, or was it the path?” after the incident rather than during it.
Reachability
TCP connect and TLS handshake timings per collector, sampled every 60 seconds.
Resolution
A, AAAA and CNAME answers recorded per resolver, with the TTL actually returned.
Path
Hop-by-hop latency captured on change, not on a fixed schedule.
Collectors
| Region | Location | IPv6 | Status |
|---|---|---|---|
| eu-west | Gravelines, FR | yes | operational |
| eu-central | Strasbourg, FR | yes | operational |
| eu-north | Helsinki, FI | no | operational |
Reading a result
Every probe is stored with the collector that ran it. Results are read back as newline-delimited JSON:
$ netutils probe --target example.org --port 443 --collector eu-west
{"ts":"2026-08-07T14:02:11Z","collector":"eu-west","target":"example.org",
"tcp_connect_ms":11.4,"tls_handshake_ms":24.9,"ttl":57,"ok":true}
Retention
Raw samples are kept for 30 days and rolled into 5-minute aggregates after that. Aggregates are kept for a year. Nothing is shared between accounts, and probe targets are never used to seed anyone else’s checks.