Push 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 Gotify.
Push notifications on a server that is entirely yours, with an app token per channel and nothing leaving your infrastructure but the message.
What lands in Gotify
Everything the alert pipeline sends to Gotify is on this list, and nothing beyond it. Read it once and you know what your team will see.
Push the recovery
The all clear arrives on the same server at a low priority, because it is news and not an emergency.
Set the priority from the severity
An outage arrives at eight, a warning at five and a recovery at two, so your client can decide what deserves a sound.
Say what actually broke
The title names the site and its state, the message carries the error, status code, response time and the checking locations.
Stay on your own server
The server URL is yours, and it is resolved and checked against internal targets before anything is sent to it.
Keep the app token out of the log
The token travels in the query string, so the recorded URL is shortened to its origin before the attempt shows up under History & Logs → Alerts.
Warn before certificates and domains expire
Expiring TLS certificates, expiring domains and blocklist hits reach the same server.
An application per monitor
Each channel carries its own app token, so a client's outage arrives under the application that belongs to that client.
Send a test message
The dashboard pushes a test while you set it up, so a wrong token is caught before the first real outage.
Teams that run their monitoring on Uptimeify
Minutes to set up. Then it runs on its own.
1. Create an application
In your Gotify server create an application for the monitoring alerts.
App token
AxxxxxxxxxxxxxxxStored encrypted
2. Copy the app token
Copy the token the application shows, together with the base URL of your server.
3. Paste both into Uptimeify
Add server URL and token as a Gotify channel, assign the monitors it covers, and send the test message.
Before you connect Gotify.
Yes, since the message is pushed to it from outside. The address is resolved and checked against internal and loopback targets first, so it cannot be pointed at something inside our network.
From the severity. An outage arrives at eight, a warning at five and a recovery at two, which is what lets your client decide what deserves a sound at night.
Encrypted in the channel configuration. It travels in the query string, which is why the recorded URL is shortened to its origin before the attempt shows up under History & Logs → Alerts.
No. Your quota covers monitors and the monthly SMS and voice allowance. Alerts over Gotify, email, webhook or Slack do not draw on it.
Yes. Every channel carries its own app token, and you assign monitors and clients to it. A client's outage then arrives under the application that belongs to that client.
Every alert, where your team already works.
Connect Gotify once, and every confirmed outage arrives on the push server you run yourself.