Internet Connection Test

Confirms you are online: your browser calls our server, which opens a TCP connection to 1.1.1.1 and times it. A reachability check, not a bandwidth speed test.

Ready to test

Click the button below to start.

Latency (Ping)
-- ms
Status
--

What this test measures

Pressing Start Test does two things. First, your browser sends a request to our server at tools.edeskcloud.com. Second, our server opens a TCP connection to 1.1.1.1, Cloudflare's public DNS resolver, on port 53, waits up to 5 seconds, and reports how many milliseconds that connection took. If both steps succeed the page shows "You are Online" and that number.

So "Online" means your device has a working path to our server, and our server has a working path to Cloudflare. The figure in the Latency box is the time our server needed to reach 1.1.1.1, measured on our side. It is not your latency, and it looks much the same from every visitor's browser; in our own checks it is typically a few milliseconds, because both ends are well-connected data centres. The time your own request took to reach us and come back is not displayed.

What it does not measure

This is not a speed test. It does not download or upload any data, so it cannot report bandwidth in megabits per second, and it does not measure packet loss or jitter. Bandwidth is how much data your connection can move per second; latency is how long one small message takes to make a round trip. Cloudflare's explanation of latency covers the difference and why distance matters so much. A connection can pass this test and still stream video badly, because the test never pushes enough data to notice.

It also does not test DNS. The connection to 1.1.1.1 is made by IP address, so it works even when name resolution is broken, and this page would not have loaded in the first place if your resolver were completely down. If websites fail by name while this test passes, run the domain through the DNS Checker or try a different resolver on your device.

Reading the result

You are Online

What it means: your browser reached our server and our server reached Cloudflare. Your connection is up at least as far as the public internet.

If things still feel slow: the cause is bandwidth, Wi-Fi quality or the particular service you are using, none of which this test examines.

Connection Failed, although this page loaded

What it means: the request reached our server but the server could not open a connection to 1.1.1.1 within 5 seconds, or the reply was lost on the way back to you. The first case is a problem on our side, not yours.

What to do: press Test Again. If your other sites and apps work, your connection is fine.

The page itself will not load or reload

What it means: your device cannot reach our server at all, which usually means it cannot reach anything. The test cannot run in this state.

What to do: work through the checks below.

When you are offline: what to check, in order

Once you are back online, the Ping Tool checks whether a specific host and port answer from our server, and What Is My IP shows the public address your connection came back with, which may have changed after a router restart.

Frequently asked questions

Is this a speed test?

No. It confirms that you can reach the internet and reports how quickly our server reached Cloudflare. To measure download and upload speed you need a test that transfers data between your device and a nearby server; this site does not offer one.

Why is the latency figure so low?

Because it is measured between our server and Cloudflare's network, not from your device. Two data centres joined by fibre answer each other in a few milliseconds regardless of how your home connection is doing.

How do I measure my own latency?

From a terminal, run ping 1.1.1.1. It sends ICMP echo requests from your device and prints the round-trip time of each reply. Repeat it at different times of day; the variation tells you more than any single figure.

Why do some sites load slowly when the test says I am online?

Being online is the minimum. Slow pages come from limited bandwidth shared with other devices, a weak Wi-Fi signal, a distant or overloaded website, or a browser extension. Loading the same page on another device or over mobile data narrows down which of those it is.