Help Center Stream Monitoring

Stream Monitoring

2 min read

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

How It Works

The monitoring system connects to your stream URL, verifies that the server is responding, and checks that audio is being broadcast. Each check records the result, response time, and any errors.

A stream must fail 3 consecutive checks before its status changes. This prevents false alerts from brief network hiccups.

Stream Statuses

Status Meaning
Up Stream is healthy and broadcasting audio
Down Stream is unreachable (connection failed, timed out, or server error)
Dead Air Stream server is online but broadcasting silence
Unknown No checks performed yet (waiting for first check)

When a stream starts failing, you’ll see progress indicators like “1 of 3 checks failed” before the status changes.

Supported Stream Types

You can monitor any publicly accessible audio stream:

  • Icecast servers
  • Shoutcast v1 and v2 servers
  • HLS (HTTP Live Streaming) endpoints
  • HTTP streams

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

Add a Stream

  1. Go to Monitoring from the main navigation
  2. Click Add Stream
  3. Enter the stream URL
  4. Give it a name
  5. Click Save

The first check runs within a minute of adding the stream.

Auto-Monitored Streams

When you create a hosted radio or an AutoDJ station with HLS output, a monitor is created automatically. You don’t need to add these manually.

Auto-created monitors cannot be deleted while the service is active. They are removed automatically when you destroy the radio or station.

Check Now

If your stream is currently down, a Check Now button appears on the stream detail page. Clicking it triggers an immediate health check so you don’t have to wait for the next scheduled interval. This helps confirm recovery faster after you’ve fixed an issue.

History

The dashboard displays the last 60 checks (roughly 1 hour of history at one check per minute). All check data is retained for 365 days in the background for incident and uptime calculations.

Was this helpful?

Still need help?

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

Open Support Ticket