How to check if a website is really down: five methods that work
Sometimes a page will not load and you need to know fast whether it is down for everyone or only for you. Here are five ways to check, ranked by speed and reliability.
Method 1: An external checker like QuickUptime
An external checker tries to load the page from a server that is not on your network. That is the simplest way to separate a problem on your side from a problem on the server side.
Drop the URL in, wait a couple of seconds, and read the result. If the checker says the site is up, your local network or device is at fault. If it says the site is down, you have confirmed it is a real outage.
Why this works: the checker has no shared DNS cache with you, no shared internet provider, and no shared browser extensions. It is the closest thing to a clean second opinion.
Method 2: Ask a friend on a different network
Send the link to someone who is not in your home, office, or on your Wi Fi. A friend in a different city is best. If the page works for them, the problem is in your network.
This is also useful when a site is regionally blocked or geo restricted. If your friend is in another country and the page works for them, the site may be blocking your country, not actually down.
Method 3: Search the site's name on social media
When a popular site goes down, people complain quickly. Search the site name on X (formerly Twitter) or look at the trending tab. If many users in different places are saying it is down at the same time, that is strong evidence of a real outage.
Reddit also has subreddits dedicated to specific apps and services. A quick scan of recent posts often confirms an outage within minutes.
Method 4: Use a command line ping or curl
If you are comfortable in a terminal, run a quick test from your machine. Two commands cover most cases.
Type ping example.com to see if your computer can reach the server at all. If you see replies coming back, the server is reachable. If you see request timed out or 100 percent loss, your network can not reach it.
Type curl -I https://example.com to ask for just the page headers. A response that starts with HTTP/1.1 200 or HTTP/2 200 means the page is up. A non 200 response code points to a specific problem. A failure to connect at all points to a network issue.
Note that some servers block ping but still serve web pages, so a failed ping is not always proof of a real outage. Pair it with a curl check.
Method 5: Check the company's status page
Many large services run a status page at status.example.com or example.com/status. The status page is meant to show, in close to real time, whether each part of the service is healthy.
When the status page shows yellow or red, the company has confirmed the issue. When it shows green but you can not reach the site, the problem is either too new to be reported yet, or it is on your end.
Status pages are useful but not always honest. A site may be down for many users while the status page still shows green. Treat the status page as one data point, not the final word.
Bonus: combining methods for a clear answer
If you want to be sure in under two minutes, use a fast combo:
- Check QuickUptime for an external view.
- Search the site name on X to see if others are reporting trouble.
- Try opening the site in a private window on your phone using mobile data.
If all three say the site is up, the problem is your network or device. If two or more say it is down, you are dealing with a real outage and the best move is to wait.
How long should you wait before retrying?
Most outages on big consumer sites are short. A study of recent public outage data from sites like X, Discord, and GitHub shows most disruptions last under an hour. Smaller sites can take longer because they have fewer engineers on call.
A reasonable retry schedule is to check again at five minutes, fifteen minutes, and one hour. If it is still down after an hour, follow the company's status page or social media for an estimated time of fix.