Uptime monitoring for web agencies
An agency’s reputation is built on the sites it looks after. When a client’s shop goes down on a Friday evening, it does not matter whose hosting failed. What matters is whether you knew first and had an answer ready. Our article on uptime monitoring for web agencies goes deeper.
One project per client
Group each client’s monitors, cron jobs, domains, servers and status pages in a project. Lists filter by project, and the project’s color marks its monitors everywhere, so fifty client sites stay easy to read. Invite colleagues as admins, members or viewers.
Client dashboards and client reports
On Professional and Business, invite people at the client to a client dashboard: a read-only login to their project, in your name, with current status, 90 days of uptime, response times, incidents and the monthly report. They never see other clients, settings or alert channels.
Clients who do not want another login get a client report instead: a private link to a live uptime report with their logo, the SLA and every incident. Add up to 5 addresses and last month’s report is emailed on the 1st. Reports also export to CSV for your own template.
A status page per client
Give every client their own status page with their logo, accent color and theme, and remove the Uptimecheck branding so it looks like part of your service. Professional and Business add custom CSS and an address you choose, such as app.uptimecheck.com/s/clientname. Password-protect pages meant for internal stakeholders.
Visitor statistics show visits by country, referrer and device, counted without cookies and without storing IP addresses, so you can show the client how many of their customers checked the page during an incident.
More than uptime for every client
Watch the things clients notice too late: certificates and domain registrations before they expire, page speed with Google Lighthouse, broken links, and SPF, DKIM and DMARC, so the client’s email does not land in spam.
Alerts go to email, Slack, Microsoft Teams, Discord, Google Chat, Mattermost, Telegram, PagerDuty, ntfy, Pushover, webhooks and push notifications on your phone. Send each client’s alerts to its own channel, and use on-call schedules so a push alert reaches whoever is on call.
A typical week with Uptimecheck
Monday, a reminder says a client’s certificate expires in 14 days; it is renewed before lunch. Wednesday, a cron job for another client’s nightly export goes missing; the hosting provider changed the PHP version, and the job is fixed the same morning. Friday at 18:40, a client shop answers 503. A second check confirms it, the Slack alert goes out, and the incident already holds the failing response and a screenshot. The client’s status page shows the problem before they think to call. On the 1st, every client gets last month’s report by email.
None of that needs a dedicated operations team. It needs the checks in place and the alerts going to the right person. Add each new client in a few minutes, or script onboarding with the REST API as your client list grows.
Moving from another tool
Import monitors from UptimeRobot, Better Stack, Pingdom or StatusCake with an API key from that service. You see every monitor before anything is created, and nothing changes at the other service, so you can run both side by side. Status pages come over from Atlassian Statuspage with their incident history and subscribers. The UptimeRobot, Better Stack, Pingdom and StatusCake pages explain each switch.
Pricing that suits agencies
A fixed price per plan in euros, billed monthly or yearly, without per-seat fees or a charge per status page. Professional includes 100 uptime monitors, 25 status pages, 50 projects, 10 members and client dashboards. Business includes 250 monitors, 250 status pages, 150 projects and 25 members. See the pricing page, or click around Nordhem, a made-up shop, in the live demo.