hallo@maenda.mediaContactKnowledge Base
Maenda Media
Network
HostingDomainsRadioVPS
DirectAdmin
Proxmox
Cloudflare
LiteSpeed
Imunify360
Let's Encrypt
Softaculous
JetBackup
Shoutcast
Icecast
RIPE NCC Member
Ubiquiti
Appwrite
DirectAdmin
Proxmox
Cloudflare
LiteSpeed
Imunify360
Let's Encrypt
Softaculous
JetBackup
Shoutcast
Icecast
RIPE NCC Member
Ubiquiti
Appwrite
Maenda MediaHosting since 2003

Web hosting, VPS servers and streaming from our own datacenter in Meppel. Dutch support on weekdays.

  • hallo@maenda.media
  • Nederland

Products

  • Web Hosting
  • VPS Servers
  • Managed VPS
  • Radio Streaming
  • Video Streaming
  • Stream monitoring
  • Domains
  • Spam Filtering

Support

  • Contact
  • Knowledge Base
  • Server Status

Company

  • About Us
  • Network Info

Legal

  • Privacy Policy
  • Terms of Service
  • Cookie Policy
  • GDPR
SSL Secure
99.9% uptime target
Dutch company
Payment methods:
iDEAL
Visa
Mastercard
Bancontact
SEPA
© 2026 Maenda Media. All rights reserved.
Made with❤in the Netherlands
Stream monitoring

Your server is up. But is any sound coming out?

A server answering politely while silence goes out is the outage nobody notices and that lasts an hour. We open your stream the way a listener does, and actually listen.
Silence detection on the audio itself
Works on streams hosted elsewhere
Email, webhook and dashboard
Read back uptime and incidents
See the plans
Livestream.yourradio.com

99,86%

last 80 checks · 24 hours

24h
99,86%
7d
99,97%
30d
99,99%
30 sec
shortest check interval
2
Icecast and Shoutcast
90 days
of checks to read back
Silence — 38 seconds
One check

What happens on every measurement

Four things, in this order. Every thirty seconds to every five minutes, depending on your plan.

  1. 1

    Connect

    We open your stream URL the way a media player does, with a timeout. No connection or an error code is immediately clear.

  2. 2

    Listen in

    Pull a few seconds of audio and decode it to sound. That gives a level in decibels — and therefore silence too.

  3. 3
What gets reported

Five kinds of fault, each with its own cause

These are the things we can tell apart. No more than that — an alert you cannot interpret is not an alert.

  • Down

    No connection, or the server returns an error code. With multiple mount points you see which one.

  • Silence

    The stream is running but no sound comes out. Below your threshold, longer than your limit.

  • Quality dropped

    The bitrate is below what you sell. Often the first sign of a source that is struggling.

Alerts

Where the message goes

You choose where and how often. And when we should say nothing at all.

Email

To the address you give us — not necessarily your billing address. With what is wrong, since when, and on which mount point.

Webhook

Signed with HMAC so you know it came from us. To Slack, Discord or your own system.

Three plans

Per stream. Cancel monthly, like everything else here.

Already have radio with us? You can add monitoring straight from your dashboard. We fill in the stream address ourselves.

Frequently asked questions

Does this work if my stream runs somewhere else?
Yes. You give us the listen URL and we monitor it — it does not matter whose server it is, as long as it is an Icecast or Shoutcast stream reachable over http or https.
How fast will I know?
That depends on your plan: every five minutes, every minute, or every thirty seconds. On top of that comes the grace period that stops a single hiccup from producing an email — three consecutive failed checks by default.
Will I get an email for every little hiccup?
No. A failure has to persist across several checks before we send anything, and between two alerts there is a wait you set yourself. You can also mark fixed hours in which we report nothing at all.
M

Do not let your listeners be the ones who notice first

Your stream is under monitoring within a few minutes.

NormalDownSilenceMaintenance

Stream offline — 2 minutes ago

No connection possible. Email sent to tech@yourradio.com.

Threshold
0 dB−50−96 dB

Silence — 38 seconds

The connection is up, bytes are arriving, and the level has been below the threshold for 38 seconds. An ordinary uptime check sees a 200 here and reports nothing.

Dead air

A 200 is no proof that music is playing

Most monitoring asks the server whether it is still there. It answers with a polite 200 — even when the source has dropped and nothing has come out for an hour. Your listeners notice immediately; you notice when somebody calls.

We pull a few seconds of audio and decode it to sound. From that we work out a real level in decibels. If it stays below your threshold for longer than you set, that is silence — and you hear about it.

  • Real audio, decoded — not a guess based on bytes
  • You set the threshold yourself, in decibels
  • And how long it has to be quiet before it counts
  • With multiple mount points: each one separately

Read

What is playing, the bitrate the server reports, how many listeners are on. Everything the stream itself carries.

  • 4

    Compare

    Against the previous check and against your settings. Only when it deviates and keeps deviating does it become an alert.

    • AutoDJ took over

    The live source dropped and the fallback playlist is running. There is sound — just not the right sound.

  • Audience gone

    The stream is fine, but nobody is listening any more. A dropped relay, a delisting, or a broken player on your own site — otherwise you only find out when someone calls.

    • Dashboard

    Every check, every incident and how long it lasted. There to read back, even if you missed the email.

    One brief hiccup is not an outage. We only alert after several consecutive failed checks, and between two alerts there is a wait you set yourself. Fixed maintenance hours stay completely quiet. A service that calls you at three in the morning about your own planned restart teaches you to ignore it within a week — and then it is worth nothing.

    How exactly do you measure silence?
    We fetch a few seconds of audio and decode it to sound. That gives an average level in decibels. If it sits below your threshold — -50 dB by default — for longer than you set, it counts as silence. So it is a measurement of the sound itself, not of how much data arrives.
    Can I mute it during maintenance?
    Yes, with maintenance windows: fixed days and hours in which we report nothing. Those are part of the Vuurtoren plan. During such a window we also skip the checks, so your uptime does not suffer for it.
    Am I tied in?
    No. Cancel monthly, like our other services. Your checks are kept for as long as your plan runs; after that we clean them up.
    Set up monitoring
    Talk it through first