Website Uptime Probe

Next

A full monitoring platform is overkill when you just want to know “is this site up right now, and how fast does it answer?”. This probe sends one request to your URL from our server in Europe and records the HTTP status, the response time and whether it was up. Click Probe again to add more samples: it keeps a rolling history of the last 20 and shows your uptime percentage and average response time. No account, no agent, no setup.

How to probe a URL

  1. 1

    Paste the URL

    Any public HTTP or HTTPS address.

  2. 2

    Probe now

    We send one request from our server in Europe and add the result to the list.

  3. 3

    Repeat to build history

    Each click adds a sample; the last 20 are kept while this tab stays open.

  4. 4

    Read the summary

    See the number of samples, the uptime percentage and the average response time.

What each sample shows

Every time you click Probe now, the tool records one line:

Column Meaning
Time When the sample was taken, on our server’s clock
Status The HTTP status code the site returned (0 if it did not answer)
Response time Total round trip in milliseconds, measured from our server
UP / DOWN UP if the status was 200-499; DOWN on 5xx, a timeout or no answer

The summary above the list keeps a rolling window of the last 20 samples: how many you have taken, the share that were UP (uptime %) and the average response time across them.

Reading the response time

The response time is the whole round trip from our server: the DNS lookup, the connection, the TLS handshake and the wait for the first byte, added into a single number. It is measured from our data centre in Europe, so it is a consistent baseline, not the exact speed your own visitors will see. Watch the trend across samples rather than any single figure: an occasional spike is normal, but response times that climb steadily suggest the server is under load.

When to probe more than once

  • Intermittent problems only show up with repeated samples. One healthy answer does not prove the site has been stable all day, so probe several times over a few minutes.
  • A flaky connection shows as a mix of UP and DOWN in the list, and an uptime below 100%.
  • A slow-down shows as response times creeping up while the status stays 200.

What this probe is not

This is an on-demand spot check, not continuous monitoring. It only runs when you click, it samples from a single location in Europe, and it keeps nothing once you close the tab: there are no alerts, no emails and no background checks. For round-the-clock monitoring with notifications, use a dedicated uptime service or a scheduled job in your own infrastructure.

Frequently Asked Questions

Not entirely. A 200 means the server answered successfully at the HTTP level, but the page could still be broken (a database error inside the body, failed scripts). The probe checks reachability and speed, not whether the page renders correctly. Pair it with a screenshot tool for visual confirmation.

Because the server answered. UP here means the site is reachable and responding (any status from 200 to 499), even if that page redirects, blocks the request or is missing. Only 5xx errors, timeouts and refused connections count as DOWN.

Up to 20, as a rolling window: the 21st sample pushes out the oldest. The samples live only in this browser tab while it is open; Clear wipes them, and closing the tab discards them.

No. It runs only when you click and from one location, so it is a quick health check, not 24/7 monitoring. There are no scheduled checks and no alerts. For continuous coverage with notifications, use a dedicated monitoring service.

Related Tools

Tool available in other languages