Push a confirmed outage
The push 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 Pushover.
A push straight to your phone, without a chat tool in between, and loud enough to get through quiet hours when it has to be.
What lands on your phone
Everything the alert pipeline sends to Pushover 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 device, at normal priority, because it is news and not an emergency.
Break through quiet hours when it matters
An outage, an expiring certificate and a slow site go out at high priority; warnings and recoveries stay at normal and respect silence.
Format the message
The push carries a formatted body, so site, error, status code and locations are readable at a glance rather than one long line.
Link the screenshot
When the failing check captured a screenshot, the message links it, since the push API takes attachments only in a form we do not use.
Add a dashboard button
Every push carries a link straight to the monitor, so the next step is one tap away instead of a search.
Warn before certificates and domains expire
Expiring TLS certificates, expiring domains and blocklist hits reach the same device with their own wording.
Retry a transient failure
A temporary failure is retried on its own ladder, and the attempt is logged as retrying rather than as a lost alert.
Keep user key and token encrypted
Both the user key and the application token are stored encrypted rather than as plain text.
Teams that run their monitoring on Uptimeify
Minutes to set up. Then it runs on its own.
1. Take your user key
In the Pushover app or on the website, copy the user key of the account that should receive the alerts.
Application token
axxxxxxxxxxxxxxxxxxxxxxxxxxxxxStored encrypted
2. Create an application
Register an application in Pushover and copy the API token it hands you.
3. Paste both into Uptimeify
Add user key and token as a Pushover channel, assign the monitors it covers, and send the test push.
Before you connect Pushover.
Only when it should. Outages, expiring certificates and a site gone slow go out at high priority, which bypasses quiet hours. Warnings and recoveries stay at normal priority and respect them.
Because Pushover accepts attachments only in a request format we do not use for this send. The picture is linked from the message instead, one tap away.
No. Your quota covers monitors and the monthly SMS and voice allowance. Alerts over Pushover, email, webhook or Slack do not draw on it.
Yes. Every channel carries its own user key, and you assign monitors and clients to it. A client's outage then reaches the person on call for that client, not everyone.
A temporary failure is retried on its own ladder and logged as retrying, not as a lost alert, so a device that briefly dropped off does not swallow the outage.
Every alert, on the phone in your pocket.
Connect Pushover once, and every confirmed outage lands on the phone in your pocket, loud when it has to be.