Network Diagnostics

# Overview

The Diagnostics view provides five network diagnostic tools accessible via tabs: Ping, Trace, iPerf, DNS, and Port. These tools run natively on your machine; no external software required.

# Ping

Test latency and packet loss to any IP or hostname. It measures from your device and through the Starlink router at the same time, then compares them side by side.

# Running a Ping

1. Enter a target address (e.g. 8.8.8.8)
2. Select the number of packets (10, 25, 50, or 100)
3. Click Run Ping

Your device pings the target over the local network while the router pings the same target directly through its own API (up to 10 samples). Running both at once is what makes the comparison possible.

# Results

Each run produces a single comparison card.

Verdict: a plain-English summary of what the two paths mean together:

• Both paths healthy: the Starlink link and your local network both look good to this target.
• Local network issue likely: the router’s path is clean, but your device is seeing loss or much higher latency. The fault sits between your device and the router: Wi-Fi coverage, interference, or local network equipment.
• Upstream link issue likely: both paths are degraded, which points at the dish or the Starlink link rather than your local network.
• Results are mixed: inconclusive; re-run with more packets for a clearer comparison.
• Router path unavailable: only your device path is shown. The router’s API could not be reached, which is expected in bypass mode or behind a third-party router.

Comparison table: average, min/max, loss, and sample count for This device and Via Starlink router, with a Δ column showing the difference (device minus router). Latency deltas are colour-coded; loss deltas are shown in percentage points.

Because your device reaches the internet over your local network (often Wi-Fi plus a few hops) while the router pings directly, the device path is normally a little slower with no packet loss. That overhead is expected, so the verdict treats asymmetric packet loss (your device losing packets where the router does not) as the reliable sign of a local-network fault, and only flags latency when the device path is markedly slower.

Expand Raw Output to see the full device ping output and the per-sample router latencies.

# Traceroute

Trace the network path between your device and a target.

# Running a Traceroute

1. Enter a target hostname or IP
2. Click Run Traceroute

# Results

Each hop shows:

• Hop number
• IP address(es), some hops may show multiple IPs for load-balanced paths
• Round-trip times (typically three samples per hop)
• Asterisks (*) for hops that did not respond

Traceroute uses the native OS command (traceroute on macOS/Linux, tracert on Windows).

# iPerf

Run bandwidth tests against public iPerf3 servers for an independent speed measurement (separate from the Starlink router’s built-in speed test).

# Running a Test

1. Select a server from the dropdown (e.g. Hurricane Electric US, Bouygues FR)
2. Set the port (default: 5201)
3. Choose duration: 10s, 30s, 1m, 5m, 10m, or unlimited
4. Choose direction: Down, Up, or Both
5. Click Start (or Cancel to stop a running test)

# Results

Animated gauges show real-time download and upload speeds with:

• Current throughput
• Maximum achieved
• Progress bar and percentage

Recent test results are listed below the gauges. Click Clear to remove history.

# Settings

Click the gear icon to configure iPerf options (server list, default port).

# DNS

Query DNS records for any hostname.

# Running a Lookup

1. Enter a hostname (e.g. cloudflare.com)
2. Select the record type: A, AAAA, MX, TXT, CNAME, or NS
3. Optionally change the DNS server (defaults to System Default)
4. Click Run DNS Lookup

# Results

Results show:

• Query time in milliseconds
• Number of records returned
• Each record value (e.g. IP addresses for A records)
• Raw output (expandable)

# Port

Test whether a TCP port is open on a remote host.

# Running a Check

1. Enter a hostname (e.g. cloudflare.com)
2. Enter a port number or select from Common Ports (HTTP 80, HTTPS 443, SSH 22, etc.)
3. Click Check Port

# Results

Results show:

• Whether the port is open or closed
• Connect time in milliseconds

# Clearing Results

Each tool has a Clear All button to remove all results from the current session.