Uptime alerts through ntfy
A push notification on your phone when a monitor goes down and when it is back, through ntfy.sh or an ntfy server of your own. No app store account, no SMS credits.
Northwind: API is down
timeout at https://api.northwind.example/health. 2 checks in a row, confirmed from a second location.
Setting it up
- Install the ntfy app and subscribe to a topic, on ntfy.sh or on your own server. A topic is just a name; pick one that is hard to guess, or protect it with an access token.
- In StatOSS, open the page's settings, Alerts, choose ntfy under "Add a destination", paste the topic URL (such as
https://ntfy.sh/northwind-status), add the token if the topic needs one, and save. - Press "Send a test alert" and watch the phone.
ntfy is on Hobby ($4 a month) and Pro. Email alerts are on every plan, Free included. The pricing page has the rest.
Why ntfy
ntfy is an open source push service: a phone subscribes to a topic, and anything that can make an HTTP request can post to it. For a one-person project that is the simplest route to a phone: no paging product, no SMS credits, no per-seat licence. Self-hosting the server keeps the alerts on your own machine. For a team with a rotation, PagerDuty or Opsgenie do the routing.
When an alert goes out
One alert per change of state: when a monitor goes down, when it turns slow, and when it is back, with the time, the reason, and how long it was out. A monitor counts as down after two failed checks in a row, each confirmed by a second server on another network; a single failed check sends nothing. A repeat interval sends a "still down" notice every so many minutes while an outage lasts, and nothing is sent during a maintenance window. Every kind of monitor alerts the same way: a website, an API, a port, a certificate, a cron job.