Status page vs social media during an outage
Founders post “we’re aware” on Twitter/X or a Telegram channel — then answer fifty DMs asking for the same link. A public status page is the bookmark customers reuse; social is amplification, not the system of record.
StillOnline hosts stillonline.tech/{locale}/s/{id} with probe-driven status, incident timeline, and subscriber email via Google sign-in. Owner alerts (Telegram bot, Slack, email) wake you first — subscribers vs owner.
Quick answer
Use your StillOnline status page as the single source of truth for incident text and timestamps. Post a short social teaser with the status URL — do not write different facts on X and on the page. First incident update within ~5 minutes of confirming customer impact — cadence guide. Free includes one public page per project; subscribers get email when you publish incident updates on that page.
What goes where
| Channel | Role | StillOnline fit |
|---|---|---|
| Status page | Canonical timeline, history, subscribe | Primary — auto status from HTTP checks + manual incidents |
| Twitter/X | Reach, “link in bio” during incident | One post → status URL |
| Telegram channel | Community / RU audience | Pin status link; owner alerts ≠ channel — Telegram alerts |
| Email blast | All customers | Link to page; see customer email template |
| Support macros | Tickets | Paste /s/... link |
NIST SP 800-61 stresses consistent stakeholder communication — one authoritative channel reduces rumor drift. Google SRE separates internal war-room chat from customer-facing status updates — same split as status page vs social.
First post template (social)
We’re investigating an issue affecting [Dashboard/API]. Live updates: https://stillonline.tech/s/your-id
Next update on the status page within 30 minutes.
Do not promise root cause on social before the status page says so.
Why not social-only
| Problem | Status page fix |
|---|---|
| Posts scroll away | Permanent URL + incident history |
| No uptime history | 24h strip on Free, 90 days on Pro |
| Subscribers re-ask | Google email subscribe on public page |
| You repeat yourself | One timeline, many links |
StillOnline workflow
- Probe goes DOWN → owner alert via Telegram bot.
- Open manual incident on affected component — incident template.
- Share same URL on social once; update only the status page thread.
- Resolved on page → optional social all-clear with link to postmortem note.
Related guides
- Incident update cadence (5-minute rule)
- Public status page guide
- Customer email during outage
- Subscribers vs owner alerts
FAQ
Should StillOnline replace my Telegram channel?
No. Channel = community voice; status page = canonical ops timeline. Link the page from the channel pin.
Do StillOnline subscribers get every social post?
No. They get email when incident/status changes on the hosted page — not your marketing Telegram.
Can I embed the StillOnline page in Twitter?
Link out; Twitter cards show your domain. No custom domain on status page in v1 — use hosted stillonline.tech/s/....
Private incident notes on StillOnline?
Public page is customer-facing. Internal war room stays in Slack/Telegram; public text on the status page only.