Outages, not audit scores
Automated incidents from uptime and SSL checks appear on the page. Lighthouse, GEO and the other advisory checks don't open incidents at all. The page reflects whether you're up, not whether an audit score dipped.
Status Pages
Posts your outage where users look, so fewer of them DM you about it.
A public status page in your branding, fed by the monitors you already run, on your own domain from Starter. Once an uptime failure is confirmed from a second region, or an SSL check fails, the incident posts itself. Advisory checks stay off it: a noisy Lighthouse dip never opens an incident. Visitors can subscribe by email or follow RSS, Atom and JSON feeds; there's an embeddable badge with live uptime. Included on every plan.
STATUS / SAMPLE OUTPUTIllustrative example
status.acme.io · API down -> incident opened · component flipped · subscribers notified
Fictional values. Not a live measurement.
01 / What it does
A status page fed by the monitors you already run
Hoppla publishes a fast public status page with your logo, colors and footer, on your own domain from Starter. Incidents open once an alert is confirmed, but only automated uptime and SSL incidents appear on the page, next to the updates you post yourself. A failing Lighthouse score or a GEO advisory stays internal. Visitors see what affects availability, not audit noise.
What’s included
- ✓Custom domain (Starter+) or a status.hoppla.dev subdomain
- ✓Your logo, colors and footer; white-label on reseller plans
- ✓Auto-posted incidents from confirmed uptime and SSL failures, uptime re-checked from a second region first
- ✓Advisory checks (Lighthouse, GEO) never open incidents
- ✓Email subscribers, plus RSS and JSON feeds
- ✓Embeddable SVG badge with live uptime %
- ✓Component grouping, rendered as a fast SPA
02 / How it works
Under the hood.
01
Group monitors into components
Map your monitors to public components (API, web app, database) grouped the way your users think about your service. Each component reads its live state from the monitor's uptime check.
02
Brand it, point a domain
Add your logo, colors and footer, then serve it on a subdomain of status.hoppla.dev or, from Starter, on your own domain. It renders as an SPA from a status payload cached for 30 seconds, so a rush of visitors during an outage reads the same cached answer, which is exactly when people show up.
03
Confirmed failure opens the incident
When an uptime or SSL check confirms a failure, Hoppla opens an incident and flips the affected component. Uptime gets re-checked from a second region first, so a single-probe blip doesn't open a public incident. DNS, ping and TCP incidents aren't shown on the page, and Lighthouse and GEO don't open incidents at all.
04
Subscribers and embeds update themselves
Turn on subscriptions and visitors get incident emails after a double opt-in. RSS, Atom and JSON feeds carry the page's incidents and updates to anything that reads them. And an embeddable SVG badge shows a monitor's live uptime % wherever you drop it: docs, README, dashboard.
03 / Why it matters012 checks 022 regions 03Every plan
The part that actually moves the needle.
Confirmed before it's public
An uptime failure is re-checked from a second region before an incident posts. One flaky probe doesn't open a public incident in front of your users.
On every plan, your domain from Starter
Status pages come with every plan, from one on Free to unlimited on Pro, with your logo, colors and footer; a custom domain from Starter.
04 / For every team
Whoever you are, this lands differently.
Solo SaaS founder
You ship alone, so an outage means a flood of "is it down?" DMs landing while you're already heads-down fixing it. Point status.yourapp.com at Hoppla (custom domains from Starter), brand it once, and the page updates itself once your uptime check confirms a failure from a second region. Nothing to write at 3am: the incident is already live, and people can subscribe instead of pinging you. One status page is included on Free.
Small agency
Twenty client sites, nobody whose actual job is monitoring. Give each client a status page on their own domain (from Starter; Pro has no page limit), in their colors and logo, not a generic dashboard. When a client's cert lapses or their host drops, the incident appears on their page on its own, and you look like you caught it before they did. One monitor per site, one branded page per client.
Large agency
Hundreds of client sites, and account managers fielding "is it up?" all day. Run a page per client with grouped components, so they see API, checkout and CDN as separate lines instead of one binary light. Each page keeps its own subscriber list, so a client's stakeholders self-serve their incident email, and the JSON feed drops straight into your reporting. The page count grows; the headcount that maintains it doesn't.
Reseller / hosting provider
You resell monitoring under your own brand, and a status page reading "Powered by someone else" breaks the illusion instantly. Every customer gets a page on your domain, branded end to end, with no Hoppla name anywhere on it. Incidents post from confirmed outages on their own, so customers experience your monitoring product and you bill for it. The status page is part of your offering, not a third party's.
Switching tools
Monitoring somewhere else? Bring your setup with you.
Import the monitors you already run in another tool. What comes across depends on the provider. Run both side by side for 24 hours or 7 days before you switch.
- ✓ Guided import
- ✓ Shadow run before you switch
- ✓ Coverage varies by provider
Import from
- Oh Dear
- Uptime Robot
- Better Stack
- Pingdom
- StatusCakeBeta
- CronitorBeta
- Healthchecks.ioBeta
- Statuspage
The importer opens in your workspace once you have access.
Get early accessFOR HOSTERS & RESELLERS
See the reseller program Give every customer a status page on your own domain, branded end to end, with no Hoppla name anywhere on the public page.
05 / FAQ
Straight answers.
How is this different from Statuspage.io?
Statuspage.io is priced by subscriber count and runs apart from your monitoring. Hoppla includes status pages on every plan, with your logo, colors and footer, and on your own domain from Starter. And because the page is fed by the same monitors raising your alerts, uptime and SSL incidents post on their own, so you're not keeping a separate status tool current by hand.
Do incidents really post automatically?
Yes, for uptime and SSL. When one of those checks confirms a failure, Hoppla opens an incident and flips the affected component on the page. Uptime failures are re-checked from a second region first, so a single-probe blip doesn't open an incident in front of your visitors. You can switch automated incidents off per page and post updates by hand.
Will a bad Lighthouse score show up as an outage?
No. Advisory checks like Lighthouse and GEO audits don't open incidents at all; they top out at a warning. A slow page-speed score or an AI-readiness finding stays in your internal dashboard and doesn't open anything on the status page.
Can I run a status page fully under my own brand?
Mostly, on any plan: your logo, colors and footer, and your own domain from Starter. Removing the "Powered by" line is part of the reseller white-label plan, where every customer can get a page on its own domain that reads as your product start to finish.
Your next step
Put up a status page before you need one.
Checks, alerts and status pages in one workspace. Now in early access: join the list for an invite.