Free tool · HTTP
Is It Down?
Check whether a website is up right now, from outside your network.
Down for everyone, or just you?
You can't load a page, and the first question is always the same: is the site broken, or is it something on my end? Your browser won't tell you. It shows the same spinning wheel whether the problem is a dead origin server, a stale DNS cache on your machine, your ISP's routing, a corporate firewall quietly blocking the domain. This tool removes the guesswork. It checks the URL from our server and reports exactly what comes back. If we get a 200 and you don't, the problem lives between you and the site, not at the site itself.
What the status code and response time tell you together
A status code alone doesn't give you the full picture. A 200 with a 6-second response time means the site is technically alive but functionally broken for most visitors. Got a 403? That's usually Cloudflare or a WAF blocking the request (the server is up, just not letting everyone in). With a 503, the backend is overloaded. It might recover on its own in minutes. No status code at all? DNS can't resolve, or the server is completely unreachable. If you see a redirect, the redirect chain checker shows every hop. For a deeper look at what the server returns, try the HTTP status checker or the response time tester.
One check tells you right now. Monitoring tells you every time
You're here because something already feels wrong. That's the problem with manual checks: they only happen after a user notices. Uptime monitoring checks your sites on a schedule, every minute if you need it, and alerts through Slack, email, or SMS the moment a response changes. Instead of refreshing a page and wondering, you get a notification before your visitors start wondering what's wrong.
Common reasons a website goes down
- Server overload. Traffic spike exceeds server capacity. Happens during product launches, flash sales, viral moments on social media. The server starts returning 503s or just stops responding.
- DNS issues. The domain's DNS records expired, got misconfigured, or the nameserver itself went down. The domain resolves to nothing. The browser shows "DNS_PROBE_FINISHED_NXDOMAIN."
- SSL certificate expired. Browsers throw up a full-page security warning. The server technically responds, but visitors can't get through to the actual content. Check your certificate if you suspect this.
- Hosting provider outage. AWS, Cloudflare, Vercel, DigitalOcean: even the large ones go down. Not much you can do except wait and communicate via your status page.
- DDoS attack. Malicious traffic floods the server faster than it can respond. Takes time to mitigate, and usually your hosting provider or a CDN like Cloudflare has to step in.
- Deployment gone wrong. A bad config push, a missing environment variable, a crashed process. Or a database migration that locked a table for ten minutes.
- Domain expired. The registrar suspended the domain. Nobody renewed it. Check your domain's expiry date to make sure auto-renewal is active.
"Down for everyone" vs. "just me" — what it means
If the site is down for everyone, the server itself is unreachable or returning errors. That's a hosting problem, a DNS propagation issue, or a straight-up application crash. Nothing on your end will fix it. The site's operator needs to act.
If it's down just for you, the problem is local. Your ISP, your DNS resolver, a firewall rule, a VPN routing traffic through the wrong region, stale browser cache. Any of those. Worth trying: flush your DNS cache (ipconfig /flushdns on Windows, sudo dscacheutil -flushcache on macOS), switch to a different browser, disable your VPN, or test on mobile data instead of Wi-Fi. If all of those fail, your ISP may be blocking the IP or routing traffic through a broken path. That's not a config fix. That's a support ticket.
What to do when your own website goes down
- Confirm it's really down. Use this tool from an external server, not your own network. Your local DNS cache might be lying to you. So might your VPN.
- Check the basics. Is the server process running? Is DNS resolving? Did the SSL certificate expire? Did someone just deploy? Start with the most recent change and work backwards.
- Check your hosting provider's status page. AWS, Cloudflare, Vercel, DigitalOcean all publish incident status. If it's their outage, you wait. Not much else to do.
- Communicate. Update your own status page, notify affected users via email or social media. Silence during downtime erodes trust faster than the outage itself. People forgive downtime; they don't forgive radio silence.
- Set up monitoring. You shouldn't find out your site is down from a customer tweet. Uptime monitoring checks every minute and alerts within 60 seconds.
Checking once vs. continuous monitoring
This tool answers "is it down right now?" Useful in the moment. But it doesn't help at 3 AM when nobody's awake to check. By the time you think to test manually, your users already know.
Uptime monitoring checks your site every 1–5 minutes, around the clock. When a check fails, it verifies from a second location to rule out false positives, then sends an alert through email, Slack, Telegram, SMS, or any of the 20+ channels you've configured. You also get response time charts, uptime percentage history, and incident logs. The kind of data you need for SLA reporting and post-mortems. Not just "is it up or down."