Websites
HTTP status, response time and a keyword on the page, so a blank checkout counts as down even when it returns 200.
Learn about website monitoring
Check any website, API or server from two regions (US East and EU Central), and get an email, SMS or Slack alert the minute it goes down.
One account covers the public site, the API behind it, the servers underneath and the jobs that run at night. Every plan includes every check type.
HTTP status, response time and a keyword on the page, so a blank checkout counts as down even when it returns 200.
Learn about website monitoring
Method, headers, body and JSON assertions on every response, with timeouts you set per endpoint.
Learn about API monitoring
Ping and TCP port checks for web, mail, database and SSH services on Linux and Windows servers.
Learn about server monitoring tools
Certificate expiry, chain validity and domain registration dates, with warnings weeks before anything lapses.
Learn about SSL certificate monitoring
Each job pings its own URL when it finishes. When the ping stops arriving, your team hears about it.
Learn about cron job monitoring
A public or password protected page on your own domain, with components, incident updates and subscriber emails.
Learn about the status pageFrom a pasted URL to a working alert in a few minutes. The full walkthrough is on how uptime monitoring works.
Paste the address of a site, an API endpoint, a server hostname or a port. For a scheduled job, UptimePilot gives you a unique heartbeat URL to call when the run ends.
Pick the check type and interval, set the expected status code, a keyword or JSON assertions, and a timeout. Checks run from US East and EU Central.
Send alerts by email, SMS, Slack, Microsoft Teams or webhook. Escalation passes the alert to the next person when nobody responds. Maintenance windows keep planned work quiet.
Show your components on a status page with your logo, colors and domain. Post incident updates, schedule maintenance and let customers subscribe by email.
Alert Slack #ops and email the on-call engineer when 2 regions report down. Escalate by SMS after 5 minutes.
Downtime rarely shows up as one line on a bill. It shows up as orders that never happen, contract credits and a support inbox that fills in minutes.
A store doing $20,000 a day earns about $830 an hour, and more on a sale day. One hour of checkout downtime costs more than a full year of the Starter or Team plan.
Enterprise contracts often promise 99.9% uptime, which allows about 43.8 minutes of downtime a month. Miss it and the credit comes out of revenue you already counted.
When customers cannot tell whether you know about a problem, they write in. A status page with incident updates answers the question once, for everyone.
Enter what your site earns in a day and compare what 99%, 99.9% and 99.99% uptime allow in a month.
Figures assume revenue is spread evenly across the day. On sale days and launches the real loss is higher.
Downtime a month
43.8 minutes
Revenue at risk a month
$609
Every month you need one number for clients and leadership. UptimePilot measures uptime percent, response time percentiles and every incident. Team plans export a monthly SLA PDF. See what the uptime monitoring service reports include.
Every plan includes every check type, multi-region confirmation and all alert channels. Plans differ by monitors, interval, status pages and reports.
$49 per month billed monthly
$24 per month billed yearly ($288 per year)
For a solo developer or a small store that wants every check type and a clean status page.
$99 per month billed monthly
$49 per month billed yearly ($588 per year)
For a SaaS team that needs fast checks, a branded status page and an uptime number for contracts.
$249 per month billed monthly
$124 per month billed yearly ($1,488 per year)
For an agency or MSP that monitors many client sites and sends each client a report.
$599 per month billed monthly
$299 per month billed yearly ($3,588 per year)
For a larger company or regulated team that needs single sign-on and a full audit trail.
A monitor is marked down only after a second region confirms the failure. A single slow route or a brief network blip in one region does not wake anyone up. Read more in our guide to reduce false alarms in uptime monitoring.
Checks run from two regions, US East and EU Central. Each result is labeled with the region that produced it, so you always know where a failure was seen.
Starter includes 30 SMS alerts per month, Team 150, Business 500 and Enterprise 1,500. Email, Slack, Microsoft Teams and webhook alerts have no monthly cap.
Yes, from the Team plan. Point a subdomain such as status.yourcompany.com at your page and UptimePilot serves it there. See the status page for components, incidents and subscriber emails.
Starter keeps 90 days of history, Team 1 year, Business 2 years and Enterprise 3 years. Reports and the incident log cover the full retention period of your plan.
Yes. You cancel from your account and the plan stays active until the end of the period you paid for. Payments are final, as described in the refund policy.
Your cron job or worker calls a unique URL each time it finishes. You set the expected schedule and a grace period, and when the call does not arrive in time, UptimePilot alerts your team. Details are on the cron job monitoring page.
Your existing monitors keep running. When you use up the monthly SMS alerts, alerts continue by email, Slack, Microsoft Teams and webhook. To add more monitors or SMS, upgrade from your account at any time.
Enter a URL and see status code, response time, certificate and domain expiry in a few seconds. Then keep it monitored every minute.
Save this check and start monitoring it every minute from two regions.