Is my internet down?
This test runs in your browser as soon as the page opens. It checks whether you can reach the internet, whether DNS works, how steady the connection is and whether your clock is right, then says what to fix.
Testing your connection
Your browser is reaching our server and a few well-known sites. This takes a few seconds.
Our server
Round trips to EU (Falkenstein)
Testing
Internet by IP address
1.1.1.1 and 8.8.8.8, public DNS servers. No name lookup needed.
Testing
Websites by name
Each name has to be looked up in DNS first.
Testing
Device clock
Compared with our server's clock.
Testing
Well-known sites
| Site | Your browser | Our server |
|---|---|---|
| Testing | Up | |
| Cloudflare | Testing | Up |
| Wikipedia | Testing | Up |
| Microsoft | Testing | Up |
| Amazon | Testing | Up |
Your browser contacts our server, Cloudflare's 1.1.1.1 and Google's 8.8.8.8 and the sites above directly; each sees the request like any visit. The results stay on your device.
One site still won't load?
Connection questions
- Is it my internet or the website?
- If this test passes but one site still won't load, your connection is fine and the problem is that site, or something between you and it. Check the site with our down checker: it tests it from our server and shows what other visitors report. If the test fails for every site, the problem is your connection.
- Sites fail by name but work by IP address. What does that mean?
- DNS has stopped working. DNS turns names like wikipedia.org into the addresses computers connect to, and without it nothing loads even though the connection itself is fine. Restart your router first. If that doesn't help, change the DNS server in your network settings to a public one such as 1.1.1.1 (Cloudflare) or 8.8.8.8 (Google).
- What is a good latency?
- For browsing, anything under about 100 ms feels instant. Calls are more demanding: past roughly 150 ms each way, or 300 ms round trip, people start talking over each other. We measure the round trip to our server in EU (Falkenstein), so the further you are from it, the higher the number, even on a perfect connection.
- What is jitter, and when is a round trip lost?
- Jitter is how much each round trip differs from the one before. Under 30 ms is fine for calls; more makes audio and video choppy, usually because of busy Wi-Fi or other devices downloading. A round trip counts as lost when no answer arrives within 3 seconds, a sign of a connection that keeps dropping out.
- Why does the test check my device clock?
- Secure connections and sign-ins depend on the time. A clock that is off by more than about 30 seconds can make codes from authenticator apps fail, and one that is off by hours or days can make browsers reject certificates with errors like NET::ERR_CERT_DATE_INVALID. If the difference is a whole number of hours, the time zone is usually set wrong. Turning on automatic date and time fixes both.
- Why is there no speed test?
- Because download speed is rarely why a site won't load, and measuring it properly means moving tens of megabytes. This test checks what usually breaks instead: reaching the internet at all, DNS, a steady connection and the clock. If pages load but slowly, your provider's own speed test is the best next step.
- Do you store my results?
- No. The test runs in your browser and the results stay there; we don't receive them. Your browser contacts our server, two public DNS servers and the well-known sites listed, and each sees the request like any visit. The round trips to our server aren't logged.