03 / LATENCYREADY
Connection quality
Eight small requests. A live view of response time.
- Status
- Not tested
← My public IP
IPNixa / NETWORK TOOLS
Ping & Jitter Test: Check Your Connection Latency
Measure eight small HTTP requests to IPNixa after warm-up. Compare median latency and jitter before and after a VPN or network change, with explanations for cached DNS and reused connections.
NIXA / CONNECTION REPORT
Inspect your connection.
Run a fresh check from this browser.
Ready when you are. Results remain on this page.
Results describe requests to IPNixa from this browser. No scan history is stored by this tool.
Understand your ping and jitter readings
Read median, range and adjacent-sample variation together. This small HTTP test helps compare browser response times without a large download.
Why is DNS or connection setup missing?
Cached DNS and a reused connection can skip new setup. The result separates reused phases from unavailable values so neither is mistaken for a zero-delay network.
Explain 0 ms and connection reuse Run a fresh latency checkDid my VPN increase latency?
Repeat with the same device and similar traffic conditions before and after switching. Compare several runs; this measures the path to this endpoint, not every destination.
Make a fair network comparison Compare my VPN addressesHow to use this check
- Pause downloads and streams, then select Run check for eight samples after one warm-up request.
- Read median, range and jitter together. One slow sample can reflect scheduling or temporary congestion.
- Repeat under similar conditions to compare Wi-Fi, mobile data or VPN servers. This is not a download-speed or game-server ping test.
What this check measures
The test warms up the connection, then measures eight sequential HTTP requests. Median is the middle response time; jitter is the mean absolute difference between adjacent samples. These include browser scheduling, HTTP and server processing. They are not ICMP ping, packet loss, bandwidth or latency to a game server. Pause downloads and compare several runs under similar conditions.
Why does my result differ from a game ping?
A game uses a different server, route and protocol. This result measures small HTTP requests to the IPNixa endpoint, not your game server.