- Home
- Free tools
- Is it down?
Is it down right now?
Find out whether a website is down for everyone or just for you. We request it from our checker regions (2 regions are live) and show the status code and response time.
- 🇳🇱Amsterdam—…
- 🇬🇧London—…
Do not come back here tomorrowAdd this URL to Tenium and get told on Telegram or email the moment it goes down, re-checked from the other regions before you are paged. 30 monitors free.
Start freeHow the verdict is decided
The page sends one GET request to the address you typed and records the status code, the time it took, the IP the name resolved to and the days left on the TLS certificate. A response counts as success when the final status is 200 to 399, after following up to five redirects, inside a 10 second limit. If every region that answered succeeded, the verdict is "It is up". If none did, it says "It looks down" and prints the error. A mixed result is labelled "Partially reachable" instead of being forced into one of the other two.
That middle verdict is the most interesting one. When one region gets a 200 and another gets a timeout, the site itself is usually fine and something on the path is not: a CDN edge that is unhealthy, a firewall that blocks one provider's address range, or a routing problem between two networks. The tool shows Amsterdam and London as separate rows for exactly that comparison.
Status codes worth reacting to differently
A red badge is not one problem. The number tells you whose turn it is:
- 403 or 429 from a site that loads in your browser: a bot filter or rate limiter is answering the checker. The site is alive; the tool simply looks like a script to it.
- 502 Bad Gateway: a proxy or load balancer reached the server and got garbage or nothing back. Restart the application process before touching DNS.
- 503 Service Unavailable: the application is overloaded, in maintenance mode, or has no healthy backend. A Retry-After header, if present, says when to try again.
- 504 Gateway Timeout: the proxy waited and gave up. Slow database queries and exhausted worker pools are the usual cause.
- Cloudflare 521, 522, 523 and 524: origin refused the connection, did not answer in time, is unreachable, or took too long to reply. 525 and 526 mean the TLS handshake or certificate between Cloudflare and the origin is broken.
- "Too many redirects": two rules send the request back and forth, typically http to https at the CDN while the origin sends it back.
The site is up, but not for you
When every row is green and your browser still shows an error, the fault is on the near side. Work through the cheap tests first: open the page on mobile data instead of your Wi-Fi, switch off a VPN, and flush the local DNS cache (ipconfig /flushdns on Windows, sudo dscacheutil -flushcache on macOS). A hosts file entry left over from a migration will pin the name to the old server on one laptop only. A broken IPv6 route is another classic: the AAAA record exists, your connection prefers it, and the packets go nowhere while IPv4 users see nothing wrong.
If your resolver is the problem, ask a different one. Running a DNS lookup shows what a public resolver returns, and a mismatch with the IP printed in this tool's details line points straight at stale DNS.
What a single request cannot tell you
The request does not run JavaScript, carry cookies or solve challenges, so a page that is blank in a browser because of a script error still reports 200 here. Only public http and https targets are accepted; private and internal addresses are refused, which means an intranet host or localhost cannot be tested. The tool is also rate limited, so repeated rapid checks will be answered with a "try again in a minute" message.
Treat one result as a snapshot. A site that fails once and recovers 20 seconds later looks identical to a stable one when you check at the right moment, and the reverse is just as likely.
When a one-off check should become a monitor
If you are visiting this page more than once for the same site, a monitor will do the looking for you. The Free plan includes 30 monitors checked every 5 min, and Starter at $7 a month brings that to 1 min. Before an incident opens on a paid plan, all two regions must agree, which is the same comparison you are doing by eye here, done automatically; Free accounts use 1 regions. See website monitoring for the settings behind it.
Questions about this tool
How can I tell if a website is down for everyone or only for me?
Look at the rows. If every region reports a success, the site is reachable from the outside and the cause is on your side: your network, resolver, VPN, a hosts file entry or a browser extension. If every region fails with the same error, the site is down for everyone. Mixed rows point at a CDN or routing problem that affects some networks only.
Why does the tool show 403 when the site opens fine in my browser?
Because the request comes from a data centre and carries no browser fingerprint. Cloudflare, Akamai and similar services often serve a challenge or a block page to such traffic. The site is up; the result only tells you that bots are filtered. A monitor can send a secret header that your firewall recognises, which is covered on the HTTP headers page.
How many regions does the check use?
It runs from the regions that are live today: Amsterdam and London. If the check service answers from only one of them, you are looking at one vantage point and not at a confirmed outage. Tenium's own monitoring is the place where a failure is verified from the other regions before anyone is alerted.
Can I check a page behind a login or a local address?
No. The request is anonymous, public and made without cookies, and addresses in private ranges such as 10.x.x.x or 192.168.x.x are rejected. For login-protected pages use a monitor with basic auth or a custom header instead.
Is there a limit to how often I can use it?
Yes, a modest per-visitor and global rate limit applies so the tool stays free and cannot be used to hammer someone's server. If you hit it, wait a minute. Continuous checking is what a monitor is for.