Find the problem
Is the website down, or is it just me?
One site will not load. Before restarting anything, find out whose problem it is - it takes about a minute.
1. Ping the site by name
Type the site's address (like example.com) into Ping and start.
- "Could not resolve host": the name lookup itself failed. Open DNS Lookup and query the same name against Cloudflare or Google as well as the system resolver. If no resolver knows the name, the site's domain is the problem - that is their side. If only your system resolver fails, your DNS is the problem (see Wi-Fi connected but no internet, step 4).
- Replies come back: the site's machine is alive and reachable from your phone. If the page still fails, the website software on that machine is misbehaving - annoying, but firmly their side, not your network.
- Only timeouts: not proof yet. Many sites simply refuse to answer ping. Continue.
2. The cross-check
Ping two things you trust: your router (quick target) and 8.8.8.8 - one after another, or side by side at once if you have Multi Ping.
- Both reply while the site stays silent: your connection is fine. The silence is on the site's side - either down for everyone, or ignoring ping. One more tool settles even that: open TLS Inspector and enter the site's name. If the certificate loads, the site is up and merely ignores ping; if the connection fails entirely, it really is down for everyone.
- Everything times out: the problem is yours, not the site's (see Wi-Fi connected but no internet).
What you now know
One of three verdicts: the name is broken (their domain or your DNS - and you know which), the site is down for everyone (nothing to fix on your side; come back later), or your own connection is the problem (the other page walks you through it). No status-checking website needed - your phone asked the internet directly.
Every check on this page runs free in Radien - and Multi Ping does the cross-check in one screen.
