Network

Network monitors check connectivity and routing below the application layer — useful for servers, ports, resolvers and the path packets take to reach you.

Ping (ICMP)

Measures reachability with round-trip time and packet loss. The monitor view focuses on RTT and loss (not a misleading "duration"), so you see latency trends and intermittent drops at a glance.

• Presets: host unreachable, high latency, packet loss above a threshold.

TCP

Opens a TCP connection to a host and port to confirm a service is accepting connections. A connection-timing waterfall breaks the handshake into stages so you can see exactly where a slow connect comes from.

• Presets: port closed / unreachable, slow connect. Optional response match for line-based protocols.

UDP

Sends a UDP probe to a host and port and checks for an expected response — for services that don't use TCP.

DNS

Resolves a name and checks the answer.

• Custom resolver — query a specific DNS server instead of the default.
• Expected records — assert that a name returns the records you expect (e.g. a specific A/AAAA/MX/TXT value); an incident's root cause shows what differed.
• Presets: resolution failure, unexpected records, slow resolution.

Network path (MTR)

Traces the full route to your host, hop by hop, combining traceroute and ping. You get:

• a path ladder of every hop with per-hop latency and loss,
• a path-history heatmap you can click to replay the network path at any moment,
• per-prober breakdown, so a single flapping hop doesn't mislead you.

Great for diagnosing "it's slow but the server is fine" — the problem is often a hop in between.