The channel that is on for everybody. List as many recipients as you need; the message names the monitor, the check that failed and the value that broke the threshold.
You configure: Recipients
Built in Europe. Monitoring worldwide.
Notification channels for uptime alerts
An outage is only useful information once it reaches somebody. Pulsitor delivers every incident to fourteen destinations — from e-mail and SMS to PagerDuty, Splunk and a webhook you write yourself.
One incident, every channel you turned on
A notification channel is a destination an incident is sent to. Each monitor carries its own set, so the production site can page an on-call engineer through PagerDuty while a staging box only drops a line into a chat room. Every channel receives the same three messages: the incident opening, a reminder every 12 hours for as long as it stays open, and the resolution. The tokens and webhook URLs a channel needs are stored encrypted at rest and decrypted only at the moment a notification is dispatched.
How an alert reaches you
Four rules stand between a failed check and your phone.
Confirmed before it is sent
More than one monitoring region has to agree the target is down before anything leaves. A single node losing its route to your server never wakes anybody up.
Opened and resolved, both
You are told when the incident starts and again when it clears, so nobody has to open the dashboard to find out whether it is still burning.
Reminders while it is still open
An unresolved incident keeps reminding you every 12 hours through the same channels. A long outage cannot quietly fall off the radar.
Per monitor, not per account
Channels are enabled on the monitor, so the noisy internal service and the customer-facing checkout never have to share one alerting policy.
Every channel Pulsitor can alert you on
Fourteen destinations. No plugin to install, no agent to run — each one needs a credential you already have.
SMS
Paid plansFor the outage nobody should sleep through. Sent to the numbers you list and worded short enough to be read straight off a lock screen.
You configure: Recipients
Slack
Paid plansAn incoming webhook posts into the channel you pick. Trigger, reminder and resolution all land in the same place your team is already watching.
You configure: Webhook URL
Discord
All plans, Free includedThe one chat integration that is free on every plan. Point Pulsitor at a channel webhook and your server sees the incident as it opens.
You configure: Webhook URL
Telegram
Paid plansYour own bot, your own chat or group. Nothing is routed through a shared Pulsitor bot, so the messages never leave an account you control.
You configure: Bot token, Chat ID
Google Chat
Paid plansAn incoming webhook into a Chat space, for teams whose whole working day already happens inside Google Workspace.
You configure: Webhook URL
Microsoft Teams
Paid plansAn incoming webhook into a Teams channel, so the incident shows up next to the conversation the outage is about to start.
You configure: Webhook URL
Mattermost
Paid plansSelf-hosted chat gets the same treatment as the hosted ones: one incoming webhook URL and the channel is live.
You configure: Webhook URL
Pushover
Paid plansPush straight to a phone, with Pushover's own priority and retry handling stacked on top of ours.
You configure: Application token, User key
Pushbullet
Paid plansPush to every device signed into your Pushbullet account, desktop browsers included.
You configure: Access token
Webhook
Paid plansA JSON POST to any URL you control. The escape hatch for everything this list does not cover — a ticketing system, an internal bot, a script that restarts the box.
You configure: Webhook URL
Zapier
Paid plansA catch hook that hands the incident to Zapier, and from there to whatever you have already wired up there.
You configure: Webhook URL
PagerDuty
Paid plansAn Events API routing key. Incidents open and resolve on your PagerDuty service, so the rotation and escalation policy you already maintain does the paging.
You configure: Routing key
Splunk
Paid plansHTTP Event Collector. Every trigger, reminder and resolution lands in your index next to the rest of your operational data.
You configure: Webhook URL, HEC token
Notifications at a glance
The numbers behind the alerting, in one place.
| Property | Value |
|---|---|
| Notification channels | 14 |
| Configured per | Individual monitor |
| Events sent | Incident opened, ongoing reminder, incident resolved |
| Ongoing reminder interval | Every 12 hours until resolved |
| Before an alert is sent | Confirmed from more than one of 5 regions |
| Free plan channels | E-mail, Discord |
| Paid plan channels | All 14, from EUR 6 per month |
| Credential storage | Encrypted at rest, inside the EU |
Notification questions
What people ask before they wire up the first channel.
Which notification channels are free?
E-mail and Discord work on the Free plan. The other twelve — SMS, Slack, Telegram, Google Chat, Microsoft Teams, Mattermost, Pushover, Pushbullet, webhook, Zapier, PagerDuty and Splunk — need any paid plan, which starts at EUR 6 per month.
Can one monitor alert several channels at once?
Yes. Channels are switched on per monitor and any number of them can be active together. One incident is fanned out to every channel that monitor has enabled.
Do I get a notification when the outage is over?
Yes. Every channel receives three kinds of message: the incident opening, a reminder every 12 hours for as long as it stays open, and the resolution when the check recovers.
How do you avoid waking me up for nothing?
An alert only leaves once more than one monitoring region agrees the target is down. A routing problem between a single node and your server never turns into a notification.
Where are my tokens and webhook URLs stored?
Encrypted at rest in our database inside the European Union, and decrypted only at the moment a notification is dispatched. Telegram, Pushover and PagerDuty all use credentials issued by you, so access can be revoked on your side at any time.
Wire up your first channel
Create a monitor, tick the channels that should hear about it, and the next incident finds you wherever you already are.
Get started