Find out when your site goes down and where the delay starts

Free uptime monitoring for websites, APIs and cron jobs. We check from multiple locations and only alert you when the failure is confirmed.

50 free monitors · No credit card required

  • Monitor
  • Confirm
  • Diagnose
  • Alert

Production

Checked from multiple locations

Public API · response time

130ms

DNS
8 ms
TCP
20 ms
TLS
35 ms
Server
68 ms
P50
134 ms
P95
150 ms
P99
162 ms

Sample data

Uptime monitoring, alerts and status pages in one place

One account for uptime checks, response-time diagnostics, alerts and public status pages.

Monitor

Checks run from multiple locations. Every minute on Pro and every 30 seconds on Scale, every five minutes on Free.

Diagnose

DNS, TCP, TLS and server time are recorded separately for each HTTP check, with P50, P95 and P99. Up to 12 months of history on Pro and Scale.

Alert

Email, Slack, Telegram, Pushover and webhooks on every plan, chosen per monitor. Recovery is confirmed before you are told.

Publish

Public status pages live in the same account: 1 on Free, 20 on Pro, 100 on Scale, with custom domains on Pro and Scale.

Use it from Claude Code, Cursor and other AI assistants with the UptimeIO MCP server.

Monitor anything with an address.

Six monitor types, all included on every plan.

HTTP/S

Check a URL for the status code you expect. Custom headers, Basic auth and Bearer tokens are supported.

Keyword

Fetch a page and confirm the text you expect is in the response, not just that the server answered.

TCP

Open a connection to a host and port, such as a database or mail server, and time the handshake.

DNS

Verify that a DNS record still resolves to the value you expect, so a bad change is caught fast.

Ping

Check that a host is reachable at all, for servers and devices that do not speak HTTP.

Heartbeat

For cron jobs and workers: get alerted when an expected check-in does not arrive.

HTTP checks also warn you before SSL certificates and domains expire, at 30, 15, 7 and 1 days. Domain expiry warnings are on Pro and Scale.

Several locations must agree before anyone gets paged.

A monitor that checks from one place pages you when that one network path has a bad moment. UptimeIO retries failures from other locations and opens an incident only after three probes in at least two regions have failed.

GET https://api.example.com/health

Every minute

Location A

HTTP 500 · 450 ms

Failed

Location B

HTTP 500 · 416 ms

Failed

Location C

HTTP 500 · 410 ms

Failed

Incident opened

3 of 3 probes failed across 3 regions, so your team is paged.

Illustrative example with sample data

3 probes · 2+ regions
must agree before an incident opens
Every attempt recorded
so you can see why an incident was raised
Recovery confirmed
the same way the failure was

Alerts land where your team already looks.

Email, Slack, Telegram, Pushover and webhooks are included on every plan, including Free.

#incidents

Public API is down

Failure confirmed from multiple locations.

Sample notification

Frequently asked questions

Short answers about how UptimeIO monitors and alerts

Start free uptime monitoring in a few minutes

Start monitoring free

Free plan · 50 monitors · No credit card required