These bots ping a website, API endpoint, or server port on a schedule and send you a Telegram message the moment something stops responding. They're built for anyone who can't afford to find out about downtime from an angry customer.
The best Telegram bot for website and server monitoring is UptimeRobot (@uptimerobot_bot): the official bot of the most widely used uptime monitor sends down and up alerts plus SSL and domain-expiry warnings, with 50 monitors checked every five minutes on the free plan. Check-Host (@checkhostbot) runs on-demand ping and HTTP checks from a dozen locations without an account, and StatusCake (@StatusCakeBot) is the official alert bot for that monitoring service.
The official Telegram bot of UptimeRobot, the most widely used free uptime monitor: delivers instant down/up alerts plus SSL and domain-expiry warnings to a chat or group. Setup of monitors still happens on the website; the free plan covers 50 monitors checked every 5 minutes.
Runs on-demand ping and HTTP checks for any host from a dozen locations worldwide, right inside the chat — no account needed. Free, English interface, useful for a quick 'is it just me' check on a site or server.
Sends a domain name and get an instant WHOIS lookup: registrar, hosting provider and ASN, without opening a web-based whois tool. Free, no ads, no sign-up.
The Telegram delivery bot for StatusCake, a UK uptime and performance monitor with an official Telegram integration: alerts land in chat the moment a StatusCake test fails or recovers. Monitors are still created on statuscake.com; the free plan covers a handful of tests.
Open-source bot that checks whether a website is up right now, or keeps tracking a URL and pings you the moment it goes down. Free, no sign-up, source code published on GitHub.
Small free bot that checks the sites you add every 5 minutes and alerts you the moment one goes down or comes back. No account needed beyond starting a chat with the bot.
Independently run bot that watches sites you register and pings you if anything looks wrong. Free, minimal setup, run by a single developer rather than a company.
Bare-bones bot that checks whether a server or site you point it at is online, and lets you know if it drops. Free, minimal features, best for a single personal server rather than a fleet.
| # | Bot | Price | Languages | Inline | Groups | Score |
|---|---|---|---|---|---|---|
| 1 | UptimeRobot @uptimerobot_bot | Freemium · 50 monitors, checked every 5 minutes | EN | no | yes | 79 |
| 2 | Check-Host @checkhostbot | Free | EN | no | yes | 74 |
| 3 | Whois Bot @WhoisBot | Free | EN | no | yes | 69 |
| 4 | StatusCake @StatusCakeBot | Freemium | EN | no | yes | 67 |
| 5 | Is it UP? @Is_it_UPBot | Free | EN | no | no | 63 |
| 6 | Uptime site @uptime_site_bot | Free | EN | no | no | 58 |
| 7 | UptimeBot @UptimeWebsiteBot | Free | EN | no | no | 56 |
| 8 | ServerWatchBot @serverwatch_bot | Free | EN | no | no | 53 |
We connected three targets to each bot: a stable production site, a URL that returns a 404, and a server with a closed port to fake an outage. We timed how long it took from the simulated failure to the Telegram alert, checked how many targets and how short a check interval the free plan allows, and tested whether the bot also tracks SSL certificate expiry and sends a status page link.
The core number to check first is the check interval on the free plan. Many bots poll every 5-10 minutes for free and drop to 30-60 seconds only on a paid tier — for a site with real traffic, 10 minutes of undetected downtime is a lot. Look for HTTP(S) checks, TCP port checks (for databases, SSH, custom services), and keyword checks that fail if a specific string disappears from the page, not just if the server returns any 200 response.
A monitoring bot needs almost no access to work — it only sends outbound requests to a public URL or port, so it shouldn't ask for admin rights on your Telegram or your server credentials. Test what happens during a real outage: does it retry before alerting (to avoid false positives from one dropped packet), does the alert include a timestamp and response code, and does it notify again when the site recovers? Also check whether alerts can go to a group chat, so more than one person on the team sees them.
Free tiers typically cap you at 1-5 monitors with a 5-10 minute interval and email or Telegram alerts only. Paid plans usually add SMS/call escalation, shorter intervals, multi-region checks (useful for catching a CDN or DNS issue that only affects one region), and a public status page. If you're watching a single personal project, free is usually enough; for anything earning revenue, the jump to a 1-minute interval is worth paying for.
Yes — most monitoring bots have a free tier, usually limited to a handful of monitors checked every 5-10 minutes, which is enough for a personal site or small project.
On a free plan, expect the alert within one check interval plus a short confirmation delay — often 5-15 minutes total; paid plans with a 30-60 second interval can notify you in under two minutes.
Many monitoring bots support this — they check the certificate's expiry date alongside the uptime check and warn you days in advance, which is worth confirming before you rely on one for a production site.