Transparency
Methodology
What each tool on Pingvero actually measures, and how — in plain terms, with no step glossed over.
Written by the Pingvero team · Last updated September 11, 2026
How Speed Is Measured
Download speed is measured by transferring real data from this server to your browser and timing exactly how long the transfer takes. Upload speed is measured the same way in reverse: real data sent from your browser to this server, timed on arrival. Ping is measured separately by timing how long a small request takes to reach the server and come back. Nothing here is estimated or simulated — every number comes from data that actually moved and time that was actually measured.
What this can’t do: match a professional, laboratory-grade measurement, or isolate your ISP’s performance from your own WiFi signal, router and current network load. Running a test more than once, and at different times, gives a fuller picture than any single result.
How Ping, Latency and Jitter Are Measured
A browser cannot send a raw ICMP echo request the way the command-line ping tool can, so these tools send several small, timed HTTPS requests to this server’s pingvero/v1/ping endpoint instead, one after another, and measure the round-trip time of each. The Ping Test reports the median of those round trips, with the first excluded as connection warm-up, so one unusually slow or fast request can’t skew the result. The Latency Test keeps sampling live and reports the running average, minimum and maximum. The Jitter Test reports the variation between consecutive round trips — the same underlying measurement RFC 3550 formally defines as interarrival jitter for real-time streams (see our What Is Jitter? guide).
Because this measures HTTPS round trips rather than raw ICMP, results include some browser and web-server overhead on top of the underlying network delay — typically a small, consistent addition, not a source of large error.
How Packet Loss Is Measured
Browsers cannot send raw ICMP packets, so this tool sends a batch of small HTTPS requests to this server, one at a time, and counts how many fail or don’t complete within a short time limit. Because TCP automatically retransmits lost packets, this is an application-layer request-failure rate rather than a measurement of raw, uncorrected packet loss the way a command-line tool sees it — a high rate here still points to a genuinely degraded, unreliable connection, but the two numbers aren’t directly interchangeable.
What Is My IP, DNS Lookup, WHOIS Lookup & Port Checker
How These Lookups Work
What Is My IP reads the public IP address your request arrived from and displays it back to you — nothing is stored on our side. DNS Lookup and WHOIS Lookup run the actual query against the domain’s DNS records or its registry WHOIS data from our server and return what comes back, live. Port Checker attempts a real TCP or UDP connection from our server to the host and port you specify and reports what happened: a completed connection (open), an active refusal (closed), or no response before a timeout (filtered/inconclusive — genuinely ambiguous for UDP, since it has no handshake).
Subnet Calculator & Bandwidth Calculator
How the Calculators Work
Both calculators run entirely in your browser using standard, well-established arithmetic — IPv4 bitwise operations for subnetting, straightforward unit conversion for bandwidth and transfer time. No address, file size or speed you enter is sent to a server; the result is only ever computed locally.
Read Honestly
What These Numbers Don’t Tell You
Every result on this site is a real, timed measurement from one specific moment, one specific path and one specific test server — not a permanent verdict on your connection. A different time of day, a different device, or a different server can produce a different number even on the exact same line. None of these tools replace professional network diagnostics, and none of them guarantee a specific experience in a game, call or stream. Treat a result as a starting point for narrowing down a problem, and where it matters, run more than one type of test before drawing a conclusion.
Get started
Try the Tools
Now that you know how they work, run any of them and see where your connection stands.