Top-grade monitoring for servers, backups and staff
Choose the type that matches what you want to watch.
| Type | Best for | Needs URL? | How it runs |
|---|---|---|---|
| Is the website up? | Simple reachability check | Yes | Automatic on a schedule |
| Check page text (GET) | Fetch a page and optionally look for text | Yes | Automatic |
| Call with POST | Call a URL with a POST | Yes | Automatic |
| Did the page content change? | Detect when page content changes | Yes | Automatic |
| Status by email | A system emails Uptime10 with status | No | Push (you send mail) |
| Status by API | A script reports status over HTTP | No | Push (you call the API) |
Simplest option. Uptime10 contacts the URL and records whether it succeeded.
Fetches the URL with GET. You can add:
Same idea as GET, but uses HTTP POST. Use when the target expects a POST.
Uptime10 downloads the page and compares it to a stored copy.
These do not poll a URL. Something else (backup software, cron job, device) must report in.
For URL checks, interval is how often Uptime10 checks (from every 30 seconds to every 24 hours; default every 5 minutes). Email and API ignore the interval — they update when a message or API call arrives.
For URL checks, timeout is how long each HTTP probe may wait: Fast, Typical (default), Slow, or Very slow. Email and API ignore timeout.
If a poll gets no HTTP response (connection dropped), Uptime10 retries once before treating that check as failed, so brief network blips are less likely to create false Error events.
A poll monitor is marked Down only after it keeps failing for about 90 seconds while still Up. Short flaps (for example a one-minute connection drop) stay Up and do not create an Events row or alert.