Uptime monitoring for Telegram and Discord bots
Telegram bots and Discord bots run on a server, serverless function, or container. Users say “the bot is offline” when your process or webhook endpoint stops responding — even when Telegram or Discord’s own status pages look fine.
StillOnline cannot reach localhost. You expose a public GET /health HTTPS URL on the host that runs the bot, register it for uptime checks and a public status page, and alert yourself with the StillOnline Telegram bot (owner account) or Slack/email — separate from your product bot token.
Quick answer
External monitors cannot reach localhost. Expose a public GET /health HTTPS URL on the same host that runs your bot (or webhook handler). Add that URL to StillOnline for uptime checks and a public status page. Alert yourself with the StillOnline Telegram bot (for your owner account) or Slack/email — separate from your product’s Telegram bot token.
Architecture patterns
Pick a health URL that proves what “up” means for your deployment — webhook listener alive, long-polling process running, or gateway sidecar healthy.
| Bot type | Health URL should prove |
|---|---|
| Telegram webhook | HTTPS endpoint accepts Telegram traffic; /health returns 200 |
| Telegram long polling | Process up; optional ping to Telegram getMe in deep check |
| Discord gateway bot | Gateway connected or HTTP sidecar /health |
| Discord interactions (webhook) | Public HTTPS handler alive |
Platform status: check Telegram / Discord status separately — your StillOnline page is your bot service.
Step-by-step
- Deploy bot with
https://bot.yourdomain.com/health→ 200 JSON. curlfrom outside — health quickstart.- StillOnline → project named after the bot → HTTP check.
- Share status page in bot
/helpor support channel — public status page guide. - Owner alerts: link your Telegram to the StillOnline bot (guide) — this is not the same token as your product bot.
Discord team notifications
StillOnline has no native Discord webhook for owner alerts today. Use Slack alerts, Telegram via the StillOnline bot, email, or Discord workarounds for team channels.
Common mistakes
Monitoring t.me/YourBot checks Telegram’s UI, not your server. Private IPs fail external probes — production must be public HTTPS.
| Mistake | What to do |
|---|---|
Monitoring t.me/YourBot | That is Telegram’s UI, not your server |
| Health only on private IP | Use reverse proxy or tunnel for dev; prod must be public |
| No status page | Users blame your bot during platform outages — clarify scope in incident text |
Agents on VPS: OpenClaw monitoring.
Related guides
- Public status page for SaaS, API, or bot
- Webhook platform status page
- Telegram owner alerts (StillOnline bot)
- Health endpoint design
FAQ
Does StillOnline DM my bot’s end users when the bot is down?
No. Owner alerts go to you via email, Telegram (StillOnline bot), or Slack — not through your product bot token. Share the public status page in /help or support — public status page guide.
Should StillOnline monitor api.telegram.org for my Telegram bot?
Usually no — monitor your public HTTPS health on the host that runs the bot. Platform outages are separate; say so in incident text on your StillOnline page.
Is StillOnline Free enough for one bot SaaS product?
Yes — 1 URL and a hosted status page on Free. Add the health URL after deploy — health check quickstart.
Can MCP agents check StillOnline bot uptime without the dashboard?
On Pro, get_public_status via MCP guide. Discord team alerts are not native — use Discord workarounds, Telegram, or Slack.