Status Pages
Your users shouldn't have to guess.
Outages happen. What matters is how your users find out. A status page that actually reflects reality — not one that says "All Systems Operational" while your API is on fire — is how you build confidence with the people who depend on your product.
How it works
Automatic or manual. Your call.
Connected to monitors
Set it and forget it
When you connect monitors, your status page updates itself. A confirmed outage changes the component state, regenerates the page, and notifies subscribers. You fix the problem, we handle the communication.
Standalone
You're in control
No monitors needed. Create components, set their state through the dashboard or API. Post incident updates when you want, with the detail you want. Use it alongside your existing monitoring, or on its own.
Architecture
Static HTML. Zero dependencies.
Every time a component changes state, we regenerate your status page as a fully self-contained HTML file. All CSS inlined, no external resources. The new version is uploaded to CDN edge nodes worldwide and live within seconds.
When your users load the page, there are no database queries, no server-side rendering, no API calls. Just HTML from the nearest CDN edge. If our entire platform went offline, your status page would keep serving the last rendered version from cache.
Render pipeline
Component state changes — from a monitor, the dashboard, or the API
Status page HTML regenerated with fresh uptime data and state
Uploaded to CDN storage, cache purged at all edge locations
Live worldwide within seconds. Subscribers notified by email.
Incidents
Tell the story as it unfolds.
When something goes wrong, you create an incident. Each update adds context — what's happening, what you're doing about it, which components are affected. Your status page shows active incidents with a timeline.
When it's resolved, it moves to the history. Your users get the full picture without you having to answer the same question fifty times.
Incident timeline
We're seeing elevated error rates on the API. Looking into it.
Root cause identified. A bad deploy is causing database connection pool exhaustion.
Fix deployed. Error rates returning to normal. Monitoring for the next 30 minutes.
Fully resolved. API error rate back to baseline.
What you get
Everything you need, nothing you don't.
Uptime history
90 days of context
Daily granularity. Aggregate uptime percentage per component. Your users see the full picture, not just the current moment.
Branding
Your logo, your colors
Light, dark, and system-auto themes. Custom brand color and logo. Removable Larm branding on Pro.
Subscribers
Automatic notifications
Users subscribe to your status page and get notified when components change state. No manual broadcasting required.
REST API
Automate everything
Create incidents, update component state, manage subscribers. Integrate with your deploy pipeline, your CI, your runbooks.
Your domain
status.yourdomain.com
Point your own domain at your status page. Add a CNAME, we handle DNS verification and SSL provisioning. Your users see your brand, not ours.
Pricing
Free: 1 status page, 100 subscribers. Pro: 3 pages, custom domain, 1,000 subscribers.
A status page in five minutes.
Free plan. No credit card. Custom domains on Pro for $19/mo.
Sign Up Free