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.