How to use Uptime monitor
- 1
Enter the address
Paste a page or API endpoint, such as your home page or a /health URL, and optionally a keyword the response must contain.
- 2
Pick a check interval
Free monitors run every 5, 10, 15 or 30 minutes; Pro adds checks every minute or every two minutes.
- 3
Add alerts
Paste a Slack or Discord incoming webhook, or any https endpoint that accepts JSON, and switch on browser notifications if you like.
- 4
Read the history
Expand a monitor for uptime, response times and incidents over 24 hours, 7 days or 30 days, or publish a status page.
Limits and Pro
Free: 3 monitors per edit key, checks every 5, 10, 15 or 30 minutes with a 10-second timeout, Slack, Discord and JSON webhook alerts, one public status page and 30 days of history. A free monitor is paused if its dashboard isn't opened for 30 days.
Pro raises the limit to 25 monitors and adds checks every 1 or 2 minutes. See Pro
About Uptime monitor
Uptime monitor requests your page from our server on a fixed schedule and records whether it answered, how long it took and which status code came back. It keeps running when your computer is off, which is the point: you find out that the shop or the API stopped responding before your customers tell you.
A check is an HTTP GET that follows up to five redirects and gives up after 10 seconds. It passes when the final response has a status below 400 and, if you set a keyword, when the first megabyte of the page contains that text, which catches a server that answers with an error page or an empty template. One failure is not enough to raise an alarm: a second check 30 seconds later must also fail before the monitor turns red, opens an incident and posts to your webhook. When it recovers, a second message reports how long the outage lasted.
Response time is measured from the moment the request is sent until the response has been read, so it includes DNS lookup, connection, TLS and the server's own work. The chart shows the average per period, with a strip of green and red cells for passed and failed checks, plus the 95th percentile for slow outliers.
It checks from a single location only, does not ping servers or test ports, cannot reach addresses inside a private network and does not send email or text messages.
Privacy
This tool runs on our server, because checks must continue while your browser is closed. The address, name, optional keyword, check interval and optional webhook address you enter are stored there, together with a SHA-256 fingerprint of the random edit key kept in your browser. Each check stores its time, status code, response time and a short failure reason; the page content we download is compared with your keyword and then discarded. Webhook addresses act as passwords, so the full address is never sent back to the page. Check results and closed incidents are deleted after 30 days; a monitor stays until you delete it, and a free monitor whose dashboard nobody opens for 30 days is paused until you resume it.
Features
Confirmed alerts
A second check 30 seconds later confirms a failure before Slack, Discord or your JSON endpoint hears about it.
Response-time history
Average and 95th-percentile response times with passed and failed checks over 24 hours, 7 days or 30 days.
Public status page
Share availability with customers without revealing the addresses you monitor.