Post 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 Rocket.Chat.
One incoming webhook on the server you run yourself, and every confirmed outage lands in the channel your team already watches.
What lands in Rocket.Chat
Everything the alert pipeline sends into Rocket.Chat is on this list, and nothing beyond it. Read it once and you know what your team will see.
Post the recovery
The same channel gets the all clear as soon as the check is green again, under its own heading rather than as another alarm.
Speak the Slack compatible payload
The incoming integration receives the same shape Rocket.Chat already accepts from Slack, so no script is needed on the receiving side.
Say what actually broke
Site, URL, the error in plain language, incident type, status code, response time and the checking locations follow the heading.
Reach your own server
Any https host is accepted, since Rocket.Chat is yours to run, and the address is checked against internal targets before it is called.
Warn before certificates and domains expire
Expiring TLS certificates, expiring domains and blocklist hits reach the same channel, early enough to act without a rush.
A channel per monitor
Each channel is its own webhook, 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 channel while you set it up, so the first real alert is not the first delivery attempt.
Keep the webhook URL out of sight
The URL carries the token, so it is stored encrypted and shortened to its origin before the attempt shows up on the Alerts tab under History & Logs.
Teams that run their monitoring on Uptimeify
Minutes to set up. Then it runs on its own.
1. Create the incoming integration
In Rocket.Chat open Administration, then Integrations, then New, and choose Incoming.
Webhook URL
chat.yourcompany.com/hooks/xxxx/yyyyStored encrypted
2. Enable it and pick the channel
Turn the integration on, choose the target channel, and copy the webhook URL it shows.
3. Paste it into Uptimeify
Add the URL as a Rocket.Chat channel, assign the monitors it covers, and send the test message.
Before you connect Rocket.Chat.
No. The payload is the Slack compatible one Rocket.Chat understands out of the box, so the integration works with its default script left untouched.
That is the case it is built for. Any https host is accepted, and the address is resolved and checked against internal and loopback targets before a request is sent.
Yes. Every channel is its own webhook, and you assign monitors and clients to it. A client's outage then reaches the people who look after that client, not everyone.
No. Your quota covers monitors and the monthly SMS and voice allowance. Alerts over Rocket.Chat, email, webhook or Slack do not draw on it.
The attempt lands on the Alerts tab under History & Logs with the status code your server returned, and a hanging endpoint is cut off after fifteen seconds so it cannot stall the alerts queued behind it.
Every alert, where your team already works.
Connect Rocket.Chat once, and every confirmed outage reaches the channel on the server you run yourself.