Tell your customers. Not your topology.
A status page your customers can read, built from the checks you already run — without publishing a single host name, address or error message.
Nothing new to maintain
Pick the checks that matter to the people outside, give each one a name they will understand, and the page keeps itself up to date. There is no second system to update during an incident, and no switch anybody forgets to flip afterwards.
Each service on the page carries the label you give it, so a page reads as a customer thinks — "Storefront", "Checkout" — rather than as your rack is wired.
Gryphon runs its own on it. See the live page that tells you whether this service is up.
What a visitor sees, and what they never do
An address you choose
Your own slug, so the page is at an address you can hand out and put in a footer. A page for every host you watch, on every plan — one for customers, one for each large client, one for the internal services your colleagues keep asking about. Search engines are kept away unless you switch listing on, so a page made for one client stays between you and them.
Your domain, a password, your name alone
On Pro and Teams a page can live at an address of your own, such as status.yourcompany.com, with its certificate issued automatically once a CNAME points it at Gryphon. It can also ask for a password before it shows anything, for a page meant for one client or for staff. On Teams it can leave out "Powered by Gryphon" as well.
Thirty days, service by service
A bar for each of the last thirty days and a percentage beside it, so somebody can see at a glance whether last Tuesday was a one-off or the third time this month. Days begin at midnight in the time zone you set for the page.
Maintenance is not downtime
A scheduled window is drawn in its own colour, labelled as maintenance, and left out of the uptime figure. Planned work does not cost you a number you have to explain.
Gaps are admitted, not papered over
If checks were paused, switched off or stopped by a lapsed subscription, that time shows as no data instead of being counted as healthy. A status page that quietly claims 100% for a week nobody was watching is worse than no status page.
Your labels, and only your labels
Host names, IP addresses, ports and the text of check messages never appear. A visitor learns that Checkout is having trouble, not that db-03.internal:5432 refused a connection.
No sign-in, no account
A visitor opens the page and reads it. It is a plain page, so it loads on a phone on bad hotel wifi during the exact incident it exists for.
Setting one up
-
1
Name the page
A title your customers will recognise, and the address you want it to live at.
-
2
Choose the checks
From the ones you already run, each with a label a customer will understand, in the order you want them.
-
3
Save it
It is live at once, and you can forget about it. It follows your checks from then on, including the maintenance you schedule later.
Fourteen days free. Then from $4.99 a month.
The agent, the dashboard, the apps and every check but the five for Kubernetes are in every plan. The plans differ in how much you watch, how often, from where, and how many people and status pages they include. Compare the plans. Cancel any time.
Already have an account? Sign in