Set Up Telegram Uptime Alerts You Won't Miss
Email alerts sit in an inbox next to newsletters; chat channels get muted. If you want to know within minutes that your site is down, the alert has to land on a device you carry and make a sound you will not ignore. Telegram does that well. This guide shows exactly how to link Telegram to Uptime Monitor, how to tune your phone so the alerts cut through, what an alert looks like, and what to check when nothing arrives.
Why Telegram works well for uptime alerts
- Push that actually arrives. Telegram is built around instant messaging, so its push notifications are prompt on both Android and iOS, and the same chat is mirrored on desktop and web.
- Per-chat notification control. You can give the alert bot its own sound and keep notifications on even when you mute everything else.
- No extra app or account for the team to buy. Many developers already have Telegram installed. Bots are free to use.
- It is personal. A team Slack or Discord channel is great for shared visibility, but it is easy for everyone to assume someone else saw it. A Telegram message goes to you. Our Slack vs Discord comparison covers the team side.
A note on "zero delay": Telegram itself adds almost no delay, but the alert can only be as fast as the monitoring that triggers it. That depends on your check interval and fail threshold, covered below.
Link Telegram to Uptime Monitor: step by step
Linking works with a one-time code, so you never have to look up or type a numeric chat ID.
- Sign in to Uptime Monitor and open Notification Settings.
- In the Telegram Notifications card, switch on Enable Telegram Notifications.
- Click Generate Link Code. A short code appears, along with the exact command to send.
- Open Telegram and start a private chat with @up2ame_bot. Press Start if this is your first time.
- Send
/link YOUR_CODE, replacingYOUR_CODEwith the code from step 3, for example/link 7KQ2M9XA. - The bot replies with a confirmation. Back in Notification Settings, the card now shows Telegram Connected!
Things to know about the code:
- It is valid for one hour. If it expires, click Generate New Code and send the new one.
- It links the Telegram account that sends the command. One Telegram account can be linked to one Uptime Monitor account; if it is already linked elsewhere, the bot will say so.
- To switch phones or accounts, use Unlink in the Telegram card and link again.
Your email address must be confirmed before monitoring starts, so if you have just signed up, do that first; otherwise there will be nothing to alert about.
Make the alerts impossible to miss
Linking takes two minutes. The part people skip is tuning the phone, and that is what decides whether a 3 a.m. outage wakes you or waits until breakfast.
Give the bot chat its own sound
Open the chat with the bot, tap its name, then open notification settings for that chat. Recent Telegram versions let you choose a custom sound per chat. Pick something distinct from your normal message tone, so you know what it is without looking.
Pin the chat
Long-press the chat in the chat list and choose Pin. It stays at the top, so the alert history is one tap away when you are triaging.
Never mute or archive it
Muting silences the alerts, which defeats the purpose. Archiving is a quieter trap: archived chats are muted by default in Telegram, so tidying up your chat list can silently disable your monitoring. If you need fewer messages, reduce them at the source (see the tuning section below), not on the phone.
Let it through Do Not Disturb
If you are on call at night, add Telegram to the allowed apps in iOS Focus or Android Do Not Disturb. Otherwise the phone receives the alert and shows it in the morning.
Check the system-level settings
On Android, some vendors' battery optimizers delay or kill background apps; exempt Telegram from battery optimization. On iOS, make sure Telegram notifications are allowed in Settings with sounds enabled.
What an alert contains
Each Telegram alert has an icon for the severity, a bold subject line, the message body and the site URL. A downtime alert looks like this:
🔴 Website Alert: https://example.com
Your website is currently unreachable. Status: 503
Probable cause: Server error (5xx).
Site: https://example.com
The "probable cause" comes from the cause code recorded for the failing check, such as a DNS failure, an SSL handshake error, a timeout, a 5xx response or a missing keyword. That one line often tells you whether to look at DNS, the certificate, the web server or the application. When the site comes back after an alert, you get a recovery message marked with ✅. You can also receive slow-response warnings and SSL expiry warnings if you configure them on the site.
For the full picture, open the site in the dashboard: you will find the response-time chart, the recent checks with their probable cause, insights such as the likely bottleneck when the site is slow, and, if screenshots are on for the site, a screenshot captured when the status changed. Our guide on going from "site is down" to "here's why" walks through that view.
How fast will the alert arrive?
Alert speed is mostly arithmetic. The time from the moment your site breaks to the moment your phone buzzes is roughly:
time to alert ≈ check interval × fail threshold (+ up to one extra interval)
| Plan | Shortest interval | Fail threshold | Approximate time to alert |
|---|---|---|---|
| Starter (free) | 5 min | 2 | 10–15 min |
| Plus | 2 min | 2 | 4–6 min |
| Professional | 1 min | 3 | 3–4 min |
| Professional | 1 min | 1 | 1–2 min, but every blip pages you |
A threshold of 1 is fastest but alerts on single network hiccups. Two or three consecutive failures is a sensible default for most sites. The trade-offs are covered in how to choose the right monitoring interval.
During a long outage, reminders are re-sent at the site's notification interval (60 minutes minimum on Starter, 30 on Plus, 5 on Professional), so you are not flooded with one message per check.
Troubleshooting: no message arrived
| Symptom | Likely cause | Fix |
|---|---|---|
| Bot says the code is invalid | Code expired (older than 1 hour), mistyped, or already used | Generate a new code and send /link CODE again |
| Bot says the account is already linked | This Telegram account is linked to another Uptime Monitor account | Unlink it there, or use a different Telegram account |
| Linked, but no alerts during an outage | Telegram toggle is off, the fail threshold was not reached, the site is paused or in a maintenance window | Check the toggle, the site's threshold and its pause/maintenance state |
| Messages arrive but silently | Chat muted or archived, phone in Focus/DND, battery optimization | Unmute, unarchive, allow Telegram in DND, exempt from battery saving |
| Messages stopped after a while | You blocked the bot or deleted the chat | Unblock @up2ame_bot, press Start, and re-link if needed |
A simple end-to-end test: add a site with a URL that you know returns an error (for example a path on your own domain that returns 404), set the fail threshold to 1, wait for the alert, then delete or pause that site.
FAQ
Can I enter my Telegram chat ID instead of using a code?
Not with the shared bot. Linking to @up2ame_bot is done only by sending /link with a code from your account, which proves that the Telegram account belongs to you and prevents anyone from pointing alerts at someone else's chat. On Plus and Professional you can instead connect your own bot (a token from @BotFather) and give it a chat ID; Uptime Monitor checks that the bot can post there before saving.
Can several people get the same Telegram alerts?
With the shared bot, each Uptime Monitor account links one Telegram account. On Plus and Professional, your own bot can post to a group chat or channel, so the whole team sees the alert. You can also add a Slack or Discord webhook; all enabled channels receive every alert.
Does Telegram replace email alerts?
Use both. Email is a durable record and a fallback if Telegram is unreachable from where you are; Telegram is the fast, loud channel.
Checklist
- Notification Settings → enable Telegram → Generate Link Code.
- Send
/link CODEto @up2ame_bot within one hour. - Custom sound for the bot chat, chat pinned, never muted or archived.
- Telegram allowed through Do Not Disturb and battery optimization.
- Fail threshold of 2–3 and the shortest interval your plan allows for important sites.
- Run one deliberate test outage and confirm the alert and the recovery message both arrive.
Telegram alerts are included on every Uptime Monitor plan, including the free Starter plan with one site checked every five minutes. Sign up, confirm your email, and you can have your phone linked to the bot before your coffee cools.