Uptime alerts that follow confirmed incidents and recoveries

UptimeSure separates check results from notification delivery. Once a monitor crosses its confirmation threshold, an incident opens and linked alert channels are queued durably so a transient notification failure does not silently disappear.

An alert association links one monitor to one notification channel. V1 supports Email, Telegram, Webhook, Slack and Discord, plus per-link delay and recovery controls.

A notification transport failure is recorded as retry or failed according to the bounded retry policy. It does not rewrite the monitor’s actual UP/DOWN result.

DOWN delivery is deduplicated per incident/channel/event. Recovery can suppress an unsent delayed DOWN and queue an UP notification when enabled. Delivery re-checks maintenance before sending a delayed DOWN.

What UptimeSure checks

Channel configuration validation
Durable alert queue state
Delivery retry state
Recovery preference
Maintenance suppression

Common use cases

Operator chat notifications
Email operations inbox
Automation webhooks
Different delays for noisy or high-priority channels

Configuration

Channel type and destination
Monitor association
Delay seconds
Send recovery toggle

Alerts and recovery

V1 notification destinations are Email, Telegram, Webhook, Slack and Discord. Quiet hours and multi-stage escalation policies are not V1 claims.

Example

Example: send an immediate webhook on confirmed DOWN and an email after a short delay; send recovery when the incident closes.

Frequently asked questions

Does UptimeSure retry transient alert failures?

Yes. V1 uses a bounded durable retry policy.

Can alerts be suppressed during maintenance?

Yes. DOWN delivery is suppressed for active maintenance, including a window that begins after enqueue but before send.