Telegram Alerts
Telegram alerts are instant downtime and recovery notifications that MonitorUrs delivers through its Telegram bot. You link a personal chat or a team group to MonitorUrs once, and the bot pushes a formatted message the moment a probe fails and again automatically when the service comes back online.
Last updated: June 2026
Why Telegram for alerts
When something breaks, the speed of the alert decides how long the outage lasts. Telegram is built for exactly this: it is free, runs on every phone and desktop, and pushes notifications instantly. Most teams already keep it open all day, so a downtime message lands where people will actually see it — not buried in an inbox or lost behind a spam filter.
Telegram also fits how teams really work. A single bot can message one engineer or an entire on-call group, messages support rich HTML formatting so the important details stand out, and there is no per-message cost to worry about. For day-to-day operational alerting it gives you the immediacy of a push notification with the flexibility of a chat platform, which is why it is the default channel many MonitorUrs users reach for first.
How to connect Telegram to MonitorUrs
Connecting a chat is a one-time setup that takes about a minute. MonitorUrs uses a unique registration code to securely tie a Telegram chat to your account:
- Open the MonitorUrs bot: start a chat with the MonitorUrs bot in Telegram, or add it to the group you want to receive alerts.
- Get your code: in MonitorUrs, generate the unique registration code for the contact you want to connect.
- Link the chat: send that code to the bot. MonitorUrs verifies it and stores your Telegram chat ID so it knows exactly where to deliver messages.
- You're connected: from then on, every alert assigned to that contact is delivered straight to the linked chat — no further setup needed.
Because the link is keyed to the stored chat ID, you control exactly which chats receive alerts. To stop messages at any time, simply send the word stop to the bot and it will stop delivering to that chat; you can reconnect later with a fresh registration code.
What a Telegram alert contains
A good alert tells you what broke and what to do without making you open another tool. MonitorUrs messages support HTML formatting, so the key facts are easy to scan at a glance. A typical downtime alert includes:
- What failed — the name of the probe or server that triggered the alert.
- What kind of failure — for example a probe failure, a server reported offline, or a threshold rule being breached.
- When it happened — the time the failure was detected so you can line it up with deploys or other events.
- Status — whether this is a new downtime alert or an automatic recovery message confirming the service is back.
When alerts fire
Alerts are generated by the MonitorUrs monitoring engines — the same engines that run your website monitoring and uptime monitoring checks. When a probe fails, a server reports offline, or a threshold rule is breached, the engine creates a message and places it in a central outgoing-message queue.
That queue is processed continuously — polled about every 15 seconds — so a message is picked up and delivered to Telegram within seconds of being created. Each queued message tracks its own delivery state and is retried if a send fails, so a momentary network or API hiccup does not silently lose an alert.
A downtime alert only fires once consecutive failures reach the threshold you configured, which filters out one-off blips and keeps the channel free of noise. When the service is restored, MonitorUrs sends an automatic recovery message to the same chat, so the loop closes itself and you always know an incident is over without having to go and check.
| Channel | Best for | Formatting | Group delivery |
|---|---|---|---|
| Telegram | Fast, free, day-to-day operational alerting for individuals and teams. | Rich HTML messages. | Yes — personal chats and group channels. |
| SMS | The most critical, can't-miss incidents that must reach a phone. | Plain text. | Per-recipient. |
| Detailed notifications and a written record, with retry and bounce handling. | Formatted email. | Per-recipient / distribution lists. |
Team channels vs individuals
MonitorUrs can deliver to both individual chats and group channels, because both have a stored chat ID once they are linked. Which one you choose depends on how your team responds to incidents.
Individual chats are ideal for the person who owns a specific system — they get a direct, private message and can act immediately. Group channels are better when a whole team shares on-call duty: add the bot to your operations or on-call group, link it with a registration code, and every member sees the same downtime and recovery messages in one place. Many teams use both — a shared channel for visibility plus direct messages to the engineer responsible for each system.
Common use cases
- On-call engineering teams — pipe every downtime and recovery message into a shared on-call channel so whoever is available can jump on it.
- Solo founders and small teams — get a free, instant push to your own phone the moment a site or server goes down, with no extra cost per alert.
- Agencies — keep a per-client group channel so each client's outages are visible to the right people, and pair it with the full incident history for reporting.
- Operations and NOC dashboards — use Telegram as the always-open feed of live incidents alongside the status dashboard.
How it fits with SMS, Email and your monitoring
Telegram is one of three delivery channels in MonitorUrs, and they work best together. Use Telegram as your fast, free, everyday channel; escalate the truly critical incidents to SMS alerts so they reach a phone even when no one is looking at a screen; and rely on email alerts for detailed notifications and a written record with retry and bounce handling.
All three channels are fed by the same monitoring engines and the same outgoing-message queue, so whatever you watch with website monitoring or uptime monitoring can alert on every channel at once. Each delivered message also becomes part of your incident history, giving you both the instant notification and the long-term record in one platform.
Frequently asked questions
How do I connect Telegram to MonitorUrs?
Open the MonitorUrs bot in Telegram and link your chat using the unique registration code shown in MonitorUrs. Once the code is verified, your Telegram chat ID is stored and the bot can deliver alerts to that chat.
Can a Telegram group receive MonitorUrs alerts?
Yes. Both individual chats and group channels can receive alerts. Add the MonitorUrs bot to a group and link it with a registration code so the whole team sees every downtime and recovery message in one shared channel.
When does MonitorUrs send a Telegram alert?
A downtime alert is sent once consecutive failures reach the threshold you configured for a probe or server. When the service is restored, an automatic recovery message is sent to the same chat so you know the incident is over.
How do I stop receiving Telegram alerts?
Send the word "stop" to the MonitorUrs bot. The bot stops delivering messages to that chat. You can reconnect later by linking your chat again with a registration code.
How fast are Telegram alerts delivered?
Alerts are placed in a central outgoing-message queue as soon as the monitoring engine detects a problem. That queue is processed continuously — polled about every 15 seconds — so messages are delivered to Telegram within seconds of being queued.
What happens if a Telegram message fails to send?
Every queued message tracks its own delivery state and is retried if a send fails, so a temporary network or API problem does not silently drop an alert.