Talk to someone new right now — for free

Voice chat with strangers instantly. No sign-up required.

Start Chatting

Why Nobody Is Listening to Your Live Stream (Our Data)

Published 2026-08-22 by Iris Crier 5 min read
broadcasting internet-radio audience live-audio original-research

Most likely because they arrived, waited a few seconds, heard nothing happening, and left — before you ever knew they were there.

We can put a number on it. Across 30 days we logged 1,842 people who opened a live audio platform, waited, and gave up without connecting to anything. The median gave up after 13 seconds. Nine in ten were gone inside a minute.

This is our own data, from our own logs, and we're publishing it because we have not seen anyone else measure the specific moment where a live audience is actually lost.

How Long Do People Actually Wait?

Thirteen seconds. That is the median, not the floor.

Measure Value
Samples 1,842 abandoned sessions
Window 30 days
Median wait before leaving 13 seconds
Mean 40.7 seconds
25th / 75th percentile 6s / 29s
Gone within 60 seconds 1,658 (90%)
Waited longer than 5 minutes 31 (2%)
Longest single wait 2h 28m

The mean is badly misleading here — a handful of people who left a tab open for hours drag it to 40 seconds. The median is the number that describes real behaviour, and it is brutally short.

Note the shape of the distribution: a quarter of people are gone in six seconds. That is less time than it takes to read a station description.

How Does This Compare to Known Streaming Research?

It measures a different failure, and that distinction matters.

The established research is about startup delay — how long the player takes to produce sound after you press play. Akamai's analysis of its streaming network found viewers begin abandoning once startup passes about two seconds, with each additional second raising abandonment by roughly 5.8 percentage points. A Limelight Networks survey put it more bluntly: 53% of viewers abandon a live stream that takes longer than two seconds to start.

The industry rule of thumb is well established:

Startup time should be under two seconds — every fraction of a second beyond that directly impacts viewer retention.

Our 13 seconds is not that. Our player starts instantly; there is nothing wrong with the technology. What our listeners are waiting for is something to exist — a broadcaster to go live, or another person to arrive.

That makes the two numbers complementary rather than contradictory. Two seconds is the tolerance for technical delay. Thirteen seconds is the tolerance for emptiness. If a stream that loads slowly loses half its audience, a stream that loads instantly into silence gets roughly eleven extra seconds of patience — and no more.

What Does 13 Seconds Mean for a Broadcaster?

It means your first impression is not your first minute. It is your first ten seconds, and silence is the most expensive thing you can put there.

Three practical consequences:

  1. Dead air at the top of a show costs you the audience that arrived for it. The people checking whether you are live do it in the first seconds. If they hear nothing, they cannot distinguish "not started yet" from "broken."
  2. Announced start times matter more than the content that follows. Someone arriving at 8:00 for an 8:03 start has already made their decision by 8:00:13.
  3. Something audible beats an accurate "starting soon" card. A visual placeholder does not survive a listener who opened the tab in the background.

This is also why we run always-on channels in the gaps. When nothing is scheduled, our platform still has audio playing — classical, an eclectic mix, and 1940s old-time radio — so that arriving at a quiet moment is not the same as arriving at silence.

Is It the Platform's Fault or the Broadcaster's?

Usually neither. It's a coordination problem.

The clearest example we have: on one evening, four people arrived from four different countries within 48 minutes — and not one of them ever overlapped with another. Our logs recorded others_in_queue=0 at every single check while each was waiting. Two of them, from Saudi Arabia and the United States, arrived 60 seconds apart and each stayed about three seconds.

Any one of them would have had a conversation if they had waited a minute. None knew the others were coming.

That is the structural problem with live audio: supply and demand have to be present simultaneously, and at small scale they almost never are. Scheduling is the standard fix. Always-on audio is the other one — it converts "nothing is happening" into "something is happening, and you can stay while you wait."

What Should You Actually Change?

Ordered by how much it moves the number, based on what we've measured:

  1. Start on time, audibly. Not a countdown graphic — sound. Talk over your own intro if you have to.
  2. Publish a fixed schedule and keep it. Habit beats quality for retention at small scale. A mediocre show every Tuesday outperforms a great show whenever.
  3. Fill the gaps with something legal to play. Public domain and CC0 audio costs nothing and needs no licence — see where to find it.
  4. Tell people how long to wait. "Starting at 8, doors open 7:55" sets an expectation that survives thirteen seconds.
  5. Give arrivals a reason to stay one more minute. That minute is the entire ballgame.

An Honest Caveat

We do not yet know whether always-on audio actually increases how long people wait. We shipped it recently and have no post-launch comparison. What we can say is that the 13-second median is measured over 1,842 real sessions, and that people are demonstrably not leaving because they were disappointed by content — they leave before there is any content to judge.

We would rather publish the number with that caveat attached than imply a result we haven't earned.

Where This Data Comes From

Client-side telemetry from HereSay, a voice chat platform, covering 30 days and 1,842 sessions that ended without a connection. "Abandoned" means the person opened the platform, entered a waiting state, and left without ever connecting. Timings are measured client-side from the moment waiting began.

For context on the platform generating it: 15,000+ conversations across 60+ countries to date, with a median call length far shorter than most people expect — the reason we started measuring the waiting period in the first place.


Sources: our own client telemetry (1,842 sessions, 30 days) · Akamai/Limelight startup-delay research summarised by Bitmovin · OTTVerse: video startup time explained · Mux: live streaming metrics that matter


Thinking about broadcasting? See how to start a talk radio station without licensing fees, or compare the platforms.

Keep reading