Ping Test — Website Uptime Checker
Enter any website. We'll send four HTTPS probes from our edge servers and report response time, success rate, and HTTP status. Useful for spotting slow responses, timeouts, or intermittent outages.
What this tool does
This ping test sends four consecutive HTTPS requests from our edge probes to any website you enter and reports the exact response time, HTTP status code, and success rate of each attempt. Unlike traditional ICMP ping (which browsers can't send), it measures the actual latency users experience when the site serves a real HTTP response — the number that actually matters for perceived speed and reliability.
When to use it
- A site feels slow — check whether latency is consistent or wildly variable.
- Users say a site is broken — confirm reachability from an outside network.
- You just deployed — verify the site is answering with a healthy status code.
- Debugging DNS or CDN issues — see whether the origin responds at all.
How to read the result
- Success 100% + low avg — healthy. Site is fast and reliable from our vantage point.
- Success 100% + high avg — reachable but slow. Look at CDN, TLS handshake, or origin performance.
- Success 50–75% — flaky. Intermittent failures point to load, rate-limiting, or an unstable origin.
- Success 0% with 5xx — the server is answering but broken.
- Success 0% with timeouts — DNS, network, or firewall issue. Site is effectively down.
Frequently asked questions
How is this different from a traditional ICMP ping?
Browsers can't send ICMP packets, so this tool measures HTTP response time instead. It's what actually matters for websites — a server may respond to ICMP ping but still take 20 seconds to serve a page. HTTP timing reflects the real user experience.
What counts as 'up'?
Any HTTP response with a status code below 500. This includes 200 OK, redirects, and even 404 Not Found — because they all mean the server is alive and responding. Only 5xx errors and network-level failures are counted as down.
How many probes does it run?
Four consecutive HTTPS requests, each with an 8-second timeout. We calculate min, max, average latency, and success rate across them so a single flaky probe doesn't skew the result.
Why does the timing look higher than my browser's network tab?
Our probe runs from our edge servers, not from your device. Depending on where you are and where the target is, network paths differ. What matters is consistency — a stable 300ms is healthier than an unpredictable 100–2000ms range.
Can I ping any website?
You can enter any publicly reachable HTTPS domain. We don't support raw IPs, non-HTTPS URLs, private ranges, or intranet hosts. Some sites also block automated user-agents; those will show as timeouts even though real browsers can reach them.