Post a confirmed outage
The message goes out once enough independent EU locations fail the check often enough in a row, both thresholds sit in your package, not on the first failed request.
Use Uptimeify with Matrix.
A bot user in your room, and every confirmed outage arrives on the homeserver you trust, federated or entirely your own.
What lands in Matrix
Everything the alert pipeline sends into Matrix is on this list, and nothing beyond it. Read it once and you know what your team will see.
Post the recovery
The same room gets the all clear, carrying the time it resolved and how many minutes the outage lasted.
Send formatted HTML with a plain fallback
Every event carries an HTML body and a plain text copy, so a client that renders neither markup nor tables still shows the whole alert.
Lay the facts out as a table
Customer, organisation, status, the error with its status code, the checking locations and the times become rows a reader can scan.
Never post the same alert twice
Each message carries a transaction id built from incident, channel and event, so a retried job is deduplicated by the homeserver itself.
Send the token in the header, not the URL
The access token travels as an Authorization header, so it does not end up in the access logs of the homeserver or any proxy in front.
Warn before certificates and domains expire
Expiring TLS certificates, expiring domains and blocklist hits reach the same room, early enough to act without a rush.
A room per monitor
Each channel carries its own room and token, so a client's outage reaches the people who look after that client instead of everyone.
Keep the access token encrypted
The bot's token is stored encrypted rather than as plain text, and only an https homeserver is accepted.
Teams that run their monitoring on Uptimeify
Minutes to set up. Then it runs on its own.
1. Create a bot user
On your homeserver, matrix.org or one you run yourself, create a user for the alerts and generate an access token for it.
2. Invite it and take the room id
Invite the bot into the room the alerts should land in and copy that room's id.
Access token
syt_dXB0aW1laWZ5_xxxxStored encrypted
3. Enter all three in Uptimeify
Add homeserver URL, room id and token as a Matrix channel, assign the monitors it covers, and send the test message.
Before you connect Matrix.
Any of them, as long as the address is https. matrix.org, a Synapse or Conduit instance of your own, or one your client federates with, all speak the same client API this uses.
No. Every message carries a transaction id built from the incident, the channel and the event, and a homeserver that sees the same id twice keeps the first message. Repeated reminders use a time bucket, so they still arrive.
In the Authorization header, never in the URL. A token in the query string would be written into the access logs of the homeserver and of every proxy in between.
No. Your quota covers monitors and the monthly SMS and voice allowance. Alerts over Matrix, email, webhook or Slack do not draw on it.
The attempt shows up under History & Logs → Alerts with the status code the homeserver returned, and a hanging one is cut off after fifteen seconds so it cannot stall the alerts queued behind it.
Every alert, where your team already works.
Connect Matrix once, and every confirmed outage reaches the room on the homeserver you trust.