What notification channels does Pingbreak support?

Updated

Pingbreak sends downtime alerts through Twitter Direct Message by default, and you can add Slack, Discord, Mattermost, email, or a Webhook as extra channels. Alerts are described as instant, and the service checks each monitored URL every minute. A Twitter account is required to join the open beta, and Twitter permissions are needed so Pingbreak can send you messages.

Notification channels at a glance

Channel How it works Notes
Twitter DM Pingbreak's robot contacts you privately by Direct Message Default channel; Twitter account and permissions required
Slack Configure as an additional notification Optional, set up alongside the default
Discord Configure as an additional notification Optional
Mattermost Configure as an additional notification Optional
Email Configure as an additional notification Optional
Webhook Configure as an additional notification Optional; useful for routing alerts into your own tooling

The wording on the site is that Twitter is the real-time alert path, while Slack, Discord, Mattermost, mail, and Webhook are "additional" notifications you can configure. So Twitter DM is the baseline you get from signing up, and the rest are add-ons you enable yourself.

What you need before configuring channels

  • A Twitter account. The open beta signup requires one, and you sign in with Twitter (a password login option also appears on the page).
  • Twitter permissions granted to Pingbreak, because the site states these are required for sending messages.
  • The URLs you want monitored. Beta testers can watch an unlimited number of URLs, checked every minute.

How to set up notifications

  1. Join the open beta and sign in. The page offers "Sign in with Twitter" and a password login; a Twitter account is required for the beta.
  2. Grant Twitter permissions when prompted. Without this, Pingbreak cannot send you a Direct Message.
  3. Confirm the default channel. Downtime alerts arrive as a private Twitter DM from Pingbreak's robot.
  4. Add extra channels. Configure Slack, Discord, Mattermost, email, or a Webhook if you want alerts somewhere other than Twitter.
  5. Verify with a real check. Because monitoring runs at a 1-minute interval, a down site should trigger an alert quickly — use that to confirm each channel actually reaches you.

Expected result: when a monitored site fails, you get an instant notification on Twitter DM and on any additional channels you configured.

Common snags

  • No Twitter permissions, no DM. The site explicitly ties message delivery to Twitter permissions, so a skipped or revoked permission is the most likely reason alerts never arrive.
  • Assuming extra channels are automatic. Slack, Discord, Mattermost, email, and Webhook are described as configurable additions, not defaults — you have to set them up.
  • Expecting sub-minute detection. Checks run every minute, so detection is at that granularity rather than continuous.

Choosing your setup

If you already live in Twitter/X, the default DM may be enough and you can stop there. If your team works in chat, add Slack, Discord, or Mattermost so alerts land where people already are. If you need alerts to feed another system — an on-call tool, a dashboard, a ticketing queue — the Webhook option is the one to configure. Email suits anyone who wants a durable record outside chat.

One caveat worth knowing: the site says the service is free and will stay free, with future updates free for beta testers, and that it does not sell personal data. It also notes Pingbreak is built by volunteers and hosted by sponsors, so treat the channel lineup as the current beta feature set rather than a contractual guarantee.