Status page subscribers vs owner alerts on StillOnline
Teams confuse “who gets emailed when we’re down?” StillOnline runs two separate channels: owner alerts (you, the operator) and public page subscribers (customers and stakeholders).
Mixing them in docs creates support debt. This guide keeps roles clear.
Quick answer
Owner alerts fire when your HTTP check goes DOWN after two failed probes — configure email, StillOnline Telegram bot, or Slack in settings. Free = one owner channel; Pro/Ultimate = all three. Status page subscribers sign up on the public stillonline.tech/s/demo page with Google email and receive mail when you publish incident updates — not on every probe blip. Owners hear first; subscribers read your narrative.
Side-by-side
| Owner alerts | Status page subscribers | |
|---|---|---|
| Who | You / on-call | Customers, partners |
| Sign-up | App settings | Public page “Subscribe” |
| Auth | Telegram bot link, Slack webhook, email | Google sign-in |
| Trigger | Check → DOWN, reminders while down | New incident post you write |
| Free tier | 1 channel | Subscribers allowed (cap per plan) |
| Purpose | Wake you at 3 a.m. | Reduce “is it down?” tickets |
Subscriber caps: 50 Free · 100 Pro · 500 Ultimate per status page — pricing. Public subscribe uses Google Identity sign-in — describe that flow in your privacy policy.
Setup checklist
Owners (do first)
- Connect Telegram or Slack or email.
- Register health URL — quickstart.
- Test: pause check or break staging URL briefly.
Subscribers (after public page exists)
- Share
/s/demoin docs — findability. - Tell customers: subscribe for incident emails, not feature releases.
- During outage: post on page; subscribers auto-notified — cadence.
FAQ
Will StillOnline email my customers when a probe fails?
Only if they subscribed on the public status page. Automatic probe failures alert owners only — copy this line into your help center if buyers ask.
Is the StillOnline Telegram bot for my end users?
No. @stillonlinebot is for owner alerts. Customers use the public page link and optional email subscribe — same pattern as public status pages that separate operator paging from customer subscriptions.
Do subscribers get owner “DOWN” emails?
No. Different notification pipelines.
Same email address as owner and subscriber?
Allowed technically; you may get both alert types — tune channels in settings.
API to add subscribers?
Manage via public UI; automation pairs with incident posts on Pro API — REST API.
Discord for owner alerts?
No native Discord — workarounds.
Further reading
Telegram alerts when your service goes down
Get Telegram DM alerts when an HTTP check fails, recovers, or stays up 24h. Link the StillOnline bot in settings — no BotFather or webhook URL needed.
Customer email template during an outage
Email all customers during an outage with a link to live StillOnline updates—distinct from status page subscriber notifications.
Public status page for SaaS and API
Ship a public status page so customers see uptime, history, and incidents. Works for SaaS, APIs, Telegram bots, and self-hosted agents — free on StillOnline.
B2B SaaS Status Page for Customer Trust — StillOnline Guide
Why B2B buyers ask for a status page link, how to add it to contracts and security reviews, and set up StillOnline checks with Telegram bot alerts.