October 12, 2026
How to check if a website is down from multiple locations
To check if a website is down from multiple locations, request the same URL from servers in different countries at the same time and compare the answers. If every location fails, the site is down for everyone. If only some fail, you are looking at a regional problem, and the site may be fine for most of your visitors.
A single check gives you one answer from one place. That answer can be wrong in both directions: a site that loads for you can be broken for another continent, and a site that fails for you can be fine for everyone else. This guide shows why, how to read a result that comes back from many places, and what to do next.
You can follow along with the free website down checker. It needs no signup.
Why a single location can lie to you
Your site is not one thing in one place. Between a visitor and your server there is DNS, one or more CDN edges, several networks and often a firewall. Each part can fail for some visitors and not for others. These are the five causes you meet most often.
A CDN edge fails
A CDN serves your site from many edge servers. When one edge breaks, only the visitors routed to it see errors. Your origin server is fine, and a check from your office, which uses a healthy edge, says everything is up.
A regional outage
A cloud region, a data center or a network provider can fail in one part of the world. Your site stays reachable from everywhere else. One location cannot tell you this is happening, because it only sees its own part of the network.
DNS has not caught up
After you change a DNS record, resolvers keep the old answer until its TTL runs out. Some visitors reach the new server and some still reach the old one. The same domain works in one country and fails in another for hours.
The site blocks a country or a network
Firewalls, bot protection and legal rules can refuse requests from certain countries or from data-center addresses. The server is up and answering, but it answers 403 or 451 to some places on purpose.
Routing between two networks breaks
The path between a visitor's network and your server crosses several other networks. A bad route or a congested link can make your site slow or unreachable for one provider and fine for all others.
How to check if a website is down from multiple locations, step by step
- Open the free website down checker and enter the address of the site, for example
example.com. - Start the check. Uptrack requests the site from 22 locations on six continents: Europe, North and South America, Asia, Australia and Africa. The results arrive one location at a time.
- Read the verdict first. It says if the site is up, down or only down in some places.
- Then read the list. Each row is one city with the HTTP status code and the response time in milliseconds. The checker treats any answer below 500 as a reply from a working server and shows you the code, so a 403 or a 451 stays visible instead of being hidden.
- Run the check again after a minute if the result is mixed. A failure that shows up in the same locations both times is real. A failure that disappears was a short glitch.
Checks are spaced a few seconds apart for each visitor, so one person cannot overload a site. Do not use the tool to test the load a site can carry.
How to read a result from many places
The pattern across locations tells you more than any single row. Use this table to turn a pattern into a likely cause and a next step.
| What you see | Likely cause | What to do next |
|---|---|---|
| Every location fails | The site, its host or its DNS is down for everyone. | Check your host's status page, the last deploy, the TLS certificate and the DNS records. Fix the origin first. |
| One region fails, the rest are fine | A regional issue: one CDN edge, one cloud region or one network route. | Check your CDN provider's status page. Look for a geo rule in your firewall. Ask the provider about that region. Your origin is probably healthy. |
| One region answers slowly | Long or congested route to your server, or no edge nearby. | Compare the response times. If one region is several times slower, move content closer or add an edge for that region. |
| Some locations answer 403 or 451 | A deliberate block: a firewall rule, bot protection or a legal restriction. | Read the response body and headers. See the guide to HTTP 451 for the legal case. Decide if the block is intended. |
| Different locations show different pages | DNS propagation, geo-based routing or a cache that has not refreshed. | Wait for the TTL to expire. Purge the CDN cache. Compare the DNS answers from several resolvers. |
If the odd rows show 403 or 451, the server is up and refusing on purpose. Our guide to HTTP 451 Unavailable For Legal Reasons explains the legal case.
Partial outages after a DNS change
If you changed a DNS record in the last day, a mixed result is normal. Resolvers around the world keep the old answer until its TTL (time to live) expires, so some visitors still reach the old server. Our guide to DNS propagation explains how long this takes and how a lower TTL before a migration shortens it.
The test is simple. Check the site from many locations and compare. If the failing locations are the same on every run and all of them show an old address or an old page, wait. If they stay down after the TTL has passed, the new record is wrong.
From a one-off check to monitoring
A check tells you what is true now. It does not tell you what happened at 3 a.m., and it does not wake you up. For that you need monitoring: the same request, repeated every 30 seconds, from several places, with an alert when it fails. HTTP and keyword monitors check from 22 locations on six continents. Several locations must confirm a failure before you get an alert. The free plan checks from Nuremberg only. Paid plans add more locations.
The confirmation step matters. One failed check from one place is often a glitch. Asking several locations to agree stops most false alarms. Read how multi-region consensus works and why alert confirmation matters for the details.
Faster detection also shortens the time to recover. The MTTR glossary page explains why detection is the part you can improve first.
When this is not the right tool
- You need to know it before your customers do. A one-time check cannot do that. Use monitoring with alerts.
- The page is behind a login. The checker requests the public address. It cannot sign in. A browser check that runs your login flow is the right tool for that.
- The problem comes and goes. A problem that lasts 20 seconds is easy to miss in a manual check. Repeated monitoring catches it.
- The server is on a private network. The checker reaches only public addresses. It cannot see an internal service.
- You want to know how many users are hit. The checker tests from data centers, not from your visitors' own networks. It shows where a problem exists, not how many people feel it.
FAQ
How do I check if a website is down for everyone or just me?
Request the site from several places at once. If every location fails, the site is down for everyone. If only your location fails, the problem is on your side: your network, your DNS resolver or a local block. The free Uptrack checker requests the site from 22 locations on six continents and shows the status code and response time for each one.
Why does a site load for me but show as down in another country?
The request may reach a different server. CDNs answer from the nearest edge, DNS can return different addresses by region, and some sites block whole countries. A failure at one edge, a routing problem between two networks, or a country block all look like "down" from one place and "up" from another.
How many locations do I need to tell a local problem from a global one?
Three locations on different continents are enough to separate a local problem from a global one. More locations help you see regional patterns, for example one continent failing while the rest are fine. A single location can never tell the two apart.
Is the multi-location checker free?
Yes. The free checker needs no signup. Checks are spaced a few seconds apart for each visitor, so one person cannot overload a site.
Does the free checker alert me when a site goes down?
No. It is a one-time check. To be told when a site goes down you need monitoring, which checks on a schedule and sends an alert to email, Slack, Discord or Telegram.
Stop checking by hand
Monitor your site every 30 seconds and get an alert when it fails. Free for 5 monitors. Paid plans from $3/mo with a 30-day money-back guarantee.