Event Networks

Guide · bandwidth budgeting

How to budget bandwidth for an event

Someone on the committee asks the venue "how fast is the internet", the venue quotes a download number, everyone nods, and on the day the card terminals queue and the livestream stutters. The problem wasn't the number — it was budgeting by headline speed instead of by demand. This page gives you the budgeting logic: what to count, how to split it, and which number actually decides whether your stream survives. For choosing the connection itself once you know your requirement, see our planning guide on how much internet an event needs.

Last reviewed: 18 July 2026 · by Alien IT Solutions

Count what people do, not how many turn up

Attendance is the wrong starting number. A thousand people wandering a market with phones in pockets need less from your network than one production desk streaming the keynote. Budget by activity:

  • Card terminals need almost nothing — tiny transactions, a trickle of data. What they need is for that trickle to arrive every single time, within a couple of seconds, or the queue backs up and stallholders start blaming you. Their requirement is reliability, not volume — the same logic behind temporary EFTPOS for markets and events.
  • A livestream is the opposite: a continuous, heavy, unforgiving flow that must be sustained for the whole session. One stream can outweigh every phone at the event.
  • Production and operations — ticket scanning, staff comms, point-of-sale back office — sit in between: modest demand, low tolerance for failure.
  • Guest WiFi is the elastic one. Guests checking maps and posting photos generate bursts, but nothing breaks if their connection is merely okay.

Write those four groups down with what each one does. That list, not the attendance figure, is your bandwidth budget.

Split the network before you split the bandwidth

The single most valuable decision in event networking costs nothing: put payments and production on their own network, and give guest WiFi whatever is left over.

Do this and a burst of guest traffic — everyone uploading at once when the headline act walks out — cannot touch the EFTPOS terminals or the stream. Skip it, and your most casual users compete head-to-head with your most critical ones, and the critical ones lose, because there are fewer of them. The split can be separate networks on the same connection with the important one prioritised, or physically separate connections for the truly critical gear. Either way, the principle holds: critical traffic first-class, guests on the leftovers, never the reverse. Our event WiFi setup guide shows what that separation looks like on site.

Upload is the number that kills livestreams

Venue quotes headline the download figure, because it's the bigger, better-sounding number. Most connections are asymmetric — upload is a fraction of download — and a livestream is almost entirely upload. So is sending photos to press, backing up footage, and video-calling a remote presenter.

Before you commit to streaming anything, get the upload figure in writing and measure it yourself on site. A connection with a generous download and a thin upload will browse beautifully all day and still drop your stream the moment it starts. If the upload can't carry the stream with comfortable headroom on top — sustained, for the whole session, while everything else runs — you need a different connection for the stream, and that decision is far cheaper to make in the planning week than in the opening minute.

Concurrency: events are not offices

In an office, only a small share of people hit the network hard at any moment, so planners quote reassuring ratios. Events break those ratios. Crowds do things together: doors open and everyone checks in at once; the speaker says "scan this QR code" and hundreds of phones hit the same page in the same ten seconds; the finale starts and half the room uploads video.

You still don't budget for every attendee at once — that ruins you on cost — but you budget for synchronised peaks, and you look at your own run sheet to find them. Every "everyone, please..." moment in the program is a concurrency spike you can see coming. If the peaks land beyond what the connection carries, decide in advance what degrades: guest WiFi slows down gracefully, payments and production never do — which is exactly why they're on their own network.

Test at the venue, at event time

A speed test from the venue office on a quiet Tuesday tells you what the connection does on a quiet Tuesday. Mobile networks around a venue congest when crowds arrive — thousands of extra phones share the same towers — and shared venue connections slow when the building fills. Weekend and evening performance can differ from business hours even with nobody in the room.

Test at the venue on the same day of the week and time of day as your event, in the spots where the critical gear will sit, and test upload as deliberately as download. Then test your fallback the same way. Ten minutes of realistic measurement beats any amount of quoted speed.

The short version

Budget bandwidth by what people do, not how many attend — terminals need reliability, streams need sustained upload, guests just need "okay". Split payments and production onto their own network and give guest WiFi the leftovers, never the reverse. Upload is the figure that decides whether your livestream survives, so measure it on site at event-day time, not from a quiet-Tuesday speed test. Plan for the synchronised peaks in your own run sheet, and choose what degrades before the crowd chooses for you.

General guidance only — every event, venue and connection behaves differently, so measure your own before relying on it.

Who runs it

Event Networks is the event-connectivity service of Alien IT Solutions, an Australian IT, networks and connectivity company with more than 18 years of building networks that have to hold under load. For the payments side specifically, see our guide to temporary EFTPOS for markets and events. For a permanent shared connection at a venue or precinct, see our sister service Shared Internet.

Size it right before the gates open.

Tell us the event, the headcount and what is running. We will size the connection, divide it properly, and price it. No pressure.

Get a quote