How to Get Instant Alerts When Your Website Goes Down

The worst way to find out your site is down is a client or customer telling you. By then it's already cost you time, trust, or a sale. The fix is a monitoring check that runs continuously and alerts you the second something breaks — and it's simpler to build than most people expect.

The basic monitor

The core pattern is four steps:

1. Schedule trigger — runs every 5 minutes (or however tight you want the detection window).
2. HTTP Request node — pings your site's URL and captures the response status and timing.
3. IF node — checks whether the response is an error status or the request timed out.
4. Alert branch — if it's down, fire off a Telegram and email alert simultaneously, and log the incident to a sheet for a historical record.

That's the entire architecture behind Website Uptime Monitor & Alert. Five minutes is a reasonable default; drop it to every minute for something business-critical, since the check itself costs nothing beyond a bit of execution time.

The two things people forget to monitor

Uptime is the obvious one. Two others quietly cause outages just as bad, and almost nobody sets up alerts for them until after the first time it happens:

SSL certificate expiry

An expired SSL certificate doesn't just show a warning — modern browsers block the page outright, which looks identical to a full outage from a visitor's perspective, and it happens on a predictable schedule that's easy to simply forget. A daily check against your certificate's expiry date, with an alert once you're inside a 14 or 30-day window, means renewal happens with time to spare instead of in a panic. See SSL Certificate Expiry Monitor.

Domain expiry

Rarer, but far worse when it happens — a lapsed domain registration can take a site offline for days while you scramble to re-register it, sometimes to someone else entirely if a squatter grabs it first. A monthly automated check against your domain's expiry date closes this gap permanently. See Domain Expiry Monitor.

Closing the loop: telling people what's happening

If you run anything with real users, an outage alert to you is only half the job — the other half is telling affected users what's going on before they start opening support tickets. An automation that updates a public status page the moment an incident is detected (and marks it resolved when things recover) turns "why is nothing working and nobody's telling me" into "oh, they already know and it's being fixed." See Incident Status Page Updater.

Putting it all together

Wire up all four and you've covered the three most common ways a site quietly goes dark — downtime, SSL expiry, and domain expiry — plus the communication layer that keeps users informed while you fix it. None of these run on paid infrastructure beyond your own n8n instance; they're exactly the kind of "set it up once, forget about it" automation that's worth the 15 minutes it takes to import and connect.