Is it down — or just you?
Enter a URL. We fetch it from the uptime.bet server (HTTP status, response time, redirects) and ask our monitoring nodes around the world to ping the host at the same time.
What “reachable from everywhere” means here
The HTTP(S) request runs from the uptime.bet application server. A status below 500 counts as “up” — even a 404 means the server answered.
In parallel, each monitoring node (currently Frankfurt, Singapore, USA and a local node) sends 10 ICMP pings to the host. That shows whether the network path works from different regions.
Many hosts and CDNs drop ICMP, so a failed ping alone is not proof of an outage. Continuous HTTP checks from multiple nodes are what uptime.bet monitors do.
+The site is down for me but this says it is up — why?
The problem is probably on your side: local DNS cache, ISP routing, a firewall, a browser extension or a regional issue. Try another network or flush your DNS cache.
+Why does the ping fail while HTTP works?
Many servers and CDNs block or rate-limit ICMP. HTTP is the more meaningful test for websites.
+Can I check internal or private addresses?
No. Private, loopback, link-local and cloud-metadata addresses are refused, also after redirects.
+Which ports are supported?
HTTP and HTTPS on ports 80, 443, 8080 and 8443.
+How do I get alerted automatically?
Create a free account and add an HTTP monitor. uptime.bet checks it continuously and notifies you by email or webhook.
Get alerted the next time it goes down
Monitor this URL continuously instead of checking by hand. Email or webhook alerts — free plan, no credit card.
uptime.bet is in a public test phase: free to use, no warranty, billing not enabled yet.