Start your 7-day free trial, card not charged until it ends

Free check · 18 worldwide locations · no account needed

Is the website down for everyone?

Probe any website from 18 worldwide locations in parallel - including two UK vantage points. Find out in seconds whether the site is genuinely down, or only blocked from your location.

01 · The tool

Check a website

20 free checks per hour

Results appear below. Product updates go to

20 free checks per hour

Probing

Checking

18 locations across 6 continents

Result

Up

Down

Avg latency

Site flapping or partially down?

TLDTrack watches uptime, DNS, SSL, malware and blacklists across your whole portfolio and alerts you when something breaks, so you find out before your customers do.

Start your free trial Check DNS propagation

02 · Troubleshooting

What the result means

Three patterns, three different sets of next steps.

All Up

The site is responding from every continent we checked - it's not down. The issue is on your end. Try a different browser or device, flush your DNS cache (ipconfig /flushdns on Windows, sudo dscacheutil -flushcache on macOS), or check if your ISP or corporate firewall is blocking the host.

All Down

The site is genuinely unreachable from the public internet. Most common causes: server crashed or out of memory, DNS misconfiguration (A record pointing to an old IP), expired SSL certificate, hit your hosting bandwidth quota, or your registrar suspended the domain. If you own the site, log into your hosting control panel or contact your hosting provider.

Mixed

A regional issue. Likely causes: a CDN node failing in one region, DNS propagation in progress after a recent change, your host blocking specific IP ranges or countries, or an upstream ISP route problem. Wait 5-10 minutes and run the check again; if the same regions stay down, contact your CDN or hosting provider.

03 · Questions

Frequently asked questions

Which locations do you check from?

18 vantage points across four continents: UK (TLDTrack London plus a second London node), Europe (Frankfurt, Amsterdam, Paris, Madrid, Milan, Helsinki, Warsaw, Kyiv), North America (New York, Texas, Toronto), South America (São Paulo), and Asia (Tokyo, Hong Kong, Singapore, Mumbai). Each probe sends a real HTTP request, not just a ping, so you see actual application-layer reachability rather than just network connectivity.

Why does the site show up from London but down elsewhere?

Usually means the site is hosted in the UK without a proper CDN, so latency from further away triggers timeouts on our probes. Other common causes: the host has geo-blocked specific countries, a CDN edge is failing in one region, or your firewall is blocking specific IP ranges. Run the check again in 5 minutes - transient regional issues often resolve themselves.

What is the difference between this tool and a ping?

Ping uses ICMP and only proves the server's network stack is reachable. This tool sends a real HTTP request, so it confirms the web server is responding with a valid HTTP status code. A site can ping fine but be HTTP-dead (Nginx down, PHP-FPM crashed, database unreachable) - this tool catches that where ping cannot.

Why is the result HTTP 301, 302 or 403 instead of 200?

3xx codes mean a redirect (e.g. HTTP to HTTPS, or apex to www) - the server is up, it is just pointing the visitor elsewhere. We treat 2xx, 3xx and 4xx all as "site responding". Only 5xx codes (server errors) and 0 (connection refused or timeout) mean genuinely down.

Can I monitor a website on a schedule instead of one-shot?

Yes. This tool is a manual one-shot check. TLDTrack checks your websites every 5 minutes, and every minute once a check fails. Downtime alerts go by email on every plan, and by push, SMS, Slack, Teams or webhook on paid plans. It also watches DNS changes, SSL expiry, malware and blacklist listings. A 7-day free trial is available, card not charged until it ends.

Is this data stored or shared with anyone?

We store the email address and domain you give us so we can send occasional monitoring tips and product updates, which you can unsubscribe from at any time. We do not store the per-location probe results, and we never sell your data. The worldwide nodes are provided by check-host.net; their privacy policy applies to the requests they receive.

Why might the same URL show different IPs at different locations?

That is normal for any site behind a CDN (Cloudflare, Fastly, CloudFront, Akamai). Each location is served by the nearest CDN edge node, which has its own IP. If your IP is identical from every region, you are not on a CDN - a small change worth considering for performance and resilience.

What does "No response (timeout)" mean?

The probe sent an HTTP request but did not get any reply within 8 seconds. Could mean the server is offline, your hosting firewall is blocking that specific IP range, your DNS is failing to resolve, or the route between the probe and your origin server is broken. If other locations succeed and one times out, it is almost certainly an issue with that route - not your site.