for agencies, msps & freelancers
Uptime monitoring for agencies: monitor every client website from one dashboard
Agencies need uptime monitoring that covers a whole book of client sites without the bill growing every time they sign a new retainer. AlertPing watches 100 client websites for $59 a month flat, checks each one every 30 seconds, and confirms every outage from three regions before it pages anyone. You find out a client site is down before the client does, and you get a branded status page and SLA report to prove the care plan is worth what you charge.
Last updated July 2026
100 monitors on Team | SMS included, no credits | status page per client
alertping ▸ run check
live
▸ type a domain and run a real-feel check
▸ probes from 3 regions · FRA · IAD · SIN
▸ waiting…▌
queued probing▌
If ever goes down, you get:
Alert fired ▸ 2 channels · 6.2 s after first failure
AlertPing app
● DOWN : HTTP timeout confirmed from 3/3 regions (FRA, IAD, SIN). Incident opened.
sms · on-call
AlertPing: DOWN. Confirmed 3/3 regions . First fail: Frankfurt.
the call you never want
Your client should never be the one who tells you
It is 9:12 on a Tuesday. A client emails you a phone screenshot of a 502 on their homepage with the subject line “is this normal?” You did not know. Their host did not tell you, because from the host's point of view the box is fine. The plugin update that ran overnight took the site down at 3:40am, and it has been down for five and a half hours.
That email costs more than the outage did. Every month after it, the client reads the care plan line on your invoice and quietly asks what they are paying for.
failure 01
The host says the server is up
Managed hosts monitor their infrastructure, not your client's site. A fatal PHP error, a bad deploy or a dead DNS record leaves every host dashboard green while the homepage serves a stack trace.
failure 02
The page returns 200 and shows nothing
A WordPress white screen of death often answers with a clean 200. A status-code-only checker calls that healthy. Your client calls it down, and they are the ones who are right.
failure 03
The certificate expired on a Sunday
An expired TLS certificate takes a client site offline behind a full-page browser warning. It is the most preventable outage there is, and it happens because nobody owns the renewal calendar for 60 domains.
failure 04
The tool that cried wolf
Get paged three times at 3am for routing blips that fix themselves and you will mute the app. Then the real outage arrives and nobody is listening. Alert fatigue is how agencies end up with no monitoring at all.
what a client fleet needs
Six things that matter when you monitor client websites
Monitoring one site is easy. Monitoring 40 sites you did not all build, on hosts you did not all pick, is a different job.
01 · one screen
Every client site on one dashboard
Group monitors by client, tag them by host or stack, and see the whole book in one view. Our website monitoring tool checks every 30 seconds on Team and Business, 60 seconds on Starter, so a four-minute outage cannot slip between probes. Nothing gets installed on a client's server, which matters when you do not have root on half of them.
02 · no 3am false alarms
3 of 3 regions, or silence
A failed probe triggers instant re-checks from Frankfurt, Virginia and Singapore. All three must agree before an alert fires. One flaky route on one network never wakes you up, so your team keeps trusting the pager.
03 · white screens
Keyword and JSON assertions
Assert that the homepage still contains the client's tagline, or that a Shopify product page still renders “Add to cart”. A 200 with a blank body fails the check the way a human would judge it.
04 · certificates
SSL expiry across the book
SSL certificate monitoring watches expiry and chain validity on every client domain and warns you 30, 14, 7 and 1 day out. The renewal calendar stops living in someone's head.
05 · silent failures
Cron heartbeats for backups
A backup that stopped running six weeks ago is the outage you find out about during a restore. Cron job monitoring expects a heartbeat and pages you when it does not arrive, including a stalled WP-Cron.
06 · the right human
Escalation per client
Downtime alerts by SMS, email, Slack and webhook in under 10 seconds. Escalation chains and on-call hours route each client to the developer who owns that account, not to everyone.
the resale math
What multi site uptime monitoring actually costs you per client
Per-monitor pricing punishes the exact thing you are trying to do, which is grow the number of sites you look after. AlertPing plans are flat. Here is the honest arithmetic, and where the cost usually lands on your own invoice.
| Plan | Monitors | Cost per monitored site | Where it fits in your billing |
|---|---|---|---|
| Starter $19/mo $15 billed yearly |
20 monitors 60 s checks |
$0.95 at 20 sites |
A freelancer with 15 to 20 retainer sites. One monitor per site, one status page, SMS included. Usually absorbed into an existing retainer without a line item. |
| Team $59/mo $47 billed yearly |
100 monitors 30 s checks |
$0.59 at 100 sites |
The agency plan. 100 monitors covers roughly 50 clients at two checks each (homepage plus SSL or a cron heartbeat). Monitoring rides inside a monthly care plan, which agencies commonly bill at $30 to $100 per client. |
| Business $189/mo $151 billed yearly |
500 monitors 30 s checks |
$0.38 at 500 sites |
MSPs and agencies past 100 client sites. Adds SLA reports, the API for provisioning, and status pages on a custom domain. The tier where monitoring becomes a product you sell rather than a cost you absorb. |
Per-site figures are the plan price divided by the plan's monitor ceiling, so they are the best case, not a promise. Fill half the plan and you pay double per site, and the plan price still does not move. Full details on the uptime monitoring pricing page. Need the box behind the site too? See the server monitoring tool.
how it works
From empty account to a monitored client book
An afternoon for the first pass, about 90 seconds per client after that, and no credentials you were never given.
-
1
Add the client sites
Paste the URLs and group them by client. For each site, an HTTP check with a keyword assertion on the homepage plus SSL expiry on the domain. On Business, the API creates the monitors inside your provisioning flow, so a new site is watched the day it launches.
-
2
Set escalation per client
Route each client's alerts to the developer who owns that account, with a backup contact and on-call hours behind them. SMS first for the ecommerce clients, Slack for the brochure sites. SMS is included in every plan, so a bad month never produces a surprise line item.
-
3
Publish a status page per client
Every plan hosts branded status pages that update themselves from your checks. On Business you can point one at the client's own domain. During an incident the client refreshes a page instead of calling you every four minutes.
-
4
Send the monthly SLA report
On Business, SLA reports give you uptime per endpoint per month, exportable, ready to attach to the invoice. “99.98% uptime, two incidents, both resolved inside nine minutes” is the sentence that renews a retainer without a meeting.
who runs it this way
Monitoring for a web design agency, an MSP, or a one-person shop
wordpress care plans
The care plan you can actually defend
Updates, backups and monitoring is the standard care-plan bundle, and monitoring is the only part the client ever sees working. A keyword assertion catches the white screen a plugin update caused. A cron heartbeat catches the backup that quietly stopped six weeks ago.
shopify & ecommerce
Stores where a down hour has a dollar figure
Monitor the homepage, a product page and the checkout path separately, each with its own assertion. When a theme deploy breaks the cart button but the page still returns 200, you know in under a minute instead of hearing it from the client's Monday sales report.
msp client fleets
Hundreds of endpoints, one escalation policy
Sites, mail servers, VPN endpoints and exposed ports across a client fleet, checked from outside the network the way the client's own staff reach them. Business covers 500 monitors, the API, SLA reports and status pages on client domains.
freelance retainers
One person, 20 sites, no on-call team
You are the whole escalation chain, which is exactly why false alarms are unaffordable. 3-of-3 confirmation means the phone only buzzes when a site is genuinely gone. Starter covers 20 monitors for $19 a month, which one small retainer pays for.
asked before buying
Client website monitoring, answered straight
How do agencies monitor client websites?
Agencies add every client site as an external monitor in one shared account, grouped by client. Each site gets an HTTP check with a keyword assertion plus SSL expiry, checked from multiple regions every 30 to 60 seconds. Alerts route by escalation chain to the developer who owns that account, and a branded status page keeps the client informed during incidents.
What is white label uptime monitoring?
White label uptime monitoring means the client sees your brand, not the vendor's. In practice that is a status page carrying your logo and colors, on your domain or the client's, plus reports you send under your name. AlertPing does this on every plan, with custom domains from Business up. It is not a reseller platform with per-client logins.
How much does it cost to monitor 100 websites?
With AlertPing, $59 a month on the Team plan, or $47 a month billed yearly. That is 100 monitors at a flat price, which works out to $0.59 per monitored site per month, with SMS, email, Slack and webhook alerts included. Tools that price per monitor typically charge several times that once you pass 50 sites.
Can I put a status page on my client's domain?
Yes, on Business and Enterprise. Point a CNAME such as status.clientdomain.com at your AlertPing status page and it serves on the client's own domain with your branding. Every plan, including Starter, hosts branded status pages on an AlertPing address, so you can publish one for a client on day one.
before you commit
Three more questions agencies ask
Want to see what a client would see? Run a real check on a live site in the interactive demo before you pay anything.
Can my client log in and see only their own site?
Not today. AlertPing gives your team a shared account with grouped monitors, and gives each client a branded status page, optionally on their own domain. Per-client logins with isolated dashboards are a reseller feature we do not offer, so if that is a hard requirement we are the wrong tool.
Does this replace the monitoring in my hosting or APM stack?
It replaces neither. AlertPing is external monitoring: it checks client sites from Frankfurt, Virginia and Singapore the way a real visitor does, and tells you when one is unreachable or broken. There is no server agent, so it will not profile a slow query. Most agencies run both.
What happens when I take on ten new clients next quarter?
Nothing on the invoice. Plans are flat: Team is $59 a month whether you run 30 monitors or all 100. You only pay more when you cross a plan ceiling, and moving up to Business brings 500 monitors, SLA reports and the API with it.
Know a client site is down before the client does
100 client websites for $59 a month flat. 30-second checks, 3-region confirmation, SMS included, a branded status page per client.