Latency / Ping (HTTP reachability)
Client‑only
No ICMP
Cache-busted
Note: Browsers cannot send ICMP pings. This measures HTTP(S) reachability time (TCP+TLS+TTFB) against publicly reachable regional service endpoints.
Results
idle
| Region | Host | Min | Avg | Max | Jitter | Samples |
|---|
DNS over HTTPS
Client‑only
DoH
| Type | Data | TTL | Latency |
|---|
Your IP & Network
Client‑only
Public IP
—
WebRTC Connectivity (STUN)
Shows candidate types your browser can produce via STUN (host/srflx/relay) using stun.l.google.com:19302.
DNS Propagation (multi‑resolver)
DoH
Client-only
| Resolver | Answer | TTL | RTT | Status |
|---|
Clock Skew (approx)
Client-only
Compares your local clock to worldtimeapi.org (corrected by ½ RTT).
HTTP Object Throughput (CORS required)
Client-only
| # | Bytes | Time | Throughput |
|---|
About
This is an initial iteration focused on endpoint‑accurate measurements. The latency test uses browser‑safe techniques (Fetch no‑CORS, cache‑busted; Image fallback) against public, per‑region service hostnames.
- ICMP is not available to browsers; figures generally correlate with TCP+TLS+TTFB.
- Some providers (notably Azure) lack consistent region‑hostnames discoverable without credentials; support is planned via lightweight probes or optional serverless helpers.
- No backend is required. Optional advanced tools (e.g., traceroute via proxy, authenticated API checks) can be added without breaking the client.
Build time: