Why Audio Streams Drop on Shared Hosting
Comparing web radio hosting often reveals a noticeable price gap. Some providers offer streams for a few euros per month or advertise unlimited listener slots. Dedicated platforms like SPCast start at 30 €* per month. This difference is not marketing driven. It is the result of two fundamentally different technical architectures.
How Traditional Shared Mass Hosting Operates
On budget hosting platforms, dozens or even hundreds of web radio stations share a single physical server. All stations run on the same operating system and draw from the same CPU, memory, and network card.
As long as most stations on the server have few listeners and perform no compute-heavy tasks, this setup functions. Problems begin when multiple stations become active at the same time.
The Neighbor Effect on Shared Servers
In a shared environment, your stream stability depends directly on what other customers do. The most common causes of stream dropouts and buffering are outside your own broadcasting software:
- Audio transcoding consumes CPU capacity: When a neighboring radio transcodes multiple AAC bitrates simultaneously, processor load spikes. If server CPU runs low, audio buffers for other stations stall.
- AutoDJ and media imports: When another user uploads large music libraries or triggers playlist re-indexing, disk I/O becomes saturated.
- Shared IP addresses: If one project on the server attracts abuse or becomes the target of an attack, network blocks or throttling affect every radio sharing that IP address.
This neighbor effect is difficult to prevent on shared operating systems. Once shared hardware is exhausted, audio streams drop.
The SPCast Architecture with Isolated Instances
SPCast avoids mass servers entirely. Each web radio project receives its own technically isolated cloud instance.
- Dedicated resources: CPU cores, memory, and 50 GB NVMe storage belong exclusively to your station. Another station cannot slow down or crash your instance.
- Global load balancer: A front-facing global load balancer absorbs traffic spikes. It delivers audio streams to listeners without overloading playout processes on the instance.
- Sustained audio bandwidth: Streams up to 320 kbps run without internal throttling or background compression.
- HLS and modern codecs: The instance handles transcoding and web player delivery directly within its own environment.
Actions taken by other stations on the platform have zero impact on your broadcast.
Why Starting on a Dedicated Instance Benefits New Projects
Many web radio stations start as a personal passion project, but still want dependable quality from day one.
- No painful migrations as you grow: Starting on budget shared servers often forces an emergency provider switch once listener numbers climb. That means changing stream URLs, rebuilding playlists, and losing listeners. On a dedicated cloud instance, capacity expands smoothly as your audience grows.
- Engineered and operated in Germany: SPCast is not an anonymous resale of third-party software. The platform has been operated and maintained in Germany by experienced developers since 2013.
- Personal onboarding instead of call centers: Newcomers benefit from direct support. Our team walks you through initial configuration step by step until your stream and AutoDJ run smoothly.
- Modern standards from the very first listener: HLS streaming, seamless transitions, and 320 kbps audio quality are included from your very first broadcast.
The price difference compared to crowded shared servers reflects this commitment to quality: you receive an independent server instance with guaranteed resources and direct developer support.
Learn more about the technical specifications in our Web Radio Hosting overview or discuss your setup directly with our support team.