Internet diagnostics

Make The Internet Go

Start with DNS, then branch into speed, public IP, and regional checks when the path gets weird.

First pass

Compare DNS answers before digging into the rest of the network.

Next checks

Confirm browser-to-edge speed and the public address your traffic uses.

Primary launcher

Run a global DNS lookup

One query fans out across every configured region.

Response

Global answer view

Run a lookup to populate the map and per-region results.

Idle

Table

Per-region answers

Exact returned records for each region, including timing.

Region Status Answer Time
Choose a name, record type, and resolver to populate the global results view.

Tools

Pick the next check

Start with the live tools, then use the planned command-style checks as the roadmap fills in.

Live DNS Lookup Check a name, record type, and resolver from every configured region.
Planned Dig A focused command-style lookup for one resolver and one answer path.
Planned Global Dig A command-style regional comparison for propagation and split-horizon checks.
Live Speed Test Measure latency, download, and upload from this browser to the edge. Live My IP Confirm the public address the internet sees from this browser.

Troubleshooting paths

Follow the symptom

Plain starting points for the most common internet mysteries.

Learn

Learn while troubleshooting

Short explanations that make each result easier to interpret in the moment.

DNS

Why answers differ by region

Resolvers, caches, geolocation, and authoritative routing can all make two regions see different records.

Connectivity

When speed and DNS disagree

A fast edge test with failing DNS points to naming or resolver behavior, not raw throughput.

Identity

What your public IP reveals

VPNs, carrier NAT, office gateways, and cloud workspaces can change the address services see.

Articles

Field notes

Practical notes to turn common failures into repeatable checks.

Reading a DNS propagation split without guessing

Separating Wi-Fi pain from edge path latency

Quick checks before blaming a provider outage