
Monitor
Website down alerts that arrive before your customers’ emails do.
A website-down alert is exactly what it sounds like: the probe that was answering suddenly did not, and the next minute you know. SiteGuardian sends one email per outage and one recovery email per come-back. Your inbox stays quiet when nothing is wrong.
- One loud email the minute the URL stops answering. No dashboard login required.
- Probes every minute on the Pro tier; every five minutes on Starter and Lifetime.
- Probes from multiple regions so a single CDN hiccup does not falsely trip the alert.
- Recovery email the second the URL answers again. So you know when to stop worrying.
- No app to install on your site. SiteGuardian watches from the outside, like a visitor.
How it works
Setup, in three beats.
Step 01
Add the URL that would ruin a Tuesday afternoon
Paste your home page or the page that sends revenue. The one you would not want offline. Pick a slow threshold in plain English. SiteGuardian starts probing inside the next minute.
Step 02
Add the second URL that matters
Any shop has more than one page worth watching. /about, /contact, a landing page from a recent campaign. SiteGuardian treats each URL independently and routes outputs to the same inbox.
Step 03
Let your inbox be the dashboard
When something stops answering, you get one email. When it recovers, you get another. Boring safeguard passes its own test: set up once, the inbox stays quiet for weeks at a time.
What the alert actually says
One email. One URL. One timestamp.
Your URL https://example.com/ answered with HTTP 502 at 14:38 UTC. The probe will retry in 60 seconds.Frequently asked
The website down alerts questions, answered flat.
Frequently asked
Related reading
Keep exploring.
Try it
Start monitoring my site.
Starter is $19 a month — one site, ten URLs, every-five-minute checks. Pro is $39 a month — three sites, fifty URLs, every-minute checks. Lifetime is $299 paid once and stays yours with every future update included.
Stay updated
Want us to email you when we ship a feature for this use case?