Down for Everyone or Just Me? How to Tell

The Question Every Internet User Asks

You click a link. The page does not load. You try again. Nothing.

The immediate question: is this website broken for the entire internet, or is something wrong on my end?

The answer matters because it determines what you do next. If the site is down for everyone, you wait. If the problem is local to you, there are specific things you can fix right now. For a broader look at checking site status, see our guide on how to check if a website is down. This guide focuses specifically on telling the difference between a "just me" problem and an "everyone" problem.

Method 1: Use an Online "Is It Down" Checker

The fastest approach is to let a third-party server test the site for you. Online checkers like "Down For Everyone Or Just Me" and similar services send an HTTP request to the target URL from their own infrastructure. If their server can reach the site but you cannot, the problem is on your end. If their server also cannot reach it, the site is genuinely down.

These tools take about five seconds. Type in the URL, hit enter, and get a yes-or-no answer.

The limitation is that most of these checkers test from a single server location (or a small set of locations). A website can be down in one geographic region while working fine in another. If you need geographic specificity, use a tool that tests from multiple locations around the world, or combine this method with the ones below.

Method 2: Try a Different Network

Your home WiFi and your mobile data connection route through completely different networks, different ISPs, different DNS resolvers, different routing paths. If a website loads on mobile data but not on WiFi (or vice versa), the problem is network-specific.

Turn off WiFi on your phone and load the site over cellular data. If it works, the issue is with your WiFi network, your router, or your ISP. If it fails on both networks, the problem is more likely on the website's end.

This is one of the most underrated diagnostic steps. It takes ten seconds and immediately narrows the problem space by half.

Method 3: Try a Different Browser or Device

Browser-specific issues are surprisingly common. Cached data, corrupted cookies, or browser extensions can prevent a site from loading even when the site itself is perfectly healthy.

Open the site in an incognito or private browsing window. This disables most extensions and ignores cached data. If the site loads in incognito mode but not in your normal browser session, the culprit is your browser's cache, cookies, or an extension.

You can also try a completely different browser. If Chrome fails but Firefox works, you have isolated the problem to Chrome-specific data or settings.

Testing on a different device on the same network provides another data point. If your laptop cannot reach the site but your phone can (while both are on WiFi), the issue is specific to your laptop's configuration.

Method 4: Check from a Different Geographic Location

Some outages are regional. A server in the US might be down while the European servers are fine. A CDN edge node serving your region might be failing while other edge nodes work normally.

A VPN is the easiest way to simulate a check from another location. Connect to a VPN server in a different country and try loading the site. If it works through the VPN, the outage is regional or specific to your ISP's routing.

You can also ask a friend or colleague in a different city or country to try loading the site. It is low-tech, but it works.

For a more systematic check, use website testing tools that render pages from servers in multiple countries. These show you exactly what a user in Tokyo, London, or Sao Paulo would see.

Method 5: Command-Line Diagnostics

If you want more detail than a yes-or-no answer, command-line tools reveal exactly where the connection is failing.

DNS lookup tells you whether the domain name resolves to an IP address:

nslookup example.com

