Contents

Connectivity Monitor

Probe up to 20 targets on a fixed interval with TCP connect, HTTP GET or ICMP echo, graph their latency, and record outage windows.

Sidebar group: Troubleshooting · Works offline: no (probes the targets you list while running) · Needs admin rights: no

When to use it

Quick start

  1. Open Connectivity Monitor from the Troubleshooting group.
  2. In the first row, choose a probe type (TCP, HTTP or ICMP) and enter the address. For TCP, also enter the port (for example 192.0.2.10 port 443). For HTTP, enter a URL such as https://app.example.com/health.
  3. Click + Add target for more rows (up to 20).
  4. Set Every (s) and Timeout (ms), or keep the defaults.
  5. Click Start. Each target gets a card with a status dot, a latency graph and statistics.
  6. Click Stop when done. The history is kept: Resume continues into it, Clear discards it.
  7. Use Export samples (CSV) for raw data, or Export for a report with outage windows.

Inputs and options

Field What it means Default / accepted values
Probe type TCP (connect to a port), HTTP (GET a URL) or ICMP (echo request). TCP
Address TCP and ICMP: host name or IP. HTTP: an http:// or https:// URL (no scheme means https://). Empty. Rows with an empty address are skipped. ICMP is IPv4 only.
Port TCP only. Empty. 1 to 65535. Required for TCP.
× Remove the row. Disabled when only one row is left.
+ Add target Add a row. Up to 20 targets.
Every (s) Probe interval for each target. 5. 1 to 3600.
Timeout (ms) Limit for each probe. It is capped at the interval. 2000. 200 to 30000.
Start / Resume / Stop / Clear Start probing, continue into existing history, stop, or discard the history.

Targets and settings cannot be changed while running.

Reading the results

The hint under the controls shows what each probe measures and, once started, the ICMP method in use on this OS.

A status bar above the cards shows Running or Stopped, a note if the oldest samples were dropped (more than 10,000 per target), and how many probes ran past the interval.

Each target card shows:

What counts as up:

Probe Up when Time measured
TCP The TCP connection completes. A refusal is a failure, but its time is still recorded. The connect call.
HTTP The server returns a status below 400. Redirects are not followed, so a 301 or 302 counts as up. The whole request, including DNS, connect, TLS and response.
ICMP An echo reply comes back from the target. Echo round trip.

Worked example: three targets, every 5 s.

● 192.0.2.1          ICMP echo    up · echo reply     Success 100.0% of 720
● 192.0.2.10:443     TCP connect  up · connected      Success 99.3% of 720
● https://app.example.com/health  HTTP GET  down · 503   Success 97.1% of 720

Outages (https://app.example.com/health)
Start            End              Duration  Failed  First failure
14:02:10         14:03:55         1m 45s    21      503
14:20:05         ongoing          -         4       failed

ICMP to the gateway never failed and TCP had only brief misses, so the network path held while the application returned 503. That points at the service rather than the network.

What the results do and do not tell you

Online activity and privacy

When you click Start or Resume, each target is probed once per interval until you click Stop:

Host names are resolved through the system resolver for each probe. Nothing is sent before you click Start, and probing stops when you click Stop. Samples are held in memory only; nothing is written to disk unless you export.

Export and projects

Platform notes

ICMP uses the same unprivileged probe as Visual Traceroute, and the hint shows which:

Troubleshooting

"Add at least one target." Every row's address is empty.

"...: TCP needs a port". Enter a port for each TCP row.

"...: ICMP monitoring supports IPv4 only". Use an IPv4 address or a name with an A record, or switch that target to TCP.

URL errors such as "unsupported scheme ..." or "not a valid host: ...". An HTTP row's URL is not valid. See HTTP Troubleshooter for the URL rules.

"at most 20 targets". Remove some rows.

Status DNS failed. The name did not resolve at probe time. Check it with Dig.

Status cannot probe. The OS refused the ICMP socket. On Linux, check net.ipv4.ping_group_range; endpoint security software can also block it.

HTTP target always failed with a certificate error. Validation uses the bundled public root store, so an internal CA is not trusted. Probe the port with TCP instead, or check it in TLS Inspector.

"N probes ran past the interval". Probes take longer than the interval (often DNS or a slow HTTP endpoint). Increase Every (s) or lower Timeout (ms).

"export larger than 50 MB". Clear old history, or export in smaller runs.