How to Check If a Website Is Down for Everyone or Just You
A few quick checks across status pages, cellular data, and DNS can tell you within a minute whether a site is broken globally or stuck on your connection.
When an essential website refuses to load, your first instinct might be to reboot the Wi-Fi router or blame the site's servers. Neither guess is necessary. With a quick sequence of checks, you can pinpoint in under a minute whether an outage is hitting everyone on the internet or just your local device, home network, or internet provider.
Start with the simplest isolation test: switch networks. Turn off Wi-Fi on your phone and load the exact same URL over cellular data. If the page opens smoothly on 5G but hangs on your home broadband, the website is fine and the trouble sits somewhere between your device, your router, and your ISP.
Check official status pages and outage trackers
If the site fails on both Wi-Fi and cellular data, look for outside confirmation. Most major platforms, including Microsoft 365, AWS, Cloudflare, GitHub, and Slack, maintain dedicated status pages hosted on separate infrastructure so they stay readable during an outage. Keep in mind that official dashboards often lag reality by 10 to 20 minutes while engineers verify alerts.
Crowd-sourced monitors such as Downdetector and independent HTTP checkers like Is It Down Right Now fill that gap. A sudden vertical spike in reports from multiple cities almost always confirms a widespread service failure. Conversely, flat report lines suggest a narrower regional routing problem or a local configuration glitch.
Read the error code and test DNS
Browser error messages carry useful clues. Codes starting with 5, such as HTTP 500, 502 Bad Gateway, or 503 Service Unavailable, mean your computer successfully reached the remote server and the remote system failed internally. That is almost never your fault. Messages mentioning DNS_PROBE_FINISHED_NXDOMAIN or connection resets point toward local name resolution issues, an overzealous VPN, or an expired browser cache.
Opening the page in a private browsing window rules out corrupted cookies and extensions. If only a handful of sites fail on your home network, switching your device's DNS resolver temporarily to a public resolver like 1.1.1.1 or 8.8.8.8 often restores access immediately when an ISP's default DNS servers stumble.