Create a status page
A public page your customers can look at instead of emailing to ask.
A status page shows which of your services are healthy, and carries your incidents and their updates. It is the cheapest support tool you will ever set up: during an outage, the question "is it just me?" arrives from everyone at once, and a page answers it once.
Creating one
Status pages → New, then:
| Field | Notes |
|---|---|
| Name | The heading on the page. |
| Handle / slug | The address. Pick it carefully; see below. |
| Public | Whether anyone with the link can see it. |
| Brand colour | A hex colour for headings and accents. |
| Logo URL | A link to an image you host. |
The logo is referenced by URL rather than uploaded, so it must be publicly reachable — and worth putting somewhere that will not be taken down by the same outage the page is reporting.
Components
A component is one line on the page: "API", "Website", "Dashboard". Each is backed by one or more monitors, and its state comes from them.
Name them after things your customers recognise. "API" means something to them; "nginx-ingress-prod-2" does not, and publishing your internal topology on a public page is its own small problem.
Group related monitors into one component. If you have four monitors on the same API, one component called "API" is more useful than four lines that all go red together.
How the status is worked out
Per component, from its monitors:
- Operational — everything up.
- Degraded — some up, some down.
- Major outage — everything down.
The overall status at the top is the worst of the components.
The 90-day history shows a bar per day, built from that day's check results.
Public or private
A public page is reachable by anyone with the link. A private one is not published.
Note what public means: the component names, the incidents and their updates are visible to the world, including search engines. Write updates with that reader in mind.
Incidents on the page
Automatic incidents appear with their monitor and duration. Manual incidents — which is what you want during a real event — appear with every update you post, timestamped.
A status page that only ever shows red and green is treated as a formality. One with "02:15 — identified, failover in progress" is the thing that stops the support queue filling. See how incidents work.
Plan limits
How many status pages you can have depends on your plan:
| Plan | Monitors | Extra regions | Status pages | Team members | Servers |
|---|---|---|---|---|---|
| Free | 20 | None | 1 | 1 | Not included |
| Starter | 50 | 2 | 3 | Unlimited | Not included |
| Pro | 150 | 9 | Unlimited | Unlimited | Not included |
| Business | 400 | 9 | Unlimited | Unlimited | 10 |
Last updated 4 October 2026
Still stuck?
If this did not answer your question, tell us and we will fix the page as well as answer you.