CloudRadio alerts you when your stream goes down or starts broadcasting silence, and again when it recovers. It also warns you when your stream's stereo phase reads inverted. Alerts go by email, and optionally to Discord, Slack, or your own webhook.
Alert types
| Alert | When it's sent |
|---|---|
| Stream down | The stream can't be reached after 3 consecutive failed checks |
| Stream recovered | The stream comes back online |
| Dead air | The stream broadcasts silence for 3 consecutive checks |
| Flatlined audio | The audio stays at one constant quiet level for about 10 minutes |
| Broadcasting static | Only static or hiss comes through for about 15 to 20 minutes (see Static detection) |
| Broadcasting a constant tone | Only one steady tone comes through for about 15 to 20 minutes (see Tone detection) |
| Dead air cleared / Audio back to normal / No longer broadcasting static or a constant tone | Audio returns after dead air, a flatline, static, or a tone |
| Certificate warning | The HTTPS certificate of your stream expires in 14 days, in 3 days, and when it expires |
| Phase inverted | Your left and right channels have read out of phase for most of the past 24 hours, so mono listeners hear near-silence (see Stream monitoring) |
A new monitor sends no alerts until its stream has been healthy at least once, to avoid false alarms during setup. So a stream that is down or silent from the moment you add it shows that status on the dashboard but sends no alert: check the status after adding a monitor. Certificate warnings are advance notices: they never open an incident or affect uptime.
Turn on alerts
Monitors created automatically for your stations start with alerts off. To turn them on:
- Go to Monitoring and click a stream.
- Open the Notifications tab. A warning icon on the tab means no one gets alerts yet.
- Turn on the Account holder switch to receive alerts at your account email, or click Enable now in the warning.
Add email recipients
You can send alerts to several people (team members, engineers, on-call staff):
- On the Notifications tab, click Add recipient.
- Enter the email address and click Add email.
- The recipient must confirm their address before they receive alerts.
New addresses get a deliverability check, then a confirmation email with a link that expires in 7 days. The address shows as PENDING until the link is clicked, then ACTIVE. Only active addresses receive alerts. To remove an address, click the trash icon next to it.
Send alerts to Discord, Slack or a webhook
- On the Notifications tab, click Add webhook on the Discord, Slack and webhooks row.
- Choose Discord, Slack, or Other (JSON POST).
- Paste the Webhook URL: a Discord or Slack incoming webhook URL, or any public HTTPS endpoint.
Each webhook has its own on/off switch. If an endpoint stops accepting alerts, it is marked NOT WORKING: remove it and add it again. Webhook alerts are available on every plan.
Pause alerts
Planned maintenance? Click Pause alerts at the top of the monitor page and choose 1, 2, or 4 hours, with an optional reason. Alert emails stop for that time. Checks keep running, incidents are still recorded, and uptime is unaffected.
Unsubscribe
Every alert email has an unsubscribe link that works without logging in. If you unsubscribe as the account holder, alert emails switch off for your streams, and you can turn the Account holder switch back on any time. If an added recipient unsubscribes, their address is removed.
What alert emails contain
Each alert email includes:
- Stream name and URL
- What happened, and why when the cause is known
- What to do about it
- When it was detected
- Technical details you can forward to your host
- A link to the monitor page