One clear alert, where you'll actually see it.

An alert is only useful if it reaches the right person and says what's wrong. Pingerer sends one clear message per incident, where your team already is.

Channels

• Email, to you or your whole team.
• Slack, Discord and Microsoft Teams, posted to the channel you choose.
• Telegram, to a person or a group.
• SMS, to verified numbers, with texts included each month on the Paid plan, and phone calls for downtime.
• ntfy and Pushover, as push notifications on your phone, at high priority for downtime.
• PagerDuty and Opsgenie: an incident opens one there, and it resolves itself when the site recovers.
• Webhooks, signed with a secret so you can trust them, for anything else.

Rules that fit how you work

• Send each site's alerts to different channels, or everything everywhere.
• Choose which events go where: downtime, slowness, expiring certificates and domains, DNS changes, email setup and missed heartbeats.
• Escalation: if nobody acknowledges an incident within the time you set, alert someone else.
• On-call schedules (Paid): your team takes turns, with overrides for swaps and holidays, and alerts go to whoever is on call.
• Quiet hours: hold the less urgent alerts overnight. Downtime and missed heartbeats still get through.

Alerts in plain English

Every alert says what failed, from where, since when, and what that usually means. Acknowledge from the email or the text with one tap, so the rest of the team knows someone is on it.

Read more: Alerts and channels and SMS alerts.