If this returns nothing or an error, the domain is not resolving. That could mean DNS is broken on your end (your resolver is having issues) or on theirs (the domain's DNS records are misconfigured or the domain expired).

Curl sends an HTTP request and shows the response:

curl -I https://example.com

A 200 OK response means the site is up and serving content. A 503 Service Unavailable means the server is reachable but something is wrong with the application. A connection timeout means the server is not responding at all.

Traceroute shows the network path between you and the server:

traceroute example.com

On Windows, use tracert example.com. This reveals where packets are being dropped. If the trace dies at a hop owned by your ISP, the routing problem is on your side. If it reaches the destination network but the site still does not load, the problem is at the server level.

Common Reasons It Is Just You

When the site works for the rest of the world but not for you, the cause is almost always one of these:

Stale DNS Cache

Your computer caches DNS lookups to avoid resolving the same domain repeatedly. If the website recently changed its IP address, your cached entry might point to the old (now dead) server. Flushing your DNS cache forces a fresh lookup.

On Windows: ipconfig /flushdns

On macOS: sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

On Linux: sudo systemd-resolve --flush-caches (or restart your DNS resolver)

For a full walkthrough of flushing DNS on every operating system, see the DNS cache flushing guide on DNS Monitoring Tool.

ISP DNS Resolver Problems

Your ISP's DNS resolver can have outages or return stale records. Switching to a public DNS resolver like Google (8.8.8.8) or Cloudflare (1.1.1.1) often fixes this immediately. You can change your DNS server in your network adapter settings or your router configuration.

Browser Cache or Extensions

Ad blockers, privacy extensions, and security tools can block requests to certain domains. A corrupted browser cache can serve broken content even after the site has been fixed. Testing in incognito mode rules this out.

Local Firewall or Antivirus Software

Security software on your computer can block specific domains or IP ranges. Corporate firewalls and network-level content filters can do the same. If you recently installed security software or if your IT department manages your network, this is worth investigating.

Hosts File Override

The hosts file on your computer can override DNS and point a domain to a specific IP address. Developers sometimes use this for local development and forget to revert the change. Check /etc/hosts on macOS/Linux or C:\Windows\System32\drivers\etc\hosts on Windows.

IP-Based Blocking

Some websites block specific IP addresses due to rate limiting, abuse detection, or geographic restrictions. If the site is up for everyone else but refuses your connection specifically, your IP may have been flagged. A VPN or a different network will confirm this.

Common Reasons It Is Down for Everyone

When the site is genuinely unavailable to the entire internet, the cause typically falls into one of these categories. For a more detailed breakdown, see our guide on website downtime causes and prevention.

Server Crash or Overload

The web server process (nginx, Apache, or the application server) has crashed or the server is overwhelmed with traffic. This is the most common cause of global downtime. The server hardware might be fine, but the software serving web pages has stopped responding.

DNS Failure

If the domain's nameservers are unreachable or the DNS records are misconfigured, nobody can resolve the domain to an IP address. The site effectively disappears from the internet. This can happen if the DNS provider has an outage or if someone accidentally deletes DNS records.

DDoS Attack

A distributed denial-of-service attack floods the server with so much traffic that it cannot serve legitimate requests. During a DDoS attack, the server is technically online but too overwhelmed to respond to real users.

Expired Domain Registration

If the site owner forgets to renew their domain (or auto-renewal fails due to an expired credit card), the domain stops resolving. The site is still running on the server, but nobody can reach it because the domain no longer points anywhere.

Expired SSL Certificate

An expired SSL certificate does not make the site unreachable in the traditional sense, but modern browsers will display a full-page security warning that blocks most users from proceeding. Functionally, the site is down.

Hosting Provider Outage

When AWS, Google Cloud, Cloudflare, or any other hosting provider has an outage, every site hosted on the affected infrastructure goes down simultaneously. These outages are usually resolved by the provider, and there is little the individual site owner can do besides wait. For tips on identifying third-party service outages quickly, see the guide on how to check if a service is down.

A Quick Diagnostic Flowchart

When a site is not loading, work through this sequence:

1. Try the site in an incognito window. If it loads, clear your browser cache and check your extensions.
2. Try the site on a different network (mobile data instead of WiFi). If it loads, the problem is your network, ISP, or DNS resolver.
3. Try the site on a different device. If it loads, the problem is your machine's configuration (hosts file, firewall, DNS cache).
4. Use an online checker to test from an external server. If the checker says the site is up, the problem is definitely on your end.
5. If the checker also says the site is down, confirm with a second checker or a command-line test. The site is likely down for everyone.

Most of the time, you will have your answer by step 2.

What to Do If the Site Is Down for Everyone

If you are a visitor, there is not much you can do besides wait. Check the site's social media accounts or status page for updates. Some companies post outage notifications on Twitter/X or their dedicated status page.

If you are the site owner, you need to move through diagnostics quickly:

Check your hosting provider's status page first. If they are reporting an incident, your site is caught in a broader outage. Monitor their updates.

Verify DNS resolution with dig yourdomain.com A. If DNS is not resolving, check your domain registration status and DNS records.

Check your SSL certificate if users are seeing security warnings. Run openssl s_client -connect yourdomain.com:443 to inspect the certificate.

If you have server access, check whether your web server process is running and review error logs. Restart services if needed.

Communicate with your users. A brief message on social media or your status page acknowledging the issue goes a long way. People are far more patient when they know someone is working on the problem.

Why Automated Monitoring Removes the Guesswork

The "down for everyone or just me" question only comes up when you find out about a problem manually, usually after a user reports it or you happen to visit your own site.

Automated monitoring removes this lag entirely. For a deeper look at what website monitoring involves, it starts with a service that checks your site from multiple geographic locations every few minutes. When the site goes down, you get an alert immediately, along with data about where the failure is occurring and what type of error is being returned. You do not have to guess whether it is down for everyone or just you. The monitoring tool has already answered that question from five different locations.

For a complete look at preventing outages before they happen, see our website maintenance and monitoring guide. For more on uptime monitoring specifically, Website Uptime Monitor has a good primer.

This matters because every minute between "site goes down" and "you find out" is a minute where users are bouncing, revenue is lost, and your reputation takes a hit. The difference between a 2-minute response and a 2-hour response is almost always whether monitoring was in place.