EN
English Français
Start your station
Help center Stream Monitoring

Stream Monitoring

9 min read Last updated: November 16, 2026

CloudRadio checks the health of your streams every minute and reports their status in real time.

How it works

Every minute, CloudRadio opens your stream from four locations (Canada, the US East coast, France, and Australia) and decodes real audio. Each check records the result, the connection time, and any error.

A check only counts as failed when most of the locations that answered agree. If one region can't reach your stream, the monitor page shows it, but it does not mark your stream down.

A stream must fail 3 consecutive checks (about 3 minutes) before its status changes. This prevents false alerts from brief network hiccups. Flatlined audio is confirmed over about 10 minutes, and static or a constant tone over about 15 to 20 minutes.

Stream statuses

StatusMeaning
OperationalThe stream is healthy and broadcasting audio
DownThe stream can't be reached or played (connection failed, timed out, server error, stream full)
Dead airThe stream is online but broadcasting silence
Flatlined audioThe stream is online, but the audio is stuck at one constant quiet level
Static detectedThe stream is online, but it broadcasts only static or hiss
Tone detectedThe stream is online, but it broadcasts only one constant tone
UnknownNo checks performed yet

Static and a constant tone count as dead air: each opens a dead-air incident and sends an alert like any other. See Static detection and Tone detection.

On the monitor page, the status card also shows what each location saw on the latest check, such as Up, Down, No source, or Dead air, with its connection time.

Static detection

Static can be loud, so the silence checks can miss it. CloudRadio also watches for streams that broadcast only static or hiss. When a stream carries steady noise for about 15 to 20 minutes, its status changes to Static detected, a dead-air incident opens, and you get an alert. The incident stays open until the audio shows normal variation again. A loud moment does not end it.

Static detection is on by default. Turn it off for a stream whose steady noise is normal, for example a radio scanner that sits on hiss between transmissions.

To turn it off, open the monitor, go to the Settings tab, and in the Audio checks card switch Static detection off. An open static incident closes right away.

Silence and outages keep alerting you while it is off, and so does tone detection.

Tone detection

A tone can be loud, so the silence checks can miss it. CloudRadio also watches for streams that broadcast only one constant tone, such as a test tone or the tone some network feeds play between shows. When a stream carries a steady tone for about 15 to 20 minutes, its status changes to Tone detected, a dead-air incident opens, and you get an alert. The incident stays open until your programming comes back. A loud moment does not end it.

The most common cause is a network or affiliate feed that plays a tone between shows. To avoid dead air during those hours, fill them with your own programming or AutoDJ.

Tone detection is on by default. Turn it off for a stream where the tone is intentional, for example a station that relays a network feed and is fine airing its tone between shows.

To turn it off, open the monitor, go to the Settings tab, and in the Audio checks card switch Tone detection off. An open tone incident closes right away.

Silence and outages keep alerting you while it is off, and so does static detection.

Supported streams

You can monitor any publicly accessible audio stream:

  • Icecast servers
  • Shoutcast v2 servers (Shoutcast v1 servers are not supported)
  • HLS (HTTP Live Streaming) endpoints
  • Other HTTP audio streams

CloudRadio detects the server type when you add a stream URL.

Add a stream

  1. Go to Monitoring in the sidebar.
  2. Click Add monitor.
  3. Enter a Name and the Stream URL.
  4. Leave Notify me by email when this stream goes down on to get alerts at your account email.
  5. Click Monitor stream.

If the URL serves several streams, you're asked to pick one. The first check runs within a minute.

Auto-monitored streams

When you create a hosted radio, or a CloudRadio One station with HLS, a monitor is created automatically. You don't need to add these manually. See Radio Auto-Monitoring.

Auto-created monitors cannot be deleted while the service is active.

Check now

When your stream has a problem, a Check now button appears in the status card on the monitor page. It runs an immediate check, so you can confirm recovery after a fix without waiting for the next scheduled one.

What the monitor page shows

The Overview tab of a monitor shows:

  • The status card, with the uptime bar for the last 60 checks (about one hour) and the result from each location
  • The connection time chart, one line per location
  • Signal quality for the last hour: sampled loudness, peak, noise floor, dynamics, and Stereo phase
  • The Incidents (last 90 days) summary
  • The certificate expiry countdown for HTTPS streams

Raw check results are kept for about 7 days. Incidents are kept permanently and are what uptime is calculated from. See Incidents & Uptime.

