Around. A scope × resolution view of the connection landscape.

Different scopes see different weather.

The connection looks one way from the browser, another from the first-mile, another from the tunnel, another from the wider net. Each scope reads its own signals; each resolution sees a different timescale. This page lays them out honestly: what's measurable, at what cadence, with what data we actually have.

Now single most-recent reading

Recent last 30 min · this visit

Day last 24 h · across visits

healthy / live elevated degraded / unreachable insufficient data

MethodWhat this is and is not

Each cell answers one question for one scope at one resolution. Where data exists at that scope×resolution, the cell shows the most-honest summary the data supports. Where it doesn't, the cell explicitly says so — no faked numbers, no "0" pretending to be data.

Now: a single live reading. Refreshes every 15 s.
Recent: in-memory readings from this browser tab since you opened the page. Sparkline shows trend.
Day: persisted in localStorage across visits. Older than 24 h is pruned. Until you've accumulated ≥4 readings on different occasions, this column says insufficient data.

Scopes are intentionally distinct. Browser sees what navigator.connection reports + this tab's own resource timing. Self is the RTT to this host (atmospheric.hyperstitious.art). First-mile is the RTT to public anycast (1.1.1.1, 8.8.8.8) — your ISP's reach. Tunnel reads the DAMM control plane fleet endpoint. Reach is favicon-load probes to 8 known hosts on different ASes/continents. Resolvers compares DoH answers between Cloudflare and Google to detect resolver divergence or DNS interference.