Status pages for MSPs
Keep a public status page for each managed client, and let HTTPS checks open and resolve incidents on that page. One Agency plan is $19 a month after a 14-day trial.
Signup does not ask for a card. This page does not collect a card.
A page for each managed client
The account holds up to 10 status pages. Put each client on their own page so a subscriber for one client does not get another client’s incidents. A custom domain, when you add one, is a subdomain such as status.client.com. The page at that hostname is the client’s status page, not this marketing site.
Monitors that write the incident
An account can have 20 monitors. A monitor belongs to one page and, if you choose, one component on that page. It requests an HTTPS URL with GET or HEAD every 1, 5, or 10 minutes. After 3 failed checks, the default, it opens an incident. After 2 passing checks, the default, it resolves that incident. If someone already resolved it, the monitor does not post another update. Those writes use the same path as an incident you post by hand, so Slack, webhooks, and subscriber email still send.
The checker refuses private, loopback, link-local, and metadata addresses, and it does not follow a redirect onto those hosts. Checks older than 90 days are deleted. A published page shows 30-day and 90-day uptime for a component that has monitor checks. A window with no checks is blank. In the editor, each monitor also shows 24-hour and 30-day uptime from its own checks.
History and a printable report
The public page lists active incidents, incidents resolved in the last 14 days, and maintenance windows that have not ended. Past incidents, linked from that page, lists resolved incidents and completed maintenance from the last 90 days. Confirmed subscribers can receive maintenance email. That message is not phrased as an incident.
The signed-in owner can open a client report for one page. It shows the 90-day history and a table of 30-day and 90-day uptime. Print uses the browser print dialog.
When one outage hits several clients
Post the incident once to several pages with POST /v1/incident-groups. Each page still has its own incident record, so a client’s subscribers and Slack channel only see their page. The API uses an account key. Another account’s page is a 404. Details are in the docs.
Limits that matter for an MSP
- 10 status pages and 20 monitors per account.
- No SMS, phone-call alerts, or on-call schedules.
- No single sign-on and no private status page.
- Monitor intervals are 1, 5, or 10 minutes, not 30 seconds.
If you need those, the comparison pages quote what Instatus, Better Stack, Status.io, Statuspal, and UptimeRobot list. Read their pricing pages before you treat a figure here as current.
Questions
Can one MSP account cover several clients?
Yes. The Agency plan is $19 per month after a 14-day trial and includes up to 10 status pages. Each page has its own components, incidents, subscribers, and optional custom domain.
Do monitors open incidents by themselves?
Yes. After repeated failed HTTPS checks, the monitor opens an incident on its page. Later successful checks can resolve that incident. An account can have 20 monitors.
Can I tell several clients about the same outage?
Yes. POST /v1/incident-groups creates one incident on each page you name. Subscribers on a page only get that page’s mail.
What does a client’s public page keep?
Active incidents, incidents resolved in the last 14 days, and maintenance that has not ended. Past incidents lists resolved incidents and completed maintenance from the last 90 days. Components with monitor checks show 30-day and 90-day uptime.
Is the client report included?
Yes. The signed-in owner opens it for one page. It shows 30-day and 90-day uptime and the 90-day history. Print uses the browser print dialog.
Related: status pages for agencies, what the client’s page shows, and pricing.