Website & infrastructure
monitoring.

Track availability, response times and certificates. See each check, investigate changes, and choose where alerts go.

Hosted checks. No agent required for public targets.

Your services, check by check.Try a real check

Check a website now

Runs one HTTP check from our server and shows the status code, response time and certificate expiry.

Public probes2
Check interval5 min
Metric retention90 days
Availability, history and alerts in one workspace.
HTTP(S)SSL certificatePingTCP portDNS

See what a check actually measures.

A reachable server does not always mean a working service. Use different sensors for your website, network and certificates.

SensorWhat you can monitorCounts as failed when
HTTP(S)Status code and response time, plus optional text the page must or must not contain. Follows up to 5 redirects.The status is outside the expected range, the text check fails, or nothing answers before the timeout.
SSL certificateDays until the certificate expires, whether the chain is valid and whether it matches the hostname.The certificate is invalid or expires within your error threshold. The warning threshold gives notice first.
PingRound-trip time and packet loss over several ICMP packets.Every packet is lost. Partial loss is a warning.
TCP portWhether a TCP port accepts a connection, and how long it takes.The connection is refused or times out.
DNSThe answer to an A, AAAA, CNAME, MX, TXT or NS lookup from a public resolver.The lookup fails or the answer does not contain the expected value.
SMTPThe SMTP greeting on port 25 or the port you set.There is no greeting, or it is not an SMTP greeting.
IMAPThe IMAP greeting, over TLS on port 993 by default.There is no greeting, or it is not an IMAP greeting.

Two checks. One confirmed incident.

One failed public probe produces a warning. A sensor is marked down only when both public probes report failure for the same check window.

Review the evidence and send alerts to email, Slack, Telegram, Discord or a webhook.

Configure alert channels
Public check confirmation

Down when both probes fail

First public probeReports a failed check · Warning until confirmed
Second public probeReports a failed check · Down when both probes fail

Recovery requires a successful result from each probe.

Start with a small monitoring setup.

Organize your devices and add a sensor for each thing you want to check. Your sensor allowance and check interval are shown before you select a plan.

Paid plans use a prepaid USD balance. Manage your plan, payments and account balance in the same workspace.

View all plans

Free

Starting plan
$0 / month
Sensors10
Check interval5 min
Public probes2
Metric retention90 days
Create account

A few practical questions.

Where do the checks come from?

From our public probes in Istanbul. Their addresses are on the Probe IPs page, so you can allow them through a firewall.

How often can a sensor be checked?

As often as every 5 min, depending on your plan.

How long are results kept?

90 days of results for every sensor.

Can I monitor servers that are not reachable from the internet?

Not from the public probes: they refuse private and reserved addresses. Checks inside your own network need a private probe, which is not available to customers yet.

How does payment work?

You keep a prepaid balance in US dollars and the plan price is taken from it each month. Accepted: card, crypto, PayPal.

What happens when my balance runs out?

At renewal the account moves to the free plan. Sensors above the free plan's limit are paused, not deleted, and can be resumed after a top-up.