A venue network is rarely yours alone. It carries point-of-sale terminals, guest Wi-Fi, ticketing, back-office systems and, on the day, your broadcast. When something degrades during a show, the hard part is not noticing it. It is working out quickly whether the problem is your equipment, the venue's network, or the path beyond it, and doing so without guessing in front of an audience.
Pre-show testing tells you the network was healthy yesterday. Monitoring tells you it is healthy now, which is the only question that matters while the show is live.
Why venue networks misbehave during a show
A network that performed perfectly during rehearsal can change the moment the doors open:
- Guest Wi-Fi load rises sharply as attendees arrive, competing for the same uplink.
- Shared infrastructure is shared. Your broadcast may sit behind the same connection as everything else in the building.
- Traffic patterns change. Ticket scanning at the door, card payments at the bar and video uploads from the media team can all coincide.
- Local interference changes once a hall fills with people and their devices.
None of these are unusual. They are also invisible to a single pre-show speed test.
What to monitor, and why
During a broadcast, a small set of signals will tell you more than any single number:
- Latency, continuously. Not one reading, but a stream of them, so a spike is visible at the moment it happens rather than averaged into a healthy figure.
- Stability over peak times. The question is not whether the line is good on average, but whether it stays good when the building is busiest.
- Loss and short outages. Brief failures that recover can still throw a stream off air. They need to be visible, not silent.
- The path, not just the endpoint. A problem may sit on the route between the venue and the ingest service, well beyond the building.
Segmenting the network matters here. Where the venue can provide a dedicated VLAN or a separate uplink for production traffic, your monitoring becomes far more meaningful, because you are measuring the path your broadcast actually uses rather than the congested one everyone else is on.
Separating local from upstream
When the numbers move, the first useful distinction is local versus upstream:
- If every device on the production network degrades at once, suspect the shared connection or the venue's infrastructure.
- If one machine degrades while others are steady, suspect that machine, its cable or its Wi-Fi.
- If your network is fine but the stream still stutters, suspect the path to the ingest service or the service itself.
Making that call quickly is what turns a scramble into a controlled response. It also produces evidence you can hand to the venue's network team, who are far more able to help when you can say exactly what changed and when.
A layered approach that scales
No single tool answers every question, so a production team benefits from layers:
- A continuous, lightweight monitor to confirm the line is steady and to catch spikes and drops as they happen. A browser-based check such as Conntivity is useful here because it needs no install and can run on any spare machine on the production network.
- Native path analysis for investigating a specific problem: traceroute to see where packets slow or stop, and ping to distinguish a local fault from something upstream. MyEvent Labs builds netdx for that deeper look.
- The encoder and platform telemetry, which describe what the stream itself is doing and complement the network view.
Together, these let the team answer both "is the link healthy right now" and "if not, where is it failing".
Prepare, then watch
The practical routine is short. Before doors open, confirm the line is steady on the production segment and note the baseline. During the show, keep a continuous monitor visible somewhere the technical lead can see it, and watch for drift rather than waiting for failure. When something changes, decide local or upstream first, then act: lower the bitrate, switch to a backup path, or escalate to the venue with specifics.
A broadcast that stays on air is rarely the one with the fastest connection. It is the one where someone was watching, noticed the change early, and had a plan for what to do about it.