--- title: "Is my site down? Free website down checker | Logdash" description: "Check if your site is down for everyone or just you. Status code and response time from outside your network in seconds, no signup." url: https://logdash.io/tools/is-my-site-down --- # Is my site down Enter your URL and Logdash requests it from its own servers, outside your network, and shows the status code and response time within a few seconds, so you know whether the site is down for everyone or just for you. The check is one GET request to the address you typed, sent from Logdash and not from your browser. It follows up to 5 redirects and gives up after 10 seconds. Any final status from 200 to 399 counts as up. Anything else, or no answer at all, counts as down. The first result lands about a second after you press enter, and no account is needed to see it. ## Is my website down or just me If Logdash gets a 200 and your browser gets an error, the site is up and the problem sits between you and the server. The usual suspects, in the order worth checking: a stale DNS cache after a record change, a VPN or office firewall, your own IP blocked by a WAF or rate limit rule you set up months ago, and your ISP. If Logdash gets the same error you do, it is not just you, and every visitor is seeing it too. ## What the result means - 200 to 399: up. The server answered with a page or a redirect that ended in one. - 401 or 403: the server is fine and something in front of it refused the request. Often a WAF, basic auth on a staging domain, or a bot rule. - 404: the server is up and the path is not. A deploy that dropped a route looks exactly like this. - 500: the app is running and crashing on this request. Your error logs have the stack trace. - 502, 503 or 504: the proxy is up and the app behind it is not, or it is too slow to answer. - Not answering: the name does not resolve, the connection was refused, or nothing came back within 10 seconds. ## Check it from your terminal ```bash host="yourapp.com" # 1. Does the name resolve? Ask a public resolver, not your router. dig +short "$host" @1.1.1.1 # 2. Does the site answer? Same rules as the Logdash check. curl -sS -o /dev/null -L --max-redirs 5 -m 10 \ -w '%{http_code} in %{time_total}s\n' "https://$host" ``` Empty output from dig means DNS, not the server. A 000 from curl means no HTTP answer at all, and curl prints the reason above it: could not resolve host, connection refused, or a timeout. Run the same two lines from your laptop and from a server somewhere else. Different answers mean the problem is the network path, not the site. ## Website down checker online vs a monitor A one-off checker answers for one moment. If the site was down from 03:12 to 03:20 and you check at 09:00, every checker on the internet says up, and you never learn about the eight minutes your users saw. That is why this one does not stop after the first request. It keeps checking every 5 minutes for 24 hours, and if you claim the dashboard with a free account it keeps going after that. ### Logdash vs Down For Everyone Or Just Me | Feature | Logdash | Down For Everyone Or Just Me | | ------------------------------- | ------------------------------------------------- | ------------------------------------------------- | | Check from outside your network | Yes, one GET from Logdash | Yes | | Reports from other people | None, it only checks | User reports and outage history for popular sites | | Keeps checking after you leave | Every 5 minutes for 24 hours, longer once claimed | One check per visit | | Tells you when it goes down | Telegram or webhook alert | No alerts | ### When Down For Everyone Or Just Me is the better pick - The site is not yours. For Gmail, Discord or your bank, hundreds of user reports tell you more than one request from one server, and Logdash collects none. - You want a yes or no and nothing else. No dashboard, no account, no follow-up checks. ## Hear about the next one first 1. **Claim the check** Sign in with a free account and the dashboard you just watched becomes yours. Five services on the free plan, one HTTP monitor each. 2. **Pick the interval** Every 5 minutes on the free plan, every minute on Builder, every 15 seconds on Pro. Each check stores the status code and response time. 3. **Connect Telegram and test it** Add a Telegram channel, attach it to the monitor, then point the monitor at a path that returns 404\. On the next check a Telegram alert arrives saying the site is down, with the status code and the start of the response body. ### Is my website down or just me? Run the check above. It requests your URL from Logdash, outside your network. If it gets a 200 and you get an error, the site is up and the problem is your DNS cache, VPN, firewall or ISP. If it gets the same error, everyone sees it. ### Is there a free website down checker online? Yes, this one. No signup for the check. It shows the status code and response time, then keeps checking every 5 minutes for 24 hours. Claim it with a free account to keep monitoring and get Telegram alerts. ### How does a website down checker work? It sends an HTTP request to your URL from its own server and reads the answer. Logdash sends a GET, follows up to 5 redirects, waits up to 10 seconds, and calls any final status from 200 to 399 up. ### Should I post "is my site down" on Reddit? For your own small site, no. Nobody on Reddit can reach it any better than a checker can, and the answer arrives hours late. Reddit threads help for big services with many users. For your site, check it here and read the status code. ## Keep reading [All free tools](https://logdash.io/tools): One page per tool, each with the tool itself, the command or formula behind it and a monitor that keeps checking after you leave. [HTTP status checker](https://logdash.io/tools/http-status-checker): Enter a URL and Logdash sends a GET request from its servers, follows up to 5 redirects and shows the final HTTP status code with the time the whole request took. [Website response time checker](https://logdash.io/tools/response-time-checker): Enter a URL and Logdash times a full GET request from its servers, from DNS lookup to the last byte, then repeats it every 5 minutes so you see a trend instead of one lucky number. [Ping monitor online](https://logdash.io/tools/ping-monitor-online): Logdash does not send ICMP ping; it requests your URL over HTTP every 5 minutes for free, which answers what ping cannot: whether the site serves pages, not just whether the machine is switched on. [Uptime monitoring](https://logdash.io/features/monitoring): HTTP checks as often as every 15 seconds. When one fails, Telegram tells you before your users do.