HTTP Check
Multi-region HTTP/HTTPS connectivity test — verify uptime and response times worldwide
Usage
• Target: full HTTP/HTTPS URL (e.g. https://example.com)
• Method: choose GET, POST, or HEAD
• Redirect: whether to follow 3xx responses automatically
• Nodes: pick specific nodes; defaults to all available nodes
About multi-region HTTP/HTTPS checks
An HTTP/HTTPS check sends real requests to your URL from multiple nodes worldwide and returns each region's HTTP status code, response time, and success state. Because it verifies availability at the application layer, it reflects the real user experience better than ping alone.
Typical scenarios include monitoring availability and speed across regions, confirming a deployment or CDN switch has taken effect globally, and investigating pages that fail to load in certain regions. GET/POST/HEAD and redirect following are supported.
Frequently asked questions
How is an HTTP check different from ping?
Ping uses ICMP to measure network-layer connectivity and latency; an HTTP check sends a real HTTP request and measures whether the web service responds correctly and how long it takes. When a site won't load, the HTTP check reflects reality better.
What does the response time include?
It generally covers DNS resolution, TCP connect, the TLS handshake, and receiving the response. When one region is clearly slower, combine it with multi-location ping and traceroute to tell whether the bottleneck is resolution, the link, or the server.
Status 200 but the page is wrong — why?
HTTP 200 means the request succeeded according to the server’s response semantics, not that the business content is correct. Inspect the body, headers, cache/CDN, authentication and application logs; a status code alone cannot rule out problems at other layers.
How do I detect a region-specific access problem?
Run the check from several nodes at once and compare status codes and response times. If a single region fails or times out while others are fine, it is usually a link or regional reachability issue between that region and your server.
References and result limitations
Online results reflect the queried source or probe state at that time. Record the target, time, nodes or data source, and parameters when citing them. A single result does not establish continuous availability everywhere.
These references explain protocol or format rules; they do not endorse results produced by this site.