How to Check if a Website is Down (For You or Everyone)

You click a link, and nothing loads. Is the site down? Is it your internet? Is it a problem with your DNS? The fastest way to find out is to check from somewhere else — and a website uptime checker does exactly that in seconds.

This guide explains how to check if a site is down, what causes outages, and how to monitor your own website so you find out before your users do.

Is it down for just you, or for everyone?

This is the first question to answer whenever a website fails to load. There are two completely different causes:

Down for everyone (server-side issue): The web server is unreachable from anywhere on the internet. The problem is on the website owner's end — a crashed server, expired domain, overloaded hosting, or a DNS misconfiguration.

Down just for you (client-side issue): The server is running fine, but something between you and the server is broken — your internet connection, a DNS caching issue, a network filtering rule, or an ISP routing problem.

A site downtime checker resolves this immediately. It sends a request to the target website from a remote server in a different location. If the remote server can reach the site but you cannot, the issue is local to you. If the remote server also cannot reach it, the site is genuinely down.

How to check if a website is down

Method 1: Use an uptime checker tool

Open the FixTools Uptime Monitor, enter the website URL, and click Check. The tool pings the server from an external location and reports whether the site is responding.

You will see:

• Status: Up (HTTP 200) or Down
• Response time: How long the server took to respond in milliseconds
• HTTP status code: The server's response code (200 = OK, 500 = server error, 404 = not found, 503 = service unavailable)

This is the fastest and most reliable method. It takes less than five seconds and gives you a definitive answer.

Method 2: Try accessing from a different network

Switch from your home Wi-Fi to mobile data on your phone. If the site loads on mobile data but not on Wi-Fi, your internet connection or router is the problem, not the website.

Similarly, try opening the site on a different device. If it works on your phone but not your laptop, the issue is specific to that device's network settings or browser.

Method 3: Flush your DNS cache

Your computer caches DNS records (the mapping from domain names to IP addresses) to speed up browsing. Occasionally these records become outdated or corrupted, making a functioning website appear unreachable.

To flush your DNS cache:

Windows: Open Command Prompt as administrator and run:

ipconfig /flushdns

Mac: Open Terminal and run:

sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

Linux: Run:

sudo systemd-resolve --flush-caches

After flushing, try the website again.

Method 4: Check HTTP status codes

When a website is partially down (the server responds but something is wrong), the HTTP status code tells you what kind of problem it is:

Status Code	Meaning	Cause
200	OK	Site is up and responding normally
301 / 302	Redirect	Site redirects to another URL
400	Bad Request	Malformed request (unusual for normal browsing)
403	Forbidden	You don't have permission to access this page
404	Not Found	The specific page does not exist
500	Internal Server Error	Server-side code error
502	Bad Gateway	Upstream server error (common with proxies/CDNs)
503	Service Unavailable	Server is overloaded or in maintenance mode
504	Gateway Timeout	Upstream server took too long to respond

A 200 response means the server is up. Codes in the 5xx range indicate the server is having problems.

Common reasons websites go down

Understanding why sites go down helps you diagnose faster and prevent outages on your own site.

Server overload

Too many simultaneous visitors can overwhelm a server. This is common during product launches, viral social media posts, or large promotional campaigns. Symptoms include slow load times, 503 errors, and intermittent availability. The fix is load balancing, CDN caching, or upgrading server capacity.

Expired domain

If a domain registration lapses, DNS stops resolving the domain and the site becomes unreachable to everyone — even if the web server itself is running fine. This is a surprisingly common cause of outages for small businesses and personal sites. Always enable domain auto-renewal.

Expired SSL certificate

If an SSL/TLS certificate expires, browsers refuse to load the site and display a security warning instead. The site technically responds, but users cannot proceed past the warning. Set up certificate auto-renewal (Let's Encrypt does this automatically) to avoid this.

DDoS attack

A distributed denial-of-service attack floods a server with traffic from thousands of compromised devices, making it unreachable for legitimate users. Mitigation requires DDoS protection services like Cloudflare.

Misconfigured DNS

Changes to DNS records — moving hosting providers, changing nameservers, updating A or CNAME records — can cause temporary outages during propagation (which can take up to 48 hours). Careful DNS change management and low TTL values reduce propagation time.

Database or application errors

A bug in a recent deployment, a full disk, a database connection limit reached, or a crashed background process can cause 500 errors. This is a code-level or infrastructure-level issue that requires the site owner to investigate server logs.

CDN or third-party service outage

Sites that rely on content delivery networks, payment processors, or other third-party APIs can appear broken when those services have outages. The site's own server may be fine, but dependencies are failing.

What to do when a site is down just for you

If the uptime checker confirms the site is up globally, the issue is on your end. Try these steps in order:

1. Clear your browser cache: Old cached files can cause rendering errors. In Chrome: Settings → Privacy and Security → Clear browsing data. Check "Cached images and files."

2. Try a different browser: If the site works in Firefox but not Chrome, the issue is browser-specific (extension conflicts, corrupted cache, or a browser setting).

3. Flush DNS cache: As described above. Outdated DNS records are a frequent culprit.

4. Try a different network: Switch to mobile data or a different Wi-Fi network. If the site loads, your home network or ISP has a routing issue.

5. Check firewall and security software: Antivirus software or corporate firewalls can block specific sites. Temporarily disable them to test (and re-enable immediately after).

6. Use a VPN: A VPN routes your traffic through a different server, bypassing local network and ISP issues. If the site loads with a VPN, your ISP or local network is blocking it.

7. Contact your ISP: If nothing else works, your internet service provider may have a routing issue or a DNS problem affecting certain domains. Contact their support.

How to monitor your own website's uptime

If you run a website, you should not rely on users to tell you when it goes down. By the time someone reports an outage, you may have already lost hours of traffic and revenue.

Set up automated uptime monitoring

A monitoring service pings your website every 1–5 minutes from external servers. If it fails to respond, you receive an alert immediately via email, SMS, or Slack.

The FixTools Uptime Monitor lets you check your site on demand. For continuous monitoring, use it alongside automated alerting to stay informed the moment your site goes offline.

What to monitor

Do not just monitor your homepage. Check:

• Homepage: Basic availability
• Login page: If authentication is down, users cannot access your product
• Checkout or payment page: Lost transactions are directly measurable revenue loss
• API endpoints: If your site uses an API, monitor critical endpoints directly
• Admin panel: Catch backend issues independently of the frontend

Interpret response time, not just status

A site can be "up" in the sense that it returns a 200 response, but be so slow that users give up. Track response time alongside availability. A page that normally loads in 300ms taking 8 seconds to respond signals a problem even before it goes fully down.

Uptime SLAs and hosting providers

When choosing a hosting provider, look at their uptime guarantee (SLA). Common tiers:

• 99.9% uptime: ~8.7 hours downtime per year — acceptable for most sites
• 99.95% uptime: ~4.4 hours downtime per year — good for business sites
• 99.99% uptime: ~52 minutes downtime per year — expected for e-commerce and SaaS

Ask whether the SLA applies to network uptime, server uptime, or service uptime — the distinction matters when claiming compensation for outages.

Check website status now

Whether you need to check if someone else's site is down or monitor your own, the FixTools Uptime Monitor gives you an instant answer — status code, response time, and whether the site is reachable from outside your network.