Check if any website is reachable right now. Probed from a Cloudflare edge server and a neutral host, so a site that only blocks Cloudflare is not reported as down.
Enter a domain or URL to check if it is reachable
It sends an HTTP HEAD request from a Cloudflare edge server to the target URL and reports back the HTTP status code and response time. A 2xx or 3xx response means the server is up and reachable. A 5xx response means the server returned an error. No response at all (timeout) means the host could not be reached from the edge server.
For popular services like GitHub, Discord, Cloudflare, OpenAI, Anthropic, Vercel, GitLab, Stripe, npm, Reddit, Atlassian, Slack, Figma, and others, the tool also pulls the official status from their status page API. A colored dot on each site card shows the current status at a glance: green means all systems operational, amber means a degraded service, orange or red means a partial or major outage. This catches cases where a site returns HTTP 200 but is functionally broken, like a Cloudflare outage where the HTML loads but JavaScript crashes.
The Ping tool measures latency over 5 rounds and shows min, avg, and max response times - it is focused on how fast a host responds. This tool asks a single question: is it up right now? One check, clear UP / DOWN verdict, HTTP status code shown.
A 4xx status (400 Bad Request, 403 Forbidden, 404 Not Found, etc.) means the server responded and is reachable - but rejected the request. This often happens because the site geo-blocks Cloudflare IPs, requires authentication, or blocks HEAD requests. The site itself is almost certainly up; the result is shown in amber to flag that the response was not a clean success.
This check runs from the Cloudflare edge node nearest to you and from our own server. Our server keeps the address you checked (without anything after a '?') for a year, to show its history. If the site shows DOWN but you can reach it in your browser, the most likely explanations are: (1) the site blocks Cloudflare's IP ranges, (2) there is a regional outage affecting only some locations, or (3) the site requires a browser-like TLS fingerprint and rejects automated requests. If the site shows UP but you cannot reach it, your local network or ISP is the more likely culprit.