Product
Alerts and integrations
Routed through EU infrastructure to Slack, Telegram, Google Chat, or email. Every delivery attempt tracked — so you know alerts arrived.
Hosted in the EU
GDPR-friendly by design
No US cloud in the data path
How it works
- Alerts are triggered on incidents
- Sent via configured notification channels
- Multiple integrations per channel
- Optional cooldowns prevent alert spam
How it works in detail
Notification channels
- A notification channel is the layer between a monitor and the places alerts are sent.
- A channel can include email recipients and multiple integrations.
- The same monitor can notify the channels assigned to it.
Alert triggers
- DOWN alerts are sent when an incident is opened.
- RECOVERY alerts are sent when the incident is resolved.
- Recovery alerts can be disabled per channel when a team only wants failure notifications.
Cooldowns and ordering
- Cooldowns help prevent repeated alerts while the same problem is still active.
- Alerts are processed asynchronously, so there can be a short delay between an incident event and notification delivery.
- Delivery order usually follows the event order, but asynchronous processing means teams should treat alerts as near-real-time signals.
Delivery reliability
- Delivery attempts are tracked so failed notifications can be inspected.
- If an integration rejects a request, Watchcat records the failure instead of hiding it.
- Retry behavior is conservative, so delivery history remains clear instead of silently masking repeated failures.
Why it matters
- Cooldown periods prevent repeated pages while the same outage is still active
- Every delivery attempt is logged — see if the Slack message arrived, not just that it was sent
- Recovery alerts fire automatically when the service comes back — no manual close needed
Integrations
-
Slack
-
Discord
-
Telegram
-
Google Chat
- Webhooks
Start monitoring for free.
5 monitors free · no credit card required