Public IP
Not checked yet- Not checked yet
Check your connection
Measure HTTPS round-trip time to this site — a real TLS connection test, not an ICMP ping.
DIAGNOSTIC CONSOLE
Connection
Not checked yet- Not checked yet
Browser Exposure
Not checked yet- Not checked yet
Usually takes a few seconds
What this measures
This test performs up to 3 sequential HTTPS requests to /api/health and reports the median round-trip time.
Each request includes:
- DNS lookup (if not cached)
- TCP connection
- TLS 1.3 handshake
- HTTP request/response
The first request is typically slower due to connection establishment. We use the median of all samples to reduce outlier impact.
Why not ping?
ICMP ping (the ping command) measures raw network latency to an IP address. It:
- Doesn't test TLS/HTTPS
- May be blocked or rate-limited by firewalls
- Doesn't reflect real application traffic
- Often goes through different network paths than HTTPS
Our HTTPS round-trip measures what your browser actually experiences when loading a website over TLS. It's higher than ping but more representative of real-world performance.
Not a speed test
This measures latency (round-trip time), not throughput (bandwidth). A speed test transfers megabytes of data to measure download/upload speed. We intentionally don't do that — it consumes bandwidth, costs infrastructure money, and isn't needed for basic connectivity verification.
Interpreting results
- Under 50 ms
- Excellent — local or nearby CDN edge
- 50–150 ms
- Good — typical for cross-region VPN
- 150–300 ms
- High — distant VPN exit or congestion
- Over 300 ms
- Very high — consider closer VPN server
- Failed / Timeout
- Connection issue — check VPN/network