Guide · event planning
How much internet does an event need?
There is no single number, because it depends on what is running, not on the headcount. A 500-person conference live-streaming a keynote can need more capacity than a 5,000-person festival whose main load is card payments. So the honest answer is: size it to what runs on the day, and to what runs at the same moment. This guide shows you how. What actually eats bandwidth, why headcount misleads in both directions, and why keeping payments, ticketing, streaming and guest WiFi on separate lanes is the difference between a network that holds and one that folds at the gate.
Last updated 1 July 2026 · by Alien IT Solutions
Why headcount is the wrong question
Two events with the same crowd can have completely different demands. What matters is what people and systems are doing at the same instant: a live-streamed keynote, a queue of card taps at the gate, traders running stock and inventory, or a whole crowd trying to upload video at once. Size to that concurrent load and to the systems you cannot afford to lose, and you get a network that holds. Size to a headcount rule of thumb and you either fall over on the day or pay for capacity you never touch.
So the first job is not counting tickets. It is listing what runs.
What uses what
Heavy on bandwidth and critical to the event are two different things. They need different handling.
Streaming & uploads
The heaviest load by far. Live streams, broadcast feeds and big media uploads need real, steady upload throughput, not just a fast download number.
Payments & ticketing
Tiny on bandwidth, but the least forgiving of a dropout. A card terminal sends kilobytes. It just cannot tolerate a stall mid-tap. These need priority and a ring-fenced lane, not volume.
Production & comms
Show control, scanners and crew comms are modest in size but mission-critical, so they sit on protected lanes alongside payments.
Guest WiFi
Large and impossible to predict, but shapeable. Cap it and shape it and the public can hammer it all day without ever threatening the systems that run the show.
The trap: one flat connection
The mistake we get called out to fix is nearly always the same. Everything, card machines, ticketing, the stream, the public WiFi, dumped onto one connection with no separation. It tests fine on setup morning when the site is empty. Then the gates open, the guest network fills up, and the card terminals start timing out because a few thousand phones are fighting them for the same pipe.
Total bandwidth is not the whole story. The order of who gets served matters more. A connection that looks big enough on paper still fails if the least important traffic can crowd out the most important. That is why we never quote a single number and walk away. We quote capacity and a plan for how it is divided.
How we size it
List what runs at once
We map every system, payments, ticketing, streaming, production, guest WiFi, and mark what peaks together. Gates opening and a headline act finishing are the moments that decide the size, not the quiet middle of the day.
Build in headroom and failover
We size the backhaul with spare capacity, then add a satellite failover so a busy peak or a carrier blip does not take the event down. On the day, redundancy is not a luxury. It is the point.
Separate the lanes
Each system gets its own sized lane with priority where it counts, so heavy guest traffic physically cannot starve the payments or the stream. This is what turns one connection into an event network.
What "enough" actually looks like
Enough is not the biggest connection you can buy. It is the right connection, divided the right way. Card payments that clear instantly even when the crowd is at its worst. A stream that does not stutter during the one moment everyone came to see. Guest WiFi that is genuinely usable but can never take the event down with it. And a second path ready to carry the load if the first one drops, without anyone on site noticing.
Get that right and the total number matters far less than most people think. Get it wrong and no amount of raw bandwidth saves you.
The five things worth writing down first
You do not need to work out a bandwidth figure yourself. You need to describe the day accurately, and the number follows from that. Before you ask anyone to quote, get these five down:
- The event type and rough headcount. A trade expo, a music festival and a corporate conference of the same size behave nothing alike. Say which one it is.
- Every system that touches the network. Card terminals, ticket scanners, the live stream, production and show control, exhibitor or trader systems, back-of-house, and public WiFi. If it plugs in or connects, list it.
- What has to keep working no matter what. Usually payments and ticketing. Naming your non-negotiables up front is what lets a network be built to protect them.
- The peak moments. Gates opening, a keynote going live, a headliner finishing and 10,000 phones lighting up at once. Peaks size the connection, not averages.
- The site itself. Whether there is any existing internet, how reliable it is, and whether there is power and somewhere to put a comms rack. This decides whether we add to what is there or bring the whole connection in.
Hand over those five and sizing stops being a guess. It becomes arithmetic, with headroom on top.
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.
Questions people ask
How much internet does an event need?
There is no single number, because it depends on what is actually running, not just the headcount. A 500-person conference doing live streaming and registration needs far more than a 5,000-person festival where most of the load is card payments. The right way to size it is to add up what each system needs, EFTPOS, ticketing, streaming, production and guest WiFi, and what runs at the same time, then build in headroom and failover.
Why is headcount a poor way to size event internet?
Because two events with the same crowd can have wildly different demands. What matters is what people and systems do at once: a live-streamed keynote, a queue of card taps at the gate, traders running stock systems, or a crowd all uploading video. We size to the concurrent load and the critical systems, not a headcount rule of thumb that misleads in both directions.
What uses the most bandwidth at an event?
Live streaming and large file uploads are the heaviest, followed by production and broadcast feeds. Payments and ticketing use surprisingly little bandwidth but are the least tolerant of dropouts, so they need priority rather than volume. Guest WiFi is large but can be shaped so it never threatens the systems that run the event.
Should every system share one connection?
They can share the backhaul, but never the same flat lane. Payments, ticketing, production and public WiFi run on separate, sized lanes with priority where it matters, so a crowd hammering the guest network cannot starve the card machines or the live stream. Separation is what turns one connection into a reliable event network.
What if the site has no internet, or it is not enough?
We bring the connection: multiple mobile carriers bonded for capacity with a Starlink satellite link as failover, feeding a comms rack with its own power. If the venue's fixed line exists but is too small or too fragile, we add to it and failover around it rather than trust a single pipe on the day.
How do I work out what my event needs?
Tell us the event type, the headcount, and which systems are running, payments, ticketing, streaming, production, guest WiFi, on the contact form. We size the connection and the lanes from that and come back with a plan and a price, so you neither under-buy and fall over nor over-buy and waste money.
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