How to Tell If a Website Is Down for Everyone or Just You

A site suddenly won't load? Work through this order before you assume the worst.

First: try a different device and network

Try loading the same site over cellular data instead of Wi-Fi, or on your phone instead of your computer β€” this narrows down the problem fast. If it loads fine over cellular but not on your home Wi-Fi, the issue is very likely your router or your internet connection, not the site. If it fails on every device and network you try, that points toward a problem with the site itself, or somewhere along the path to it.

Check a real-time outage tracking service

Services like Downdetector aggregate reports from users worldwide who say a specific site or service isn't loading for them, and display it as a live graph. A sudden spike in reports means it's very likely a broad outage, not just you. Keep in mind these services rely on user reports, so a site with a small user base, or a very recent outage, may not show up yet.

Search social media and forums in real time

Large outages usually generate posts within minutes. Searching the service's name alongside words like 'down' or 'not working' on X (Twitter) or relevant forums often surfaces reports before any official statement β€” just keep an eye on timestamps, since older unrelated posts can mix in.

Check the official status page

Many tech services maintain a dedicated status page, often at a URL like status.servicename.com, that transparently reports current outages and which specific features are affected. Because the company runs it directly, it's usually more accurate and detailed β€” including affected regions and estimated recovery times β€” than user-report services.

Rule out a problem on your end: browser and DNS cache

If it's not a broad outage, clearing your browser cache or flushing your DNS cache can often fix it on its own. If a site recently moved servers or changed domains, your computer might still be using stale DNS information or an old cached page, causing a failed load or an outdated view. A hard refresh (Ctrl+Shift+R), clearing the browser cache, or flushing DNS are all worth trying.

Diagnose directly with ping and traceroute

A ping test tells you whether the site's server is responding at all, and traceroute shows exactly which hop along the path from your computer to the destination the connection stalls at β€” helping you narrow the problem down to your home router, your ISP's network, or somewhere near the destination server.

What a browser error code is actually telling you

Specific errors carry specific meanings: something like DNS_PROBE_FINISHED_NXDOMAIN usually means the domain name itself couldn't be resolved (often a DNS or typo issue), while ERR_CONNECTION_REFUSED means your device reached the server but the server actively rejected the connection (often meaning the service is down, not the network path). Reading the exact error code before you start troubleshooting usually points you toward the right fix much faster than guessing.

Getting more out of ping and traceroute

Ping response times that are consistently high, or that show packet loss, point to a shaky connection somewhere along the route rather than the destination being fully down. Traceroute breaks that route into individual hops, so if responses stop at a hop still inside your ISP's network, the problem is on their end; if they make it most of the way and stop right near the destination, the problem is more likely with the site's own server or hosting provider.

Frequently Asked Questions

An outage tracker shows nothing reported, but the site still won't load for me β€” what now?

Outage-tracking services depend on user reports, so problems limited to a small user base, a specific region, or a specific ISP may never get reported there. In that case, comparing access across different devices and networks, and running your own ping and traceroute test, will give you a more reliable answer.

Only one site is down and everything else works fine β€” is that still an outage?

If every other site loads normally, it's very unlikely to be a broad internet outage β€” more likely it's a problem with that specific site's server, its DNS, or the path to it specifically. Checking that site's official status page or searching social media for it is usually the fastest way to confirm.