Uptime monitoring that confirms a failure before it alerts you
Six monitor types, checks from three locations, response time broken down by phase, and SSL and domain expiry warnings. One-minute checks on Pro and Scale.
Your cron job, worker, or backup script calls a URL when it finishes. If the call does not arrive on time, you are alerted.
Example: nightly-backup
Last ping 4 min ago
A unique ping URL for each job
Expected interval and grace period you set
Alert when a scheduled run is missed
Available on every plan
DNS monitoring
Check that a hostname resolves to the records you expect.
Example: A example.com → 203.0.113.10
Matches expected value
A, AAAA, CNAME, MX, TXT, and NS records
Exact, contains, or regex matching on values
Up to 10 record checks per monitor
Optional custom DNS server
The check results above are examples with sample data.
Confirmed from several locations before anyone is alerted
Checks run from Amsterdam (EU), US West, and Singapore (Asia-Pacific). A failure at one probe is retried from the others, so a bad moment on one network path does not page you.
1A check fails at one probe.
2The failure is retried from the other locations.
3An incident opens only when 3 probes in at least 2 regions have failed.
4Recovery is confirmed the same way.
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
Response Time Breakdown
Composition of latency for uptimeio.com by connection phase (DNS, Connect, TLS, Response)
A slow response can come from DNS, the connection, the TLS handshake, or the server. Each HTTP check records all four separately.
DNS resolution
Time to resolve the hostname
TCP connection
Time to open the connection
TLS handshake
Time to complete the TLS handshake
Server response
Time until the server starts responding (TTFB)
P50, P95, and P99 response times show the slow tail that an average hides.
Five alert channels, on every plan
Email, Slack, Telegram, Pushover, and webhooks are all included on every plan, including Free.
#incidents
Public API is down
Failure confirmed from 3 locations.
Sample notification
Webhook requests can be signed with HMAC-SHA256. There is no SMS or phone-call alerting.
Certificates and domains that expire without warning
Two common causes of avoidable outages, with alerts sent to the channels you already use.
Expiry date
30 days
15 days
7 days
1 day
Illustrative example: a warning is sent to your alert channels at each step.
SSL certificate expiry
Get warned before a certificate expires, and get an incident if it is expired or invalid.
Warnings 30, 15, 7, and 1 days before expiry, sent to your alert channels
An expired or invalid certificate opens an incident
The incident resolves on its own once a valid certificate is seen
Included on every plan
Domain expiry
Get warned before the domain name itself expires.
Registration data looked up over RDAP and re-checked hourly
Warnings 30, 15, 7, and 1 days before expiry
For HTTP, keyword, and DNS monitors on a publicly registered domain
Some country-code domains do not publish an expiry date; these show "not published" and send no warnings
Status pages for your customers
Publish the status of your monitors on a page your customers can check during an incident. Status pages are part of your account, and the Free plan includes one.
Your logo, colors, and text on every plan
Custom domain (status.yourcompany.com) on Pro and Scale
UptimeIO branding removed on Scale
RSS and Atom feeds for subscribers
Incident history and scheduled maintenance notices
90-day uptime display for each component
Password-protected pages on every plan
UptimeIO StatusAll systems operational
Component Status
API Gateway
99.98%
Web Application
99.97%
Customer Dashboard
99.95%
Illustrative example with sample components.
Good to know
Where checks run, who can use them, and how long we keep the results.
Choose where checks run
On Pro and Scale you can choose which locations a monitor uses, down to a single region.
Teams without per-seat pricing
Pro and Scale include team members and projects in the price, with role-based access. The Free plan is for a single owner.
12 months of history
Pro and Scale include 12 months of history for your monitors.