To get notified when your website goes down, run a small script on a schedule that checks your site and calls your Hook.Notifier URL when the check fails. You get a push notification the moment it happens, with no paid uptime service.
Here is the whole check, in one line:
curl -sf https://yoursite.com > /dev/null || curl "https://hooknotifier.com/{IDENTIFIER}/{KEY}?object=Site%20down&body=yoursite.com%20is%20not%20responding&priority=critical"
If your site answers, nothing happens. If it does not, your phone rings. The priority=critical makes the alert cut through quiet hours, because downtime at 3am is exactly the notification that should wake you.
Run it every minute with cron
Put the check on a schedule so it watches your site around the clock.
# crontab -e
* * * * * curl -sf https://yoursite.com > /dev/null || curl -s "https://hooknotifier.com/{IDENTIFIER}/{KEY}?object=Site%20down&body=yoursite.com%20is%20not%20responding&priority=critical"
That is a full uptime monitor. Free, running on any server or Raspberry Pi you already have.
First get your URL
Your Hook.Notifier URL is https://hooknotifier.com/{IDENTIFIER}/{KEY}. Create a free account to get yours, then drop it into the script.
Already using a monitor
If you run Uptime Kuma, Healthchecks, or a similar tool, you do not need the script. Point its webhook or custom notification at your Hook.Notifier URL and downtime alerts land on your phone.
Relay it to Slack too
If your team lives in Slack, add an outgoing webhook in the dashboard. Hook.Notifier forwards the same downtime alert to your Slack channel, so you get the push on your phone and the team sees it in the channel, from one hook.
Why it matters
Downtime costs the most in the minutes before you notice. A notification the second your site stops answering turns a lost afternoon into a two minute fix.
New to this? Start with how to send yourself a native push notification.