⌁
NETSCOPEv.1.3
NETWORK AVAILABLE
TTY 01 / NETWORK OBSERVATORY

Network monitor_

HTTP / SPEED / LATENCY / REQUEST TRACE

SERVERCloudflare Edge/ auto
PALETTE

▣root@netscope: ~/network

READY
NETSCOPE / NETWORK DIAGNOSTICSTTY: 01   UTF-8
PROCESS / HTTP MEASUREMENTREAD · WRITE · OBSERVE
root@netscope:~/network # awaiting command
TELEMETRYKEY METRICS ↙
↓ DOWNLOAD
—Mbps
▰▰▰▰▰ download speed
↑ UPLOAD
—Mbps
upload speed
↔ HTTP PING
—ms
round-trip time
≋ JITTER
—ms
latency variation
⌁ HTTP ERRORS
—%
of completed requests

01THROUGHPUT

DownloadUpload
Mbps
AWAITING MEASUREMENTS
0 samplestime since test started, s

03CONNECTION

HTTPS
Test endpointspeed.cloudflare.com
TransportHTTP / TLS
StatusReady to test
Test traffic0 B
ModeQuick

04LATENCY STABILITY

HTTP RTT
— ms
— ms
— ms

05REQUEST STATISTICS

0 / 0
0
0
0
HTTP requests, not network packets.
Timeouts: 0 · Packet loss: n/a
❯ netscope --speed --verbose
Ready. Start a test to measure your connection.00:00
About internet speed tests and network diagnostics

Internet speed test, HTTP ping and jitter

NETSCOPE measures download and upload speed with real HTTP requests to Cloudflare Edge. HTTP ping measures request-response time; jitter measures latency variation. Results depend on Wi-Fi, VPN, traffic and routing.

Check a website or IP address

Enter a hostname or public IP in Site / IP mode. The terminal shows DNS responses and four HTTPS checks. A response with a hidden HTTP status does not confirm that a website is healthy. Arbitrary websites cannot be speed-tested in the same way as a dedicated speedtest endpoint.

VPS diagnostics

In Site / IP mode, select VPS as the source. DNS, HTTPS, four ICMP probes and MTR TCP/443 run on the server. The table shows the route from the VPS to the target; use the local collector for the route from your computer. Missing ICMP replies at the destination and unanswered intermediate-hop probes are shown separately.

Traceroute and network hops

A local Python collector is available for traceroute from your computer. Import its report to view actual intermediate hops and latency. End-to-end ICMP loss is shown only when reported by the system ping command. An intermediate timeout is not equivalent to loss of user traffic.

TERMINAL SETTINGS

Measurements start only when you click Start test. The speed test uses internet data and connects to Cloudflare.

HOW IT WORKS

Real requests. Observable results.

Download and upload show the average payload transfer rate to Cloudflare Edge, including HTTP request time. A short test gives an estimate, not a guaranteed maximum for your internet plan.

HTTP ping is the median duration of empty-response requests after warm-up. It is not ICMP ping. Jitter is the mean absolute difference between consecutive latency samples.

The counters show completed HTTP requests, errors and timeouts. HTTP errors do not measure packet loss: TCP can retransmit lost packets without a visible request error. Network packet loss is not measured here.

Quick test: up to 32 MB. Extended test: up to 128 MB. Each request has an 8-second timeout. Results depend on Wi-Fi, VPN, load and the route to the endpoint. An access error may be caused by blocking or CORS, rather than a missing internet connection.

VPS diagnostics

In Site / IP mode, select VPS as the source. DNS, HTTPS, four ICMP probes and MTR TCP/443 run on the server. The table shows the route from the VPS to the target; use the local collector for the route from your computer. Missing ICMP replies at the destination and unanswered intermediate-hop probes are shown separately.

History is stored only in this browser, up to 20 completed speed tests. Demo data is synthetic and is not saved to history. Cloudflare test endpoints ↗

SUPPORT NETSCOPE

ROUTE FROM YOUR COMPUTER

Browsers do not expose traceroute or ICMP. The local collector runs system commands and saves a JSON report without uploading it to a server.

  1. Download netscope-route.py · Python 3.9+
  2. Open a terminal in the file's folder and run:python3 netscope-route.py example.comOn Windows, use py instead of python3. You can replace the hostname.
  3. Wait for netscope-route-report.json, then click Import route on this page. A run typically takes 10–100 seconds.

Linux may require the system traceroute package. The collector does not install programs or run a background service.

Full instructions ↗

The report shows responding hops, RTT and end-to-end ping results. A single traceroute cannot identify exactly where throughput drops.