Alerts that check twice before they wake anyone.
False alarms train people to ignore alerts. StatusTick reads every failed check before it alerts, knows the difference between down, slow and blocked, and sends the alert where your team already works.
Four checks against false alarms.
Failures in a row.
Open an incident after 1 to 10 failed checks, and resolve it after the good checks you choose.
Blocked is not down.
When a firewall or bot protection answers instead of your site, the monitor shows Blocked.
Slow is not down.
Answers over your threshold show as Degraded, with their own alert rules.
Maintenance windows, one-off or repeating, in your time zone. No incidents during planned work.
Where your team already works.
An alert policy sends each step to the channels and the on-call people you choose.
Email
Verified addresses, a clear subject and one link to act.
Slack
An incoming webhook to any channel.
Microsoft Teams
A webhook to a Teams channel.
Discord
A channel webhook.
Telegram
A private or group chat.
PagerDuty
Events API v2, for teams that page through PagerDuty.
Webhooks
JSON to your endpoint, with bearer, basic or API-key authentication.
Alerts you can act on.
The facts in the message.
Monitor, target, the error and the start time, with a link to the incident.
Acknowledge from the alert with one link, and escalation stops.
If nobody acknowledges in time, StatusTick escalates to the next channels, up to 3 times.
Failed deliveries are retried up to 3 times, and every attempt is kept for 30 days.
Questions.
- How does StatusTick know a firewall blocked the check?
- It looks for typical block answers, such as a 403 or 429 with WAF headers or a bot challenge page. A normal 403 from your app still counts as down if you did not expect it.
- Can I get an alert when my site is slow?
- Yes. Set a slow-response threshold on the monitor. Slow checks show as Degraded.
See it on your own product.
Point it at your product tonight. In the morning you’ll see what happened while you slept, and which of it needed you.