Documentation

Documentation

Customising a status page

Components, branding, maintenance windows and subscribers — everything beyond publishing the page itself.

Last updated August 7, 2026

How do I decide what goes on the page?

Publish components your customers recognise, not monitors you happen to run. "Checkout" and "API" are components; "checkout-api-prod-us-east health endpoint" is a monitor. Group the monitors behind each component so an internal renaming does not confuse the people reading your page during an outage.

Only put a component on the page if you are willing to be honest about it during a bad week. A status page that shows green through an outage does more damage than having no status page at all, which is why the underlying monitors drive the component state rather than a human toggle.

How do maintenance windows work?

Schedule a window ahead of the work and it appears on the page before it starts, so a planned degradation does not read as an unplanned one. Subscribers are notified when it is published.

Schedule it far enough ahead that customers can plan around it. A maintenance notice published fifteen minutes before the maintenance is an outage notice with better manners.

What can I brand?

Page name, colours and logo. Status pages published on the Free plan carry a PageLantern attribution mark, which must not be removed or altered; paid plans do not.

Custom domains for status pages are not available today. The page is served from a PageLantern URL you can link to from your own site and support pages.

How do subscribers work, and what am I responsible for?

Visitors can subscribe with an email address and are notified when you publish an incident update or schedule maintenance. Every message carries a one-click unsubscribe link and RFC 8058 List-Unsubscribe headers, and our postal address as the sender.

Those subscribers are your users, not ours: you are the publisher and the sender for the purposes of CAN-SPAM, GDPR, PECR and CASL. Do not import purchased, scraped or otherwise non-consenting lists. Sending reputation is shared across every PageLantern customer, so one bad list degrades deliverability for everybody, and we will suspend sending for a page whose complaint or bounce rate warrants it.