# Network Latency Test

> Ping several well-known endpoints from your browser and compare round-trip times to work out whether a slowdown is you or them.

URL: https://uttir.com/network-latency-test
Categories: network-tools, developer-tools
Privacy: The test sends a handful of tiny anonymous requests to public endpoints and times the responses in your browser. No data about you is attached and nothing is stored.

## About

Latency is the time a request takes to travel from your device to a server and back. This test sends a short series of tiny requests to several well-known public endpoints and reports the median, minimum, and jitter for each — side by side, so you can compare.

The comparison is the diagnostic. If every endpoint is fast but one is slow, the problem is that service or its route. If every endpoint is slow, the problem is local: your Wi-Fi, your ISP, or your device.

Each endpoint is pinged six times after one warm-up request (which absorbs connection setup), and the numbers shown come from the measured round trips only.

## How to use

1. **Run the test** — Endpoints are pinged one at a time; results appear as each completes.
2. **Compare medians** — A single slow endpoint points at that service; uniformly slow numbers point at your connection.
3. **Watch jitter** — High jitter (wide wobble between pings) hurts calls and gaming more than a slightly higher median.

## Examples

### Diagnosis example

Reading a typical result table.

Output:

```
Cloudflare 12 ms, Google 18 ms, GitHub 45 ms, one endpoint 480 ms — your connection is fine; that one service or its route is the bottleneck.
```

## FAQ

### Is this the same as the ping command?

The measurement idea is the same (round-trip time), but this test uses HTTP requests instead of ICMP. That means it measures what your browser actually experiences, works from any network that allows web traffic, and needs no software install.

### Why do different endpoints show different times?

Distance and routing. A nearby edge server answers in a few milliseconds; a data centre on another continent takes 100 ms or more. Different does not mean broken — compare each against its own history.

### Why might an endpoint be unreachable?

Some networks block certain services, and some endpoints rate-limit or block unusual clients. An unreachable result tells you that path is blocked from your network, which is itself useful diagnostic information.

### What is a good latency number?

Under 30 ms to a nearby endpoint is excellent, under 100 ms is good for most uses, and video calls stay comfortable up to roughly 150 ms. Jitter under 5 ms keeps calls and games steady.

## Related tools

- [Internet Speed Test](https://uttir.com/internet-speed-test) — Measure your download speed, latency, and jitter in the browser. Download-only: nothing is uploaded and nothing is tracked.
- [API Tester (HTTP Requests)](https://uttir.com/api-tester) — Make HTTP requests from your browser: GET, POST, PUT, DELETE, with custom headers and body. Import a cURL command, see the full response (status, headers, body) with timing. Free, in browser, no signup.
- [DNS Lookup](https://uttir.com/dns-lookup) — Query DNS records (A, AAAA, MX, TXT, NS, CNAME, SOA, CAA) for any domain using Google DNS-over-HTTPS.
- [HTTP Status Code Lookup](https://uttir.com/http-status-codes) — Look up any HTTP status code from 100 to 511 with plain-language explanations, searchable and filterable by category.

---

For the full HTML page with the live tool, visit https://uttir.com/network-latency-test.
This file is the markdown rendering at https://uttir.com/network-latency-test.md. See https://uttir.com/llms.txt for a site-wide summary.