Tools · What's not opening
Not opening: for everyone or for you
The same service is checked from two sides — from your browser and from our server. The difference between the answers is the diagnosis.
On the button press your browser will contact every service on the list, and our server will do the same from its side. The check doesn't start by itself: requests to third-party sites should be triggered by your decision, not by opening a page.
What you checked is not recorded. The server half of the measurement is shared by all visitors and refreshes on a timer.
Your own address
Type in a site address — we'll open it from our side and match it against your result. Regular sites on ports 80 and 443 are accepted; local-network addresses are not checked.
Why two measurements
When a page won't open there are exactly two causes: the service itself is down — or the path from you to it is closed. From inside the browser both look identical: a connection error that tells you nothing.
Only a second measurement from another point separates them. Your browser knocks on the service itself; our server does it from a different network under a different address. Answered us but not you — your stretch of the path is closed. Answered no one — the fault is on its side, and no detour helps.
What “unavailable for you” means
Not necessarily provider-level blocking. The same result comes from a filter on office Wi-Fi, parental control in the router, an antivirus inspecting traffic, a failing DNS, or the service's own regional rule.
The picture across neighbours helps tell them apart. One service out of ten failing — more likely a targeted rule or its own quirk. Several big ones down at once — the cause is shared and close to you: in the network you go out through.
Why availability “flickers”
A big service is dozens of sites around the world, and different users are routed to different ones. Hence partial availability: works for a neighbour, not for you, and the other way round an hour later.
For the same reason a rerun a couple of minutes later may answer differently. The tool isn't wrong — it records the state at measurement time. If results jump, run the check several times and read the overall picture, not a single answer.
How this differs from Downdetector
Complaint trackers count presses of “it's down for me”: the bar grows with crowd mood. Spikes happen without outages, and a quiet night-time failure with the audience asleep barely shows on the graph.
There are no other people's complaints here at all. Every run is two live requests — yours and ours — and the verdict is built on them alone. The answer describes your connection, not a national average.
Questions and answers
When the path is closed, not the service
MeerGuard White changes the route to the service and the point you're seen from. It doesn't fix services' own outages — only the road to them.