Website Down Checker
Is a website down for everyone, or just for you? Enter its address or paste a link. We check it live from Mumbai and from 7 other locations across North America, Europe, Asia and Oceania, and show whether it answered, the HTTP status code, how fast it replied and where it redirected.
Works for any public website. For banks, UPI apps, telecom and government portals we track, you also see what other users are reporting.
How the Website Down Checker works
-
Step 1
You enter a website.
Type an address such as example.com, or paste any link from your browser.
-
Step 2
≤ 8sWe send live requests.
Our checks open the site the way a browser would, from Mumbai and from 7 other locations at the same time, and wait up to 8 seconds for each answer.
-
Step 3
≤ 4 redirectsWe follow redirects.
If the site sends us to another address, we follow it, up to 4 times, and note each step.
-
Step 4
You see the result.
Whether the site responded, its HTTP status code, the response time, the redirect path and the time of the check.
HTTP status code Response time Redirect path Time of the check
What the result means
The site answered our check. A site that turns automated visitors away with 401 or 403 is still running, so it counts as responding.
No answer within 8 seconds, a server error (5xx) or "too many requests" (429). The site may be down, or it may be blocking automated checks for now.
The address sent us on to another one. The result shows where it ended up and every step on the way.
It kept sending us on to new addresses, so we stopped after 4, the same way a browser gives up with "too many redirects".
HTTP status codes you may see
The page loaded normally
The site refused automated visitors, but the server is up
The server is up, but that page does not exist
The address moved, and the site sent us to the new one
Too many requests; the site is limiting traffic
A server or gateway error on the site's side
Timeout, a DNS failure or an SSL certificate problem
Is it down or just me?
If our check gets an answer
the site is up.
The problem is most likely between you and the site:
If our check cannot reach it either
it is probably down for everyone,
or the site is blocking automated checks for now.
- Wait a few minutes and use Test again.
- The company's official social media account is usually the first place it announces an outage.
Website not loading for you? Try these
-
1
Switch between Wi-Fi and mobile data. If it opens on one, the problem is your connection.
-
2
Open the site in a private or incognito window. If it works there, clear the browser cache and cookies for that site.
-
3
Turn off browser extensions and any VPN, then try again.
-
4
Restart your router, or change your DNS to a public one such as 1.1.1.1 (Cloudflare) or 8.8.8.8 (Google).
-
5
Check your device's date and time. A wrong clock causes SSL certificate errors on many sites.
-
6
Try another browser or device. If nothing works anywhere, the site is likely down for everyone.
Services we track
For these, we show what other users are reporting as well as our own check, so you know more than a single test can tell you.
See all services
Checking a website: common questions
It is a free online tool that tells you whether a website is working right now. Ours sends the site a live request and shows whether it answered, the HTTP status code, how fast it replied and where it redirected, so you can tell if it is down for everyone or just you.
Enter its address above. If our check gets an answer, the site is up and the problem is most likely on your side: your connection, your DNS, a VPN or your browser. If our check cannot reach it either, it is probably down for everyone, or it is blocking automated checks for now.
Usually something on your side: your Wi-Fi or mobile data, your internet provider, an old DNS entry, or your browser's cache, cookies or extensions. Switch between Wi-Fi and mobile data, open the site in a private window, or restart your router. A VPN, or a site that serves only some countries, can also make it fail for you alone.
Some sites block automated visitors to stop bots. Our check gets a 403 (forbidden) or 401 (sign in required), but that still means the server answered, so we show it as responding.
Some websites block visitors from other countries, and many block traffic from cloud servers to stop bots. Government and banking sites often do both. So a site can respond from Mumbai but not from Europe, without anything being wrong. If it fails from every location, it is probably down.
The site's server answered, but refused our automated check with a 401 or 403. That still means the site is running, so we count it as responding.
No. Uptime monitoring checks a site every few minutes and alerts its owner. Our checker runs once, when you ask, and shows the result straight away. For the services we track, we also check regularly and collect user reports, which you can see on each service's page.
As often as you need. Test again on the result page runs a fresh check. If you run many checks in a short time, we ask you to wait a little before the next one.
Apps talk to the company's servers behind the scenes, so checking its website is a good first step. For the apps we track, such as banks, UPI apps, telecom and government portals, the service page also shows what other people are reporting right now. Search for it above.
Yes, for the services we track. Our free status badge is a small image that shows a service's live status and updates on its own. Pick the service, copy one line of code and paste it into your website, README or docs. There is no account to create and no script to install.