Skip to content

Five check types, confirmed outages, one history.

Uptime monitoring

Uptimo checks not only whether a service answers but what it answers. Every monitor carries an interval, a timeout, an expected status code and optionally a string that must appear in the response — an error page served with status 200 does not pass as healthy.

Check types
HTTP · Ping · TCP · DNS · TLS
Intervals
from 10 seconds
Incidents
per monitor and location
One monitor's response times, split by checking location — straight from the product.
One monitor's response times, split by checking location — straight from the product.

What matters here

HTTP and HTTPS

Status code, response time, redirects and a required string in the body.

Ping (ICMP)

Reachability and latency for hosts, routers and anything with an IP.

TCP port

Database, mail server or your own service: does the port answer at all?

DNS

Resolution and zone availability, before customers see an empty page.

TLS certificates

Expiry and chain, so no certificate lapses unnoticed.

Confirmed outages

Down only after several consecutive failures — a single blip wakes nobody.

FAQ

Common questions about Uptime monitoring

Which check types are available?

HTTP and HTTPS, ICMP ping, TCP port, DNS and TLS certificates.

How does Uptimo prevent false alerts?

Uptimo confirms an incident only after several consecutive failures. A single blip remains one failed check.

Can an HTTP check catch false success pages?

You can require both a status code and a string in the response body, so an error page served as HTTP 200 still fails.

Test it with your own system.

A first monitor shows you the flow without example data.

Start for free