Send a confirmed outage
The message goes out once enough independent EU locations fail the check often enough in a row, not on the first failed request; both thresholds sit in your package.
Use Uptimeify with Telegram.
One bot token and one chat id, and every confirmed outage arrives on the phone that is already in your pocket. No app to install.
What lands in Telegram
Everything the alert pipeline sends into Telegram is on this list, and nothing beyond it. Read it once and you know what your team will see.
Send the recovery
The same chat gets the all clear as soon as the check is green again, under its own heading rather than as another alarm.
Post through the Bot API
Each event is one HTML formatted message sent by your own bot, with the link preview suppressed so the chat stays readable.
Reach a chat, a group or a channel
A private chat, a supergroup or a public channel all work, since the target is just the chat id you paste in.
Say what actually broke
Site, URL, incident type, status code, response time and the checking locations follow the heading, with the error in plain language instead of a raw exception.
Warn before certificates and domains expire
Expiring TLS certificates, expiring domains and blocklist hits reach the same chat, early enough to act without a rush.
A chat per monitor
Each channel carries its own bot and chat id, so a client's outage reaches the people who look after that client instead of everyone.
Send a test message
The dashboard posts a test into the chat while you set it up, so a wrong chat id is caught before the first real outage.
Keep the bot token out of sight
The token is stored encrypted, and because it sits in the request URL that URL is redacted before the attempt shows up under History & Logs → Alerts.
Teams that run their monitoring on Uptimeify
Minutes to set up. Then it runs on its own.
1. Create the bot
Message BotFather in Telegram, send the new bot command, and copy the token it hands back.
2. Add it and find the chat id
Add the bot to the channel or group, or start a chat with it, then read the chat id from a helper bot or the getUpdates endpoint.
Bot token
123456789:AAF...Stored encrypted
3. Paste both into Uptimeify
Add the token and the chat id as a Telegram channel, assign the monitors it covers, and send the test message.
Before you connect Telegram.
A numeric id for a person, a supergroup id starting with minus one hundred, or a public channel name with an at sign in front. All three are accepted as they are.
No. It only calls the send message endpoint of the Bot API. Nothing in the integration reads a chat, and the bot needs no privileged mode in your group.
No. Your quota covers monitors and the monthly SMS and voice allowance. Alerts over Telegram, email, webhook or Slack do not draw on it.
Encrypted in the channel configuration. The Bot API carries the token in the request URL, so that URL is redacted before the attempt shows up under History & Logs → Alerts.
As soon as the outage is confirmed. How many re-checks that takes is yours to set per package, which is the same setting that keeps a single slow response from waking anyone.
Every alert, where your team already works.
Connect Telegram once, and every confirmed outage reaches the chat that is already on your phone.