Creative Broadcast Agency

Venue testing

Streaming diagnostic: is your internet good enough for live streaming?

A streaming diagnostic answers one question: is this internet good enough for live streaming? Before we quote a live stream or go live from a room, we test the venue network against what the show needs: sustained upload, packet loss, jitter and latency, plus the checks the chosen protocol adds. This is the full check we run with StreamCertified, the thresholds behind each verdict, and how the result shapes the quote.

Reading time
4 min read
Updated
Updated
Run the free streaming diagnostic
Per diagnostic run
~30 s
Ready, Check, Not ready
3 verdicts
Set the checklist
4 answers
On every show
Second path
The short answer

Is your internet good enough for live streaming?

A streaming diagnostic tells you. It measures the room's network against what the show needs: sustained upload for the planned resolution, packet loss, jitter and latency, plus the checks your protocol adds. Run it on the port the encoder will use, at the time the show runs.

We run this check before we quote and again before we go live. The core of it is the StreamCertified streaming diagnostic, which measures the whole connection in about half a minute and grades each figure against broadcast thresholds.

Run the free streaming diagnostic on StreamCertified

The plan

The plan decides the checklist

Not every show needs the same checks. Four answers set the list:

  • Live resolution. 720p30, 1080p30, 1080p60 or 4K. This sets the upload the room must hold.
  • Protocol. RTMP, SRT or WebRTC. SRT and WebRTC add a NAT check; WebRTC adds a TURN relay check.
  • Does something at the room listen? An SRT listener or a server in the room needs open inbound ports.
  • Is there a return feed or comms into the room? That adds a download floor and a playback check.

Each check then reads Ready, Check or Not ready. A check that was not measured shows as not measured. It never counts as a pass.

Thresholds

What the venue must pass

Technical specification

These are the thresholds StreamCertified uses.

CheckReadyCheckWhy it matters
Sustained uploadEncode bitrate + 20% (7.2 Mbps for 1080p30)Meets the bitrate, no headroomThe stream leaves the room on the upload
Packet lossUnder 0.5%Under 1%Live protocols cannot wait for a re-send
JitterUnder 15 msUnder 30 msTiming wobble the encoder cannot buffer away
Latency to test server80 ms or less150 ms or lessRound trip to the named server
Download (return feed only)Over 10 MbpsOver 5 MbpsReturn feed or comms into the room
NAT type (SRT, WebRTC)Open or coneUndeterminedThe connection mapping must hold
Ingest URLNo errorsWarnings onlyA bad URL fails at the encoder, seconds before the show

Anything worse than the Check column is Not ready. Each line links to its own article: upload, packet loss and jitter.

How we do it

How we run it on a site visit

  1. Find the encoder's port. We agree with venue IT where the encoder will sit and test from that port. Guest Wi-Fi is not the show network.
  2. Name the room. Readings are kept against the room, so a second visit compares like with like.
  3. Run the diagnostic several times. Quiet room, then busy room. We look for agreement between runs, not one good number.
  4. Add the protocol checks. NAT type for SRT and WebRTC, inbound ports if we listen in the room.
  5. Check the cellular signal. We test the second path at the same position, because it has to work in that room too.

This is the network half of a site survey. Power, sightlines and cable runs are the other half.

Before we quote

Why we test before we quote

The reading changes the scope. A room that is Ready for 1080p60 on a dedicated line is one quote. A room that is marginal on a shared line needs a dedicated circuit from the venue, a lower resolution, or a stronger second path. Quoting before we know is guessing, and a guess becomes a surprise on show day.

When we cannot visit before the quote, we quote with the assumption written down, such as "venue provides a wired line with 7.2 Mbps sustained upload", and test at the first chance. You see what the price depends on.

Show day

Test again on show day, and keep a second path

Venues change. Another event moves into the next hall. IT changes a firewall rule. So we run the diagnostic again at load-in and before doors, and compare with the site-visit readings. For timing, we measure latency on the rehearsal with a clock in the picture.

Every show also carries a second path: bonded 5G alongside the venue line. The test tells us how much to trust the room. The second path means that if the room lets us down, a failure never reaches your audience. We ran the YOUNGO daily broadcast at COP28 this way: we produced the YOUNGO daily broadcast, in four languages across four channels, for two weeks, with bonded 5G reporters as part of the build.

See how we plan live streaming in Dubai.

Run the free streaming diagnostic on StreamCertified

When you have a venue and a date, send them to us with your result. We will test the room and quote against what it can carry.

FAQ

Questions we get asked.

What internet speed does a venue need for a live stream?

How long does a venue network test take?

Can we rely on the venue's internet alone?

Can we run the test ourselves before contacting you?

Tell us the date, the venue and who is watching.

We scope every engagement against its run of show, not a package.

Scope your event