How status pages work
Your status page is a view of your disruptions. When you create a disruption and post an update that affects a status page component, the page re-renders with the new state. When you resolve the disruption, the component goes back to operational and the disruption moves to the history section. With monitors: Monitors create disruptions automatically. If a status page component is linked to a monitor, the whole flow is hands-free — outage detected, disruption created, status page updated, subscribers notified, and resolved when the monitor recovers. Without monitors: Create disruptions yourself, post updates, choose which components are affected. You’re in control of the timing and the messaging. You can also hit the Post update button directly on a status page to create a disruption in one step — it’s a shortcut into the same disruption workflow.Creating a status page
Go to Status pages and click New status page. Configure the settings, add components, and optionally customize the branding. Your page is published athttps://<slug>.status.larm.dev.
Page settings
Components
Components are the services or systems shown on your status page — “API”, “Dashboard”, “Payment processing”, whatever makes sense for your users. Each component has a name, optional description, and a display position. A component can be linked to monitors for automatic updates, or left standalone.Component states
Component state is set by disruptions. When a disruption update marks a component as “major outage”, that’s what your users see on the status page until the disruption is resolved or a newer update changes it.
Maintenance
Use maintenance to tell visitors that work is in progress on some of your services.- Click Maintenance on the Disruptions page or on a status page.
- Give it a title and a message, pick the status pages to publish to and the affected components on each, and click Start maintenance. It starts right away.
- Post updates as the work goes on.
- Click Complete when you’re done. The completion is published to every page the maintenance was published to.
Custom domains
Custom domains are available on paid plans.
status.example.com). Apex domains are not supported — use a subdomain.
- Enter your domain in the status page settings
- Add a CNAME record pointing your domain to
<slug>.status.larm.dev - If you’re using Cloudflare, also add a TXT record:
_larm-verify.<your-domain>with valuelarm-verify=<token>(shown in the dashboard) - Click Verify — Larm checks DNS and provisions SSL automatically