Alerts
Alert channels
Where StatusTick sends incident alerts: email, Slack, Microsoft Teams, Discord, Telegram, PagerDuty and webhooks, and how delivery, retries and acknowledging work.
An alert channel is a destination for incident alerts. Admins add channels in the organization settings, send a test message, and choose which channels each incident setting uses.
Channels
| Channel | What you need |
|---|---|
| Verified email addresses | |
| Slack | An incoming webhook URL for the channel |
| Microsoft Teams | A webhook URL for the Teams channel |
| Discord | A channel webhook |
| Telegram | A private or group chat to connect |
| PagerDuty | An Events API v2 integration |
| Webhook | Any HTTPS URL you control |
For phone, SMS and push paging, connect PagerDuty.
What an alert contains
Alerts are sent when an incident opens and when it resolves. Each alert says which monitor failed, the target, the failing regions, the error and when it started, with links to the incident and to acknowledge it. Acknowledging from the link stops escalation.
Webhooks
StatusTick sends a JSON POST to your URL when an incident opens or resolves. You can protect the endpoint with one of these:
- no authentication,
- a bearer token,
- HTTP basic authentication,
- an API key in a header you choose.
Webhook URLs must be public. StatusTick refuses private and internal addresses.
Delivery and retries
If a channel answers with a network error or a 5xx status, StatusTick retries up to 3 times with a growing delay. A 4xx answer (except 429) is not retried, because it usually means the channel is set up wrong. Every attempt is stored for 30 days, so you can see whether an alert was delivered.
Last updated 28 Sept 2026