Alerts worth reading
Real outages, not blips.
- A failed check is repeated before it counts
- Announced once it has lasted 9 minutes; shorter blips are only recorded
- "Back up after 14 min" when it answers again
- One message when a server takes many sites down
- Quiet hours hold warnings at night; outages still come through
client-shop.com.au412 ms
law-firm.co238 ms
dental-clinic.com690 ms
More than up or down
Everything that breaks a site, watched.
SSL certificates
Expiring within 14 days, or already warning visitors.
Domains
Registration expiring within 30 days, nameservers changed.
Slow pages
Slower than your limit for 30 minutes.
Vulnerabilities
Plugins, themes and app packages with known flaws.
Fatal errors
The critical-error page, with the file that caused it.
Digest
Everything open, daily or weekly.
Where alerts go
The place you already look.
01
Telegram
On your phone in a minute.
02
Slack or Discord
A channel your team already reads.
03
Webhook
Signed JSON for your own tools, Zapier, n8n or Make.
FAQ
Questions
How often are sites checked?+
Every 5 minutes. A failed check is retried after a few seconds before it counts as down.
Will I get woken up by short blips?+
No. Downtime is announced after 9 minutes and slowness after 30; shorter problems are recorded in the history, and you only get a recovery message for problems you were told about.
Where do the alerts go?+
Slack, Discord, Telegram or a signed webhook, with quiet hours and a daily or weekly digest. Email alerts are not available yet.
Does monitoring need the plugin?+
Uptime, SSL and domain checks run from outside. The connector adds fatal errors, versions and security findings.
Can I monitor apps?+
Yes. Node.js and Laravel apps get uptime, health checks and dependency vulnerability alerts.
Keep reading
Related
The sites keep running.
So do you.
Connect your first site in two minutes. Free during launch.