Monitor degrades
A selected component reflects the failed monitor state.
DegradedHealth, update, trust
Status pages that keep incident silence from becoming support load.
PageLantern turns monitor health, incident updates, maintenance, and recovery history into a hosted customer-facing page with your selected components and brand.
Update published
The incident timeline explains scope, impact, and the current response.
InvestigatingService recovers
The component and incident history preserve the return to healthy.
OperationalLive health and communication
One public answer, backed by the monitors you already run.
Choose which services appear, publish the customer-facing narrative, and keep current health and history on the same hosted page.
Customer health
Show the components customers care about.
- Uptime, DNS, TLS certificate, and domain components
- Live state and recent availability history
- Public or private visibility
Communication controls
Publish updates without rebuilding a separate site.
- Incident timelines and maintenance windows
- Email subscribers with component scopes
- Brand colour, logo, and verified custom domain
Plan access: Free includes 1 hosted page and automatic incidents. Starter includes 3 pages and Team 10; manual timeline updates and maintenance windows are paid features. Custom domains require DNS ownership verification.
Example page
Customers see the same incident your team is working.
Illustrative values show the public component state and communication trail together.
- Page
- Acme Cloud
- Components
- 4
- Affected
- Checkout API
- State
- Investigating
- Subscribers
- 184
- Outcome
- Update published
Next step
Publish the answer before the tickets arrive.
FAQ
Frequently asked questions
What can I put on a PageLantern status page?
Status pages connect monitored components, incident timelines, maintenance notes, and uptime history, so customers see current service health from the same monitors your team watches.
Can I choose which monitors appear publicly?
Yes. You select which monitors and component types appear on each status page, and control visibility, naming, colors, and logo.
Can customers subscribe to status updates?
Yes. A public status page can collect email subscribers for every component or selected components, then send customer-facing incident and maintenance updates with one-click unsubscribe links.