Guide

Status Pages for Hosting Providers: What to Show Customers

A public status page cuts the tickets that arrive during an outage. What a hosting provider should show on one, what to keep private, and how to keep it honest.

By Frabs · 15 November 2026 · 3 min read

The short answer: a hosting status page should show whether each service or location is up, a timeline of past outages and how long each lasted, and short updates while something is wrong. It should not show server addresses, internal hostnames or the technical cause, which belong in your own tools.

When something goes down, customers want to know two things: is it them or you, and is someone on it. A status page answers both before they open a ticket.

Why It Is Worth Having

  • Fewer tickets during an outage. Customers who can see the problem is known tend to wait rather than write in, which leaves your team free to fix it.
  • Trust over time. A record of past outages, including the short ones, shows customers you are not hiding anything.
  • A single place to send people. Support replies, social posts and emails can all link to the same page.

What to Show

Status per service or location. Group what customers buy in a way they recognise: a data centre, a product line or a region. Most customers do not know which node they are on, and do not need to.

An up and down timeline. Days or weeks of history, with each outage and how long it lasted. A page that only ever shows green looks broken, or worse.

Uptime over a period. A percentage over 24 hours, 7 days and 30 days is easy to read and easy to compare.

Updates while it is happening. Short, plain notes: what is affected, that you are working on it, and when you will update again.

What to Keep Private

Server addresses and hostnames. An address on a public page is an address someone can attack while you are already having a bad day.

The exact cause during the outage. "A kernel crash on node 4 after a memory leak in a driver" helps your team, not your customers, and can change as you learn more. Say what is affected and that it is being fixed. Explain the cause afterwards, once you are sure.

Other customers. Never name a customer, even when one customer's VPS caused the trouble.

Keep It Honest

A status page only works if customers believe it. Two rules help:

  1. Record real downtime only. If your monitoring lost contact but the server was fine, that is not an outage, and showing it as one teaches customers to ignore the page.
  2. Do not hide short outages. A two-minute drop that customers noticed should be on the page. If it is missing, they will trust the next update less.

Status Pages in Frabs

Frabs Host and Frabs Hypervisor include uptime monitoring and public status pages. Each server reports every minute, and you can give customers a page at uptime.frabs.net with your company's name. It shows the up and down timeline and where each server is, and never the reasons for an outage or any address.

Behind it, your control panel keeps the full story: uptime over 24 hours, 7 days and 30 days, every outage with why it happened, and the server's own logs from just before. Frabs only shows downtime it can prove, so a pause in reporting is never shown to customers as an outage.

Frequently Asked Questions

What should a hosting status page show?

Whether each service or location is up, a timeline of past outages with how long each lasted, uptime over a period, and short updates while something is wrong.

Should a status page show server IP addresses?

No. Addresses and internal hostnames on a public page help attackers. Group status by service, product or location instead.

Should I show the cause of an outage on the status page?

Say what is affected and that it is being fixed. Keep the technical cause for your team, and explain it afterwards once you are sure.

Does Frabs include status pages?

Yes, on Frabs Host and Frabs Hypervisor. Customers get a page at uptime.frabs.net with the up and down timeline and server locations, never the reasons or addresses.

Earn 30% recommending Frabs

Share your own code. Your customers get 20% off their first month, and you earn 30% of every payment for them, for as long as they keep them. Paid by PayPal.

Become an Affiliate

Start with One Server, Free