Instant Alerts in Telegram, Slack and Email
Monitoring availability without delays
Explore Channels Escalation RulesWhere Your Alerts Arrive
PingKit pushes status changes to the tools your team already uses every day. Configure one or all four channels from the dashboard — no code, no webhooks to maintain.
Telegram
Send alerts to bots, groups or private chats. Configure per-project bot tokens and channel IDs directly in the UI. Typical delivery latency is under 1.2 seconds. Supports inline buttons for acknowledge and dismiss actions.
bot @PingKitAlertsBot → @your_channel
Slack
Post formatted cards into any Slack channel via Incoming Webhooks or the Slack App integration. Mentions are resolved to real users — @sre-on-call gets pinged automatically. Threaded follow-ups keep the channel tidy.
#incidents → webhook → formatted block
SMTP and SendGrid transport with DKIM verification. Digest mode bundles all events into a single daily summary, or switch to real-time for critical outages. Custom sender address and reply-to headers are supported.
SMS
Twilio andvonage backends for voice-grade reliability. SMS is reserved for P1-only events by default. Character limit awareness keeps payloads under 160 characters with truncated URLs.
+1 415 555 0192 → Twilio SID
What Your Team Actually Reads
Every alert follows a structured template that surfaces the facts first: what broke, when, and what to do next. Customize variables per integration without touching code.
Incident Opened
[P1] api.example.com — HTTP 502 since 14:23 UTC — Last healthy: 14:21:47 — Runbook: https://runbooks.internal/api-502
Includes the check name, HTTP status, first failure timestamp, last known good timestamp, and a direct link to the relevant runbook page.
Incident Resolved
[RESOLVED] api.example.com — Restored at 14:38 UTC — Downtime: 14m 53s — 3 consecutive 200 OK responses confirmed
Reports total downtime duration, the exact moment recovery was confirmed, and the number of consecutive successful checks required to close the incident.
Degraded Performance
[WARN] cdn.example.com — Response time 2.4s (threshold: 800ms) — 12 of 15 probes above SLA — Region: eu-west-1
Triggers when response time crosses the configured threshold for a sustained window. Shows probe count, threshold value, and the affected region.
Daily Digest
PingKit Daily — 2025-01-15 — 47 checks monitored — 2 incidents (1 P1, 1 P2) — Overall uptime: 99.94% — Summary: https://pingkit.io/daily/2025-01-15
Optional summary email sent at a configurable hour. Aggregates all events, uptime percentages, and links to the detailed daily report.
When No One Responds, PingKit Escalates
Define time-based escalation chains so critical incidents never sit unread. Each policy has a primary responder group, a timeout, and a secondary group that takes over automatically.
Step 1 — Primary Alert
At T+0 the alert fires to the on-call engineer's Telegram and the #incidents Slack channel. An acknowledgment button is attached; clicking it pauses the escalation clock.
T+0 → @marina.chen (Telegram) + #incidents (Slack)
Step 2 — Secondary Escalation
If no acknowledgment within the configured window (default 5 minutes for P1, 15 minutes for P2), the alert escalates to the engineering manager and adds an SMS notification to the on-call phone.
T+5min → @dmitry.volkov (Slack + SMS) + @sre-lead (Email)
Step 3 — Management Notification
After a second timeout (default 15 minutes for P1), a summary is sent to the VP of Engineering and the CTO via email and Slack, with a direct link to the live incident page and suggested actions.
T+20min → @sarah.kim (Email) + @cto (Slack DM)
Escalation policies are attached per check or per project. Each step logs its delivery receipt, so you can audit exactly who was notified and when. Missed escalations are reported in the weekly reliability review.
Instant Alerts in Telegram, Slack and Email
Monitoring availability without delays
Explore Channels Escalation RulesWhere Your Alerts Arrive
PingKit pushes status changes to the tools your team already uses every day. Configure one or all four channels from the dashboard — no code, no webhooks to maintain.
Telegram
Send alerts to bots, groups or private chats. Configure per-project bot tokens and channel IDs directly in the UI. Typical delivery latency is under 1.2 seconds. Supports inline buttons for acknowledge and dismiss actions.
bot @PingKitAlertsBot → @your_channel
Slack
Post formatted cards into any Slack channel via Incoming Webhooks or the Slack App integration. Mentions are resolved to real users — @sre-on-call gets pinged automatically. Threaded follow-ups keep the channel tidy.
#incidents → webhook → formatted block
SMTP and SendGrid transport with DKIM verification. Digest mode bundles all events into a single daily summary, or switch to real-time for critical outages. Custom sender address and reply-to headers are supported.
alerts@yourdomain.com → recipient list
SMS
Twilio and Vonage backends for voice-grade reliability. SMS is reserved for P1-only events by default. Character limit awareness keeps payloads under 160 characters with truncated URLs.
+1 415 555 0192 → Twilio SID
What Your Team Actually Reads
Every alert follows a structured template that surfaces the facts first: what broke, when, and what to do next. Customize variables per integration without touching code.
Incident Opened
[P1] api.example.com — HTTP 502 since 14:23 UTC — Last healthy: 14:21:47 — Runbook: https://runbooks.internal/api-502
Includes the check name, HTTP status, first failure timestamp, last known good timestamp, and a direct link to the relevant runbook page.
Incident Resolved
[RESOLVED] api.example.com — Restored at 14:38 UTC — Downtime: 14m 53s — 3 consecutive 200 OK responses confirmed
Reports total downtime duration, the exact moment recovery was confirmed, and the number of consecutive successful checks required to close the incident.
Degraded Performance
[WARN] cdn.example.com — Response time 2.4s (threshold: 800ms) — 12 of 15 probes above SLA — Region: eu-west-1
Triggers when response time crosses the configured threshold for a sustained window. Shows probe count, threshold value, and the affected region.
Daily Digest
PingKit Daily — 2025-01-15 — 47 checks monitored — 2 incidents (1 P1, 1 P2) — Overall uptime: 99.94% — Summary: https://pingkit.io/daily/2025-01-15
Optional summary email sent at a configurable hour. Aggregates all events, uptime percentages, and links to the detailed daily report.
When No One Responds, PingKit Escalates
Define time-based escalation chains so critical incidents never sit unread. Each policy has a primary responder group, a timeout, and a secondary group that takes over automatically.
Step 1 — Primary Alert
At T+0 the alert fires to the on-call engineer's Telegram and the #incidents Slack channel. An acknowledgment button is attached; clicking it pauses the escalation clock.
T+0 → @marina.chen (Telegram) + #incidents (Slack)
Step 2 — Secondary Escalation
If no acknowledgment within the configured window (default 5 minutes for P1, 15 minutes for P2), the alert escalates to the engineering manager and adds an SMS notification to the on-call phone.
T+5min → @dmitry.volkov (Slack + SMS) + @sre-lead (Email)
Step 3 — Management Notification
After a second timeout (default 15 minutes for P1), a summary is sent to the VP of Engineering and the CTO via email and Slack, with a direct link to the live incident page and suggested actions.
T+20min → @sarah.kim (Email) + @cto (Slack DM)
Escalation policies are attached per check or per project. Each step logs its delivery receipt, so you can audit exactly who was notified and when. Missed escalations are reported in the weekly reliability review.