← Blog

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/{id} 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 alertsStatus page subscribers
WhoYou / on-callCustomers, partners
Sign-upApp settingsPublic page “Subscribe”
AuthTelegram bot link, Slack webhook, emailGoogle sign-in
TriggerCheck → DOWN, reminders while downNew incident post you write
Free tier1 channelSubscribers allowed (cap per plan)
PurposeWake 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)

  1. Connect Telegram or Slack or email.
  2. Register health URL — quickstart.
  3. Test: pause check or break staging URL briefly.

Subscribers (after public page exists)

  1. Share /s/{id} in docs — findability.
  2. Tell customers: subscribe for incident emails, not feature releases.
  3. During outage: post on page; subscribers auto-notified — cadence.

Related guides

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.