StillOnline?

Launch checklist: status page before you go live

Launch day traffic spikes expose whatever you skipped: no health URL, no public status link, support guessing while you read deploy logs. This checklist is the communication layer you can finish the day before press or Product Hunt—not a replacement for load testing.

StillOnline gives you external HTTP checks, a hosted page at stillonline.tech/s/..., and owner alerts via email, the StillOnline bot on Telegram, or Slack. Run through it once; reuse on every major release.

Quick answer

Before go-live: (1) public GET /health returning 200, (2) StillOnline check on that URL, (3) status link in docs/onboarding/support macro, (4) one owner alert channel on Free. Wait 2–3 probe cycles after creating the check. Post scheduled maintenance for risky deploys. StillOnline does not load-test your app.

Day before launch

Do these while traffic is still low.

StepDone when
Health route live on production hostcurl from outside Wi‑Fi returns 200 in <2s
StillOnline project + checkDashboard green after 2–3 intervals
Public URL copiedLink in README, help center, launch email draft
Owner alertsTelegram or email tested with a intentional staging fail
Incident template readyCopy bank in Notion

Full production monitoring list: side project checklist.

Launch day

MomentAction
T-60 minOptional maintenance incident if deploy is risky
DeployWatch StillOnline dashboard + owner channel
T+15 minConfirm public status page matches dashboard
Support macrosPaste status link in auto-replies
Social / PHOne line: “Status: [url]”

If the check flips red, fix forward—do not hide. Update the incident post on the same page.

Week one after launch

  • Add Subscribe with Google note for integrators on the public page.
  • Review false greens (redirects and antibot).
  • If API and marketing both matter, plan Pro for a second URL (pricing).

What not to block launch on

  • Custom domain on the status product (StillOnline hosts the URL).
  • Enterprise status vendor RFP.
  • Page Speed tab (add after uptime is boring: uptime vs page speed).

FAQ

Can I launch without a StillOnline status page?

You can, but the first outage costs more support time than this checklist takes. Free includes a real public page—ship the link before traffic.

Should the launch checklist include Page Speed?

Optional after core uptime. Schedule PSI on marketing URLs on Pro—Page Speed guide—not on /health.

How long before I trust a green StillOnline check?

Wait 2–3 intervals (5 minutes each on Free). One green probe is noise.

StillOnline alerts during a planned launch deploy?

Brief red is possible. Post maintenance or explain in an incident; keep owner alerts on for overruns (scheduled maintenance).

Where should the status link appear on launch day?

Footer, onboarding email, support signature, and Product Hunt comment—same URL everywhere. Public status page guide.

Does StillOnline replace staging environment monitoring?

Monitor production URLs customers use. Staging checks belong on separate projects or slugs—not the same check you give customers.

Further reading