How to Check if a Website Is Down or Just Slow

Updated

A website is "down" only if it fails to respond from multiple independent locations, not just yours. Check-Host.net is a free online tool that tests availability of websites, servers, hosts, and IP addresses from servers in different countries and datacenters, so you can separate a real outage from a local network, ISP, or routing problem. Use it when a site won't load, loads slowly, or loads for others but not for you.

Step 1: Confirm the symptom before testing

Decide what you're actually seeing, because each symptom points to a different tool:

  • Nothing loads at all → start with Ping and HTTP checks.
  • Loads very slowly → HTTP check for response performance, Ping for latency and packet loss.
  • Loads sometimes, or only for some people → check DNS and TCP port.
  • Loads for everyone except you → compare your result against checks from other locations.

Step 2: Run a multi-location HTTP check

The HTTP tool checks a website's response performance and availability from many countries and datacenters.

  1. Enter the site's hostname (for example, example.com) into the check field.
  2. Select multiple check nodes in different regions rather than a single one.
  3. Run the check and read the results per node.

What to look for:

  • All nodes fail → the site is very likely down or its server is unreachable.
  • Some nodes succeed, some fail → the site is up, but reachability is regional or routing-dependent. This is not a full outage.
  • All nodes succeed but slowly → the site is up but slow, which is a performance problem, not an availability problem.

Step 3: Use Ping to measure reachability, latency, and packet loss

Ping tests the reachability of a host and measures network latency and packet loss from servers around the world.

  • High latency from all locations → the server or its network path is slow.
  • Packet loss above zero → the connection is unstable; intermittent loss often explains "sometimes it loads, sometimes it doesn't."
  • No response from any location → the host may be blocking ICMP, which does not by itself prove the site is down. Confirm with an HTTP check.

Step 4: When results are inconsistent, check DNS and TCP ports

If the site loads inconsistently, the problem may be name resolution or a specific service port rather than the whole server.

DNS check: retrieves A, AAAA, and PTR records with TTL from nameservers around the world. Use it to:

  • Confirm the domain resolves to the expected IP address.
  • Compare records returned by different nameservers — mismatches suggest DNS propagation or misconfiguration.
  • Watch TTL values when you've recently changed DNS and are waiting for updates.

TCP port check: tests whether a TCP connection can be made to a specified port on the host. If HTTP fails but the TCP port responds, the server is reachable and the problem is at the application layer. If the port doesn't respond, the service itself may be down or firewalled.

UDP port check: tests whether communication over UDP works on a specified port, useful for services that don't use TCP.

Step 5: Rule out your own connection first

Before concluding a site is down, eliminate local causes:

  1. Try the site on a different network (mobile data instead of Wi-Fi).
  2. Compare your result with multi-location checks — if other locations succeed, the problem is on your side.
  3. Check whether your ISP, router, or a local firewall is blocking the site.
  4. If you use a VPN or proxy, test with it disabled.

Quick reference: symptom to tool

Symptom Tool to use What confirms the problem
Site won't load at all HTTP + Ping Failure from all locations
Site is slow HTTP + Ping High latency or packet loss across nodes
Loads for some, not others HTTP (multi-location) Mixed success across regions
Loads inconsistently DNS + TCP port DNS mismatch or port not responding
Only you can't reach it Compare with multi-location checks Other locations succeed

Related tools on the same site

Check-Host.net also provides IP info (geolocation data such as country, region, city, time zone, ISP, and organization for an IP address or hostname), a subnet calculator that converts between IP address ranges and CIDR notation, and a live server terminal for diagnostic or testing purposes. An API is documented for building your own monitoring solution, and a FAQ covers usage questions.

Bottom line

A site is down only when it fails from multiple independent locations. Use HTTP checks across regions to confirm availability, Ping to measure latency and packet loss, and DNS plus TCP port checks when results are inconsistent. If other locations succeed and only yours fails, the problem is almost certainly local — your network, ISP, or a block on your side, not the website.