Uptime monitoring for web agencies
One account for every client site, a monitor per site plus one for each checkout or login that matters, a status page per client, and a weekly summary you can forward as proof the retainer is doing something. The Business plan covers 200 monitors and 20 status pages for $29 a month.
The problem with finding out from the client
An agency with 40 client sites has 40 ways to get a Monday-morning email that starts with "the site's been down since Saturday". Hosting dashboards don't tell you; the client's own analytics tell them, a week later. Monitoring from outside, every 30 to 60 seconds, is how you get the message first and reply with "already on it".
Every failure is confirmed by a second check before anyone is alerted, so a single slow response doesn't wake you up. When something is really down, the alert names the likely cause: a 503 from the host, an expired certificate, a DNS record that changed, a timeout. That's usually enough to know whether to call the host or open the code.
What to monitor
Plan on two to four monitors per client: the home page, the one page that makes them money, and the certificate and domain. The table shows a typical set for a client with a WordPress site and a contact form.
| Page / URL | Check | Why |
|---|---|---|
| Client home page | Status 200, every 60 s | The basic "is it up" check; the one the client cares about. |
| Key page (shop, booking, contact) | Status 200 and contains a phrase from the form or button | A page that loads but lost its form is still an outage to the client. |
| Staging site | Status 200, every 5 min, alerts to the dev channel only | Catches a broken staging deploy before the client's review call. |
| Certificate (automatic) | Reminders at 14, 7, 3 and 1 days before expiry | Let's Encrypt renewals fail quietly; this is the usual Friday-night emergency. |
| Domain (automatic) | Reminders at 30, 14, 7 and 1 days; DNS change alerts | Clients forget renewals; registrars' emails go to old addresses. |
| Nightly backup script | Heartbeat: expects a ping every day, 1 hour grace | A backup that stopped running is worse than no backup, because everyone thinks there is one. |
Which plan, in monitor counts
In short: Starter (10 monitors) for up to 3 clients, Pro (50) for 10 to 15, Business (200 monitors, 20 status pages) for 40 to 60 clients.
Starter is $5.99 a month with 10 monitors, 60-second checks and one status page. Pro is $29 with 50 monitors, 30-second checks and five status pages. Business is $59 with 200 monitors, 30-second checks and 20 status pages. Every plan includes every alert channel, including webhooks for when alerts should land in your own ticketing system, and yearly billing is cheaper ($39.99, $299 and $599 a year).
At three monitors per client, Business covers about 65 clients for less than most agencies charge one client per month for "hosting and maintenance".
A status page per client
Each status page is its own public page with its own name and components, so you can give Acme Dental a page with Website and Booking on it, and Riverside Law a page with Website and Client portal, without either seeing the other. Clients can subscribe by email and get the outage notice and the all-clear without you writing either.
Pro includes five status pages, Business includes twenty. Give them to the clients who ask "was the site down?" most often; everyone else gets the weekly summary.
Deploys, maintenance windows and the weekly summary
- Schedule a maintenance window before a deploy or a hosting migration. Checks keep running and are recorded, but nothing is alerted, and the status page shows planned maintenance instead of an outage.
- The weekly summary email lists uptime and average response time for every monitor. Forward it, or paste the numbers into the monthly client report; it's the simplest proof that the retainer includes monitoring.
- Alert channels per monitor: route the client's checkout to the on-duty Slack channel and staging sites to a quieter one. Every channel (Email, Slack, Discord, Microsoft Teams, Telegram and webhooks) is on every plan.
Questions
How many monitors do I need per client site?
Two to four: the home page, one key page with a text rule, and the automatic certificate and domain reminders that come with the site's monitor. Add a heartbeat for any nightly backup or sync job you're responsible for.
Can clients see their own uptime without logging in?
Yes, through a public status page. Each page has its own name and components, shows 90 days of history, and lets the client subscribe to outage and all-clear emails.
Will deploys trigger alerts?
Not inside a maintenance window. Schedule one for the deploy and the checks are recorded but not alerted. If a deploy breaks the site after the window ends, you're told the normal way.
Can heyUptime send alerts to our ticketing system?
Yes, on every plan, through webhooks: each alert is posted as JSON to a URL you choose. Every plan also alerts by email, Slack, Discord, Microsoft Teams and Telegram.
See it on your own site.
heyUptime checks every 30 seconds, confirms before alerting, and tells you why it's down in plain words. Free for 14 days, no card.
Related
- Uptime monitoring for freelancers
- Uptime monitoring for WordPress sites
- Status page example
- Cron job monitoring
- Pricing
- Uptime monitoring for online shops
- Uptime monitoring for SaaS and startups
- Uptime monitoring for WordPress sites
- Uptime monitoring for Shopify stores
- Uptime monitoring for freelancers and small studios
- Uptime monitoring for side projects and indie developers
Updated October 8, 2026.