Give each client a page that shows whether their site is up.

If clients often ask whether their site is working, a status page lets them check for themselves.

Why clients keep asking

A client only sees their site when they open it, or when a customer complains. If a customer says the shop was down last night, the client has no way to check. So they email you, and you go through logs to piece together what happened and when.

That costs you time on every question, and it costs some trust too. The client hears about the outage from a customer first, and from you second. A status page fixes the order. The client can see what happened, how long it lasted and that it is over, without waiting for your reply.

One page for each project

Each project can have a public status page. It shows the monitors you choose, whether they are up right now, and recent incidents. It uses the same checks as your alerts, so it is always up to date.

At the top, a banner says whether all systems are operational or some are down. Below it, each monitor shows its current state, when it was last checked, and its uptime over the last 90 days as a percentage. If a monitor has had incidents, they are listed under it with the HTTP status code, when the incident started and how many minutes it lasted. An incident that is still going on is marked as ongoing.

The data on the page refreshes about every minute, so what the client sees is never far behind your own dashboard.

What clients do not see

A status page is public, so Barkme keeps it plain on purpose:

• Monitor URLs are never shown. Each monitor appears under a display name you set, such as "Website" or "Checkout", so internal hostnames and health endpoints stay private.
• You pick the monitors. A staging site or an internal API can be monitored without appearing on the client's page.
• It stays out of search results. Every status page is marked noindex. The client gets the link from you.

Making it look like the client's

Each page has its own title and an optional short description. You can upload the client's logo, set an accent colour to match their brand, and add a support link so visitors can get back to the client's site in one click. Times on the page are shown in your team's timezone, and the footer names the zone.

On the client's domain

Every status page gets an address on a barkme.dev subdomain. On Founder and Pro you can use your own domain instead, such as status.yourclient.com.

The custom domain has to sit under a domain your team has already verified, so status.yourclient.com works once yourclient.com is verified. To connect it, you add two DNS records: a TXT record that proves the domain is yours to use, and a CNAME that points it at Barkme. If you look after the client's DNS already, that is a few minutes of work. If not, you send the client the two records to add.

Setting it up

The order matters, because a status page shows monitors and a monitor needs a verified domain:

1. Verify the client's domain. Add one TXT record on the apex. It usually takes about two minutes, and it covers every subdomain, so the site, the shop and the API are all covered.
2. Create a project for the client and add their monitors to it. Each monitor checks a URL with an HTTP GET on the interval you pick, from 30 seconds to 5 minutes.
3. Create the status page for that project. Pick which monitors appear, rename them for the public view, add the logo and colour.
4. Connect a custom domain if you are on Founder or Pro, then send the link to the client.

The client does not need an account. The page is public at its address.

What a client sees after an outage

Say a client's shop goes down at 22:40 and comes back at 22:58. The next morning, the client hears from a customer that something was wrong. They open status.yourclient.com.

The banner says all systems are operational. Under "Checkout" they see an uptime figure a little below 100% for the last 90 days, and one recent incident: resolved, the HTTP status code it failed with, started at 22:40, lasted 18 minutes. That answers the question. Nobody had to search through logs, and you hear about it only if the client wants to know why it happened.

You heard about it at 22:41, because the same incident sent you an alert. If you want a fuller picture of what an agency setup looks like, see uptime monitoring for web agencies.

Plans

The Free plan includes one status page. Founder and Pro include as many as you need, so you can have one for every client.

The Free page lives on a barkme.dev subdomain and can show the Free plan's three monitors. For client work, Founder ($19/mo) is usually the right fit: 30 monitors across five verified domains, custom domains for every status page, and alerts in Slack or Telegram. Pro ($39/mo) removes the monitor cap, covers up to 50 domains, and adds Linear, Trello and a signed webhook. See the full comparison on the pricing page, or how Barkme compares with Better Stack, which also sells status pages.