Ping, live from your browser.
Send a series of requests to Cloudflare, Google, AWS or your own server and watch every reply — average, minimum, maximum, jitter and loss, as they happen.
Test your own domain
Choose a target and press Start ping.
Minimum
Maximum
Jitter
Packet loss
Results reflect the full path between your device and the target: Wi-Fi, ISP, routing and the server itself.
An honest HTTP ping.
Browsers can’t send ICMP packets, so we time real HTTPS requests — which is also what your users’ apps experience.
The first request opens the connection (DNS, TCP and TLS). It’s shown separately and excluded from the statistics.
For targets that allow it (Cloudflare, AWS), we use the browser’s Resource Timing API: time from request sent to first byte received. Otherwise, the full request time.
Average absolute difference between consecutive pings — the best single indicator of call quality.
Requests with no answer within 3 seconds are counted as lost.
Type any domain to measure how far your users are from it. The request is sent without cookies or credentials.
Frequently asked questions
What is a good ping?
Below 30 ms is excellent, 30–70 ms is good for almost everything, 70–150 ms is noticeable in calls and real-time apps, and above 150 ms feels slow.
Why is this ping different from the ping command?
The ping command uses ICMP; browsers can only make HTTPS requests. An HTTP ping includes a few milliseconds of server processing, so it is usually slightly higher — but closer to what web applications experience.
What causes packet loss?
Weak Wi-Fi, congested networks, faulty cables or routers, and overloaded servers. Any loss above 1% is enough to hurt video calls.
You bring the problem. We figure out what needs to be built.
Tell us what’s happening in your operation, the product you want to create or the system that needs to evolve. Our first conversation starts with the problem — not the technology.
Talk to Kordis