Is the site down
A site won't open, and it is impossible to tell whether it is down for everyone or blocked only on your network. Enter the address: we ask the site from our server abroad while your browser tries to reach it on its own. The difference between those two answers is the diagnosis.
Enter a website address — we check it from both sides at once: from our server abroad and from your own browser.
- Site's server address
- —
- Site's reply
- —
- Response time
- —
- Server
- —
Availability over 24 hours
up down from visitor reports no data
Recent outages
The graph is built from anonymous measurements: host, up or down, 10-minute slot. No addresses and no visitor history are stored. Status of all services →
The check only looks at availability: whether the site's server answers. What the page shows, or whether logging in works, it cannot know.
Common checks — one click
These are the addresses people check most often. Click any of them to run the check.
Services people ask about mostGlobal platforms — the usual suspects
Why two sides are better than one
The usual outage detectors show one thing: whether other people are complaining right now. Useful, but not an answer to your question. What you need to know is whether the site works at all — and whether your network gets to it. Those are two different questions, and different machines answer them.
- Our server sits in a datacentre abroad, on a different provider and a different route. If the site answers it, the site's server is alive;
- Your browser goes to the same site through your own operator. If it fails, the problem is the road, not the site;
- The difference between the two is the diagnosis. All four combinations are below.
How to read the result
- Answers both of us. The site is up and your network reaches it. If the page is still blank, the cause is on your device: extensions, cache, router DNS, antivirus.
- Answers us, not you. The common case with global services: the server is alive, but the request from your network never arrives. That is what a restriction on the way looks like, and a different route fixes it.
- Answers you, not us. The mirror image, familiar to anyone who has moved abroad: national sites and banks often close their doors to foreign addresses. Nothing is broken on your side.
- Answers nobody. The site itself is down. Neither a VPN nor a router reboot helps — wait a few minutes and check again.
What the status codes mean
- 200 — the page was served normally;
- 301 and 302 — a redirect to another address, which is a perfectly normal answer;
- 403 — the server is alive but won't show the page to an automated request. In a real browser it usually opens;
- 404 — the server works, that particular page does not exist;
- 500, 502, 503 — a failure on the site's side: the server answers but cannot produce the page.
Any code is good news — it means the connection reached the server. The bad sign is not a code but its absence: a timeout, a dropped connection or a certificate error.
The 24-hour graph: two series, three sources
A single check answers “right now”; the graph answers “since when”. It has two series, measured in different places:
- Worldwide — our server in a datacentre abroad sweeps every watched service every 10 minutes;
- From Russia — the same sweep from our node inside the country: from Germany it is physically impossible to see what a Russian subscriber sees;
- Visitor reports fill the Russian series where the node is silent. Your browser already checks the site for the second card, and that result feeds a shared anonymous counter. Those slots are drawn lighter — one particular network, not our own measurement.
What this tool does not do
Honest limits. It does not read the page — only the fact that the server answered, so it cannot tell you whether logging in or paying works. It is not an official verdict on blocking: restrictions differ between operators and regions, and no external service sees the whole picture. And it is not a scanner: checks per minute are limited, and names that resolve inside private networks are never requested at all.
If it answers us but not you
This is the case a VPN exists for: the site's server works, but the request from your network never gets there. A protected connection changes the route — the data travels through an encrypted channel and the site opens as usual. You can verify it right here: switch the VPN on, reload this page and run the check again — the second card should flip to “Answers”.
And if nothing changes after connecting, see “VPN is on but nothing works” — it covers the cases where the connection drops or slows down.
Site alive, but out of your reach?
7 days free, no card needed. With BrodVPN the request travels through a protected channel and sites open like they used to.
Frequently asked questions
How do I check whether a website is down?
Type its address in the field above and press Check. The check runs from both sides at once: our server abroad requests the site from its side while your browser tries to reach it from yours. A couple of seconds later you see both answers and the verdict.
Is the site down for everyone or only for me?
That is exactly what the check answers. If the site answers neither us nor you, it is down on its own and waiting is the only fix. If it answers us but not you, the problem is on the way — a restriction at your provider or at country level. If it answers you but not us, the site itself closes its doors to foreign addresses, and there is nothing to fix on your side.
What does a reply of 403 or 503 mean?
That is the server's status code. 200 means the page was served, 301 and 302 are redirects, 403 means the server answered but refused to show the page to an automated request, and 5xx means a failure on the site's side. Any of these already proves the server is alive and reachable.
Why doesn't the check show what is on the page?
It only looks at availability: whether the server answers and how fast. We do not read or store page content — for an “up or down” diagnosis it is not needed.
The check says the site is up, but it still won't load for me
Then your network did reach it, and the cause is closer to you: browser extensions, a stale cache, the DNS in your router, antivirus software, or a failure after the connection — a login that won't go through, for example. Start with a private window and a different browser.
Do you keep a record of the sites I check?
We keep no history against you: the request is not tied to you or to any account, and the result lives on screen for as long as the page is open. The only thing stored is anonymous counters for the graph — host, up or down, a 10-minute slot and a country (derived from the address prefix; the address itself is not kept). Those counters cannot be traced back to a person.
Where does the availability graph get its data?
From three sources. The worldwide series is measured by our server abroad every 10 minutes. The Russian series comes from our node inside Russia on the same cadence, plus anonymous reports from visitors' browsers there — your browser already checks the site for the second card, and that result feeds a shared counter. Slots covered only by visitor reports are drawn lighter.