How to get a public status page for your online product

You run something on the internet: a SaaS app, a REST API, a Telegram bot, an AI agent on a VPS, or a landing + checkout stack. When it breaks, users ask “is it just me?” before they read your logs. A public status page answers that in one link — green, yellow, or red, with recent checks and an open incident if something is wrong.

StillOnline gives you that page automatically when you add external uptime checks. This guide is about the page, not only the probe. For the health URL itself, start with health check quickstart.

Quick answer

A StillOnline public status page updates automatically from external HTTP checks—no manual “we’re up” post. Create a project, add one health URL on Free, share https://stillonline.tech/en/s/{project-id} in docs, onboarding, or incident comms (not the site footer). Visitors see uptime, history, and incidents; you get owner alerts via Telegram, Slack, or email. Custom domains for the status page are not offered—use the hosted StillOnline link.

Who needs a public status page

You do not need a separate “status product” subscription—only a project in StillOnline with at least one external check. The table maps common product shapes to what customers expect on the page.

You do not need a dedicated “status product” team. One project, one check on Free, and you already have a shareable URL.

What visitors see (and what you get)

On a typical StillOnline public page:

• Overall status — operational, degraded, or down from the latest probes.
• Per-check rows — HTTP uptime (and SSL on paid plans where enabled).
• History — 24 hours on Free, longer on Pro/Ultimate.
• Open incident — when monitoring marks an outage (and cleared when checks recover).
• Subscribe with Google — stakeholders get email when status changes (no manual mailing list on your side).

Behind the scenes you still want owner alerts (email, Telegram, Slack) so you hear first. Setup: Telegram · Slack. Free = one owner channel; Pro/Ultimate = all three in settings.

Preview a live example: demo status page.

Five steps to publish your page

1 — Expose a health URL

Monitors only see a URL you choose. Add GET /health (or /api/health) that returns 200 when the service is alive. Verify from outside:

curl -sS -o /dev/null -w "%{http_code}\n" https://api.yourproduct.com/health

Details: Health check URL quickstart. Bots and local agents need a public health endpoint first — see OpenClaw / agent monitoring.

2 — Create a project in StillOnline

1. Start free (Google sign-in).
2. New project — name matches what customers recognize (product name, not internal codename).
3. StillOnline creates a status page with public visibility by default.

3 — Add your first check

Paste the full HTTPS URL, method GET, expect status 200, interval 5 minutes on Free. After two or three probe cycles, the page should show green if your health URL is correct.

Free limits (honest): 1 project, 1 URL, 24h history. More checks, private pages, API/MCP: Pricing (Pro $9/mo).

4 — Copy the public link

In the project dashboard you get:

• Human page: https://stillonline.tech/en/s/{project-id} (locale prefix en or ru).
• Machine JSON: https://api.stillonline.tech/v1/public/status/{project-id} — no API key; for status widgets, CI smoke tests, or agents (REST guide).

Put the human URL where customers look when something breaks:

• Help center / Notion / README / API docs
• Onboarding email for B2B customers
• Support reply template or contract appendix
• Social post or email during an incident

5 — Optional but recommended

• Turn on owner alerts so downtime does not depend on someone refreshing the page.
• Ask key customers to Subscribe on the page (Google) for email updates.
• On Pro: stillonline-mcp to recreate checks after infra moves (MCP post); set private visibility if the page is internal-only.

Public vs private visibility

Public is the default: anyone with the link sees the same view as your demo page. Private hides the HTML and JSON from anonymous visitors while you still manage checks in the dashboard—useful for internal-only stacks on Pro.

Downgrade from paid forces public again — plan for that if you share the URL widely.

Status page is not a substitute for

A status page answers availability and comms for outsiders. It will not replace engineering tools that explain why something failed inside your stack.

• Deep APM — no distributed traces on the page; probes are HTTP/SSL shaped.
• Log search — use your host or logging stack for root cause.
• Synthetic “click” tests — unless you expose a route that represents that path.
• Page speed regressions — use Page Speed monitoring on marketing URLs separately from /health.

Choosing tools? Best uptime monitoring for indie SaaS 2026 · comparison hub.

Related guides

• Health check URL quickstart — prerequisite probe URL.
• Monitor on Vercel · Monitor on Railway — platform-specific health routes.
• REST API public status JSON — automate reads without the HTML page.
• Page speed monitoring — marketing URLs, separate from /health.
• Telegram owner alerts · Slack webhook.
• Best uptime monitoring for indie SaaS 2026 · comparison hub.

FAQ

Do I need a custom domain for a StillOnline status page?

No. StillOnline hosts your page at https://stillonline.tech/{locale}/s/{project-id}—share that link in help docs, B2B onboarding, support macros, or incident email. A custom domain for the status page is not part of the product today; the hosted URL is the canonical customer-facing status link.

Can I use a custom slug instead of the StillOnline project id in the URL?

New StillOnline projects use the project id in links from the dashboard (/s/{project-id}). Some legacy slug aliases may still resolve, but you should copy the id-based URL from the app when publishing. Machine-readable status uses the same id: REST public JSON.

Will StillOnline status page email subscribers get spam on every probe?

No. Subscribe with Google on the public page sends email on meaningful status changes tied to incidents and recovery—not on every 5-minute probe tick. That is separate from owner alerts you configure in settings (Telegram / Slack).

Can StillOnline show a public status page for an AI bot with no public health URL yet?

No. StillOnline external checks cannot reach localhost or private LAN IPs. Publish GET /health on public HTTPS first (tunnel or reverse proxy)—OpenClaw / agent guide—then add the check; the status page follows automatically.

How is a StillOnline status page different from a social “we’re investigating” post?

The StillOnline page is always available, shows history and per-check status, and works for users who do not follow your social accounts. During major outages, use both: post for reach, link the StillOnline URL for detail. Page speed regressions belong on Page Speed, not mixed into /health uptime.