A website can be available from one network and unreachable from another. Checking status and latency from more than one region helps separate a global outage from a routing, DNS, firewall, CDN, or regional availability problem.
Check the complete request path
Start with the final URL and record whether the request resolves DNS, connects to the host, completes TLS, and returns an HTTP response. A timeout and an HTTP 503 are different failures: the first may indicate connectivity or routing trouble, while the second confirms that a server or upstream returned a response.
Record redirects as well as the final status. A redirect loop, an unexpected HTTP-to-HTTPS redirect, or a hostname mismatch can make a site appear broken even when the origin server is running.
Compare regions and latency
Run the same check from multiple regions when users report location-specific problems. A large latency difference can point to CDN routing, peering, overloaded origins, or a distant deployment region; it does not automatically mean the site is down.
Use repeated checks instead of treating one request as a definitive measurement. Network latency varies with congestion, DNS caching, and the path selected by each provider.
Turn a check into a useful incident signal
Keep the URL, timestamp, region, status code, redirect chain, and measured latency together. Pair external checks with origin logs and synthetic monitoring so you can distinguish user impact from an isolated probe failure.