Website Uptime Monitor
Check up to five websites on a schedule while this page is open and see each one's HTTP status, response time and recent results. Not a 24/7 monitor.
Still loading. If the tool doesn’t appear, reload this page.
About this tool
Website Uptime Monitor: Status and Response Time Checks
Watch up to five websites while this page is open: each check reports the HTTP status and response time, with a strip of recent results.
Website Uptime Monitor checks up to five web addresses on a schedule you pick, from every minute to every 15 minutes, for as long as this page stays open. Each check asks ALTFTool's server to request the address once and report the final HTTP status and how long it took, so a site counts as up when its answer falls in the range you choose. The results of the visit build up as a strip of recent checks, a response-time line and a share of checks passed. It is a watch-while-you-work tool: when the tab closes, checking stops, and it sends no alerts.
How to use Website Uptime Monitor
- 1
Type a website address such as example.com (https:// is added for you) and choose how often to check it.
- 2
Pick what counts as up: a 200–299 answer, anything up to 399, or any HTTP answer at all.
- 3
Press Add website. The first check runs straight away and the next ones follow your schedule while the page is open.
- 4
Read each card: the current status, the last response time, the average when up, the checks passed and the strip of recent results. Pause, check now or remove a site at any time.
Why use Website Uptime Monitor
Real status codes, redirects followed
Every check is an actual request to the address. Redirects are followed up to five hops, so you see the status of the page a visitor finally lands on.
Your rule for up
Decide whether only a 2xx answer counts, whether redirects are fine, or whether any answer at all means the server is alive.
Honest about its limits
It runs only while the page is open, from one server region, and keeps the history of this visit only. It says so on the page instead of implying round-the-clock monitoring.
Nothing to sign up for
The list of addresses and their settings stay in this browser's storage. The check history is not saved anywhere.
Common use cases
- Watching a site come back after a deploy, a DNS change or a server restart, without refreshing it by hand.
- Keeping an eye on a client's site or a status endpoint during a launch or a maintenance window.
- Spotting slow answers: a response-time line that climbs over a few minutes before anything fails outright.
- Confirming that a redirect or a health check URL answers with the status code you expect.
Frequently asked questions
Does it keep checking after I close the page?
No. Checks run only while this page is open in your browser. Close the tab, or let the device sleep, and checking stops until you come back. For round-the-clock monitoring with alerts you need a service that runs on its own server.
Will it email or message me when a site goes down?
No. It sends no alerts. While the page is open, a change of status is shown on the card and announced to screen readers.
Where do the checks come from?
From ALTFTool's server. It makes one GET request per check, reads only the response headers, follows up to five redirects and reports the final status and the time taken, including the DNS lookup and any redirects. It cannot check private or local network addresses.
Why does a site show as down when it opens fine for me?
The check comes from one server region, and some sites block automated requests, filter by country or answer a bot with an error page. The reason is shown on the card, such as an HTTP code or a refused connection.
What does "checks passed" mean?
The share of this visit's checks whose answer met your rule for up. It is not uptime over days or weeks, because the page cannot see what happened while it was closed. Checks that could not run at all, for example while you were offline, count as neither up nor down.
Is my list of sites saved?
The addresses and their settings are saved in this browser's local storage so they are there next time. The results of the checks are not saved.