Know when your service is down
and where the delay starts
Uptime monitoring that checks your endpoints from multiple regions, confirms failures before alerting, and shows where response time is spent.
50 free monitors · No credit card required
- Monitor
- Confirm
- Diagnose
- Alert
Production
Amsterdam · US West · Singapore
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
Monitor it. Diagnose it. Get told. Show everyone.
One account for uptime checks, response-time diagnostics, alerts and public status pages.
Monitor
Checks run from Amsterdam, US West and Singapore. Every minute on Pro and 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.
Monitor anything with an address.
Six monitor types, and pricing depends only on how many monitors you run.
HTTP/S
Check a URL for the status code you expect. Custom headers, Basic and Digest auth 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.
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 60 s
Amsterdam
HTTP 500 · 450 ms
Failed
US West
HTTP 500 · 416 ms
Failed
Singapore
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.
Public API is down
Failure confirmed from 3 locations.
Sample notification
Start monitoring in a few minutes
Free plan · 50 monitors · No credit card required