Signal quality readings

Each check measures a short sample of the decoded audio. Because one sample is only a moment of your stream, every tile reads all the checks from the last hour, not the latest check. Peak, noise floor and dynamics are measured on the audio mixed down to mono; the levels shown are medians, in dB relative to digital full scale (0 dB is the loudest a digital signal can be). Loudness is measured on both channels, in LUFS.

ReadingWhat it measuresVerdicts
Sampled loudnessLoudness in LUFS (loudness units relative to full scale), the unit loudness targets use: streaming services aim for about -14 to -16 LUFS, EBU R 128 broadcast for -23 LUFS. Each check takes one 0.4 second measurement, about one a minute, with the BS.1770 weighting and gating a loudness meter uses. Typically within 1 LU of a continuous loudness meter. A mono stream reads about 3 LU higher than a meter in mono mode, because it is measured as heard on stereo devices.No verdict: the right level depends on where your audio plays. With fewer than 20 measurements above silence in the hour, the tile shows Not enough readings. When most of the hour is far quieter than its loudest moments (short loud bursts between long quiet stretches), a sample a minute can't estimate it, and the tile shows Too variable to estimate.
PeakThe highest sample level reached.Good, Over 0 dB or Distorted (see below)
Noise floorThe level of the quietest moments.Clean at -45 dB or lower, Noisy above -45 dB. Shown without a verdict unless the hour had real gaps (peak at least 30 dB above the average level), because continuous music has no quiet moments to judge.
DynamicsThe gap between peak and the average (RMS) level of the mono mix.No verdict: the number is there for reference.

Sampled loudness is an estimate for comparing your stream with a target, not a replacement for a loudness meter, especially on programme with wide swings in level. It does not measure loudness range (LRA) or true peak. An inverted channel doesn't lower it: the two channels are measured separately, not mixed.

A peak reading of 0 dB doesn't trigger a warning on its own. The Peak number stops at 0 dB; the two warnings below look at the decoded audio before that cap, and only when the average (RMS) level of the mono mix is above -20 dB, so quieter audio and pauses are never judged.

Over 0 dB means the decoded audio spends more than 1 second of every minute past 0 dB on either channel. Each check times the stretches of decoded audio that go over, and the tile adds them up against all the audio measured in the hour, once that audio reaches 15 seconds. MP3 and AAC encoding pushes peaks that sit right at 0 dB slightly past it, and listeners' players then clip them. The usual cause is a limiter or processor ceiling set to 0 dB: set it to -1 dB (-2 or -3 dB for streams at 64 kbps and below, where encoding overshoots more). Loud streams with a -1 dB ceiling measure well under the 1 second rate. Without a limiter, lower your encoder input level instead.

Distorted means runs of consecutive samples stuck at the same peak value, the sign of an overdriven input or hard clipping. Lower your encoder input level in your studio.

Light clipping, where only the loudest peaks are cut, can read Good: after MP3 or AAC encoding it looks like a limiter's normal overshoot. Clipping before an MP3 or AAC encoder can read Over 0 dB or Distorted, depending on the codec and how hard it clips.

Stereo phase compares the left and right channels over the last 30 minutes:

  • Phase correct: no polarity inversion found.
  • Phase inverted: in at least 80% of readings, one channel is the other upside down. The stream sounds normal in stereo but thin or nearly silent on mono speakers. A What this means link explains how to check and fix it.
  • Mono stream: most readings come from a mono source, which can't be inverted.
  • Not enough readings: fewer than 20 readings in the last 30 minutes, or the stream is not currently up.

When at least 80% of a stream's phase readings over the past 24 hours are inverted, CloudRadio sends a phase alert while the stream is up. The stream needs about 12 hours of readings within the past 24 hours first, and time the stream is down or unchecked doesn't reset the count. A single inverted show doesn't send it: the alert is for a stream that stays inverted, like a cable wired wrong or a polarity or phase invert setting left on for one channel in your audio processor, encoder or sound card mixer. It goes to the same recipients and channels as your other alerts: email, plus any Discord, Slack or webhook channel you set up. There is no setting to turn on, and it is not sent again until fewer than half of the past 24 hours of readings are inverted.

These readings don't change your stream's status or open incidents, and the other tiles never send alerts. Dead air, flatlined audio, static, and constant tones are detected separately (see Stream statuses above).

Was this helpful?

Still need help?

If you couldn't find the answer, our team is here to help.

Open Support Ticket