Public status pages that update themselves
Every FourSight plan — including Free — includes a public status page driven directly by your monitors. When a multi-region quorum confirms an outage, the page updates automatically; subscribers get notified; maintenance windows show as banners. No separate status-page product, no separate bill, no manual updating.
A status page has one job: answer "is it you or me?" before the customer opens a support ticket. Done well, it cuts inbound support during incidents dramatically and turns downtime — the worst moment in your customer relationship — into a demonstration of competence.
Most teams bolt a status page on as a separate product with its own subscription, its own incident workflow, and a human in the loop who has to remember to update it mid-outage. FourSight takes the opposite approach: the status page is a rendering of your actual monitoring. The same 4-region quorum checks that page your on-call also flip the public component status, so the page is exactly as current as your monitoring — always.
Don't take the claim on faith: our own demo page at /status/demo is a live FourSight status page monitoring real endpoints. What you see there is what your customers would see.
Why do status pages go stale during real incidents?
Because most status pages are manual. When an outage starts, the engineer who could update the page is the same engineer debugging the outage — so the page says "All Systems Operational" for the first forty minutes while Twitter and the support queue say otherwise. That gap is precisely when customer trust is decided, and a stale page is worse than no page: it reads as either ignorance or dishonesty.
A monitor-driven page removes the human from the critical path. FourSight opens an incident when a quorum of probe regions confirms the failure, the affected component flips on the public page within the same cycle, and the incident timeline accumulates automatically. You can still post human context — what's happening, what you're doing about it — but the factual state of the system never waits on anyone's keyboard.
What do FourSight status pages include?
Each page is composed of components mapped to your monitors, with current state, uptime history, incident timeline, and maintenance visibility built in.
- Live component status driven by 4-region quorum checks — no false "down" from a single probe blip
- Automatic incident creation and a public incident timeline as the outage progresses and resolves
- Subscriber notifications so customers hear it from you, not from their own error logs
- Maintenance banners: schedule a window and the page announces it, before and during
- Uptime history so prospects can verify your track record instead of taking your word
- Custom CSS on Pro; custom domains and full white-label on Scale
Is the free status page really free?
Yes — one public status page is included on the Free plan, which also allows commercial use. That combination is deliberately rare in this market: most vendors either gate status pages behind paid tiers or sell them as an entirely separate product. A side project, an early-stage startup, or a freelancer with production clients can run a real, monitor-driven public status page at zero cost.
As you grow, the ladder grows with you — more pages, then customization, then white-label:
| Plan | Status pages | Customization |
|---|---|---|
| Free ($0) | 1 | Standard FourSight page |
| Starter ($16/mo) | 2 | Standard FourSight page |
| Growth ($40/mo) | 5 | Standard FourSight page |
| Pro ($80/mo) | 10 | Custom CSS |
| Scale ($160/mo) | 25 | Custom domains + white-label |
How do subscriber notifications work?
Visitors to your status page can subscribe to updates. When an incident opens, updates, or resolves — or a maintenance window is scheduled — subscribers are notified automatically. That flips the support dynamic during an outage: instead of a thousand customers individually discovering the problem and emailing you, they hear about it from you first, along with the fact that you're already on it.
The subscriber list is a trust asset with one rule: never use it for marketing. FourSight status page notifications are operational only — incidents and maintenance — which is exactly why customers stay subscribed.
How does this compare to a dedicated status-page product?
Dedicated products like Atlassian Statuspage or Instatus are more customizable at the top end, and if you need a deeply branded, marketing-grade status site with no monitoring attached, they're reasonable choices. But they don't monitor anything — you still need a separate uptime monitor, plus the integration between the two, plus the second subscription. Statuspage in particular gets expensive quickly as subscriber counts grow.
FourSight's bet is that the monitoring is the status page. One product, one incident pipeline, one bill — and the page can never disagree with the monitoring because they're the same system. For the large majority of SaaS teams, agencies, and API businesses, that's both cheaper and more honest.
Included on every plan — starting free
Put up a real status page today — free
The Free plan includes 10 monitors with 4-region validation and one public status page, commercial use allowed, no credit card required. Upgrade for more pages, custom CSS, or full white-label when you need it.
- Status page included on every plan — starting at $0
- Driven by the same quorum checks that power your alerts
- Subscriber notifications and maintenance banners built in
- White-label with custom domains on Scale — built for agencies
FAQ
Common questions
Does the status page update automatically when my site goes down?
Yes. When FourSight's 4-region quorum confirms a failure, an incident opens and the mapped component on your public page changes state in the same cycle — no manual step. When checks recover, the incident resolves and the page follows.
Can I use my own domain?
Custom domains and white-label status pages are included on the Scale plan — point a CNAME like status.yourcompany.com at your FourSight page and your customers never see our brand. Pro includes custom CSS on the FourSight-hosted URL.
Can visitors subscribe to updates?
Yes — status pages support subscriber notifications for incident and maintenance updates, so customers hear about problems from you rather than discovering them. Notifications are operational only, never marketing.
How do maintenance windows appear?
Schedule a maintenance window in FourSight and the status page shows a banner announcing it; while the window is active, planned work isn't presented as an outage. Growth and above support recurring windows for regular maintenance schedules.
Is there a live example I can look at?
Yes — /status/demo is a live FourSight status page monitoring real endpoints. It's the actual product, not a mockup: the same page your customers would see, driven by real checks.
Can I run status pages for multiple products or clients?
Yes — plans scale from 1 page (Free) to 25 (Scale). Agencies typically use Scale's 25 white-label pages to give each client their own branded status page; see our agencies solution page for the full pattern.
Keep reading
Related guides, terms & comparisons
More check types
Explore FourSight's other monitors
Start monitoring in under 60 seconds
No credit card required. 10 free monitors with 4-region consensus — commercial use allowed.