How do stadiums cope when phone networks saturate?

A cell site or a Wi-Fi access point shares a limited amount of radio capacity among the devices connected to it. On an ordinary day the people around a stadium are spread across many cells. On match day the crowd sits in one bowl, much of it trying to post, stream and call at the same moments, and the cells that cover that bowl run out of room.

Ready.gov describes the same effect in emergencies: mobile networks can become overwhelmed, making it hard to make and get phone calls. Its advice is to text, because text messages need less bandwidth and so are transmitted more reliably when many people use their phones at the same time.

Venue Wi-Fi has its own version of the problem. Cisco’s design guide for large public networks notes that stadium guests are not under the operator’s control, stay on the network for a few hours at most, and keep joining and leaving as they move around. That onboarding activity puts extra load on the wireless controllers, on top of the airtime the traffic itself uses.

The main tool carriers use inside a venue is a distributed antenna system (DAS). AT&T defines a DAS as a network of antenna nodes that provides and enhances wireless service within a building or area and improves coverage and capacity indoors and outdoors. AT&T’s stadium example describes hundreds of antennas providing coverage throughout the venue, served by dozens of cell sites located in the stadium itself.

For events, carriers add temporary sites:

• Cells on wheels (COWs). Verizon describes its COW as a trailer-based site that gets coverage running fast. AT&T has described using COWs, along with temporary rooftop antennas, around a stadium and the venues hosting related events.
• Cells on light trucks (COLTs) and similar truck-mounted sites, which carriers also use when permanent towers are down.
• Units built for crowds. Verizon lists a scissor-lift antenna unit for handling large capacity events.

Public safety has a parallel fleet. The FirstNet Authority says its deployables boost coverage after disasters, during large planned events and in remote areas, and are available to FirstNet subscribers. How does emergency communication work when towers fail? covers those in more detail.

Wi-Fi takes a share of the load off cellular, but only if it is designed for density. Cisco’s guide covers antennas mounted above the seating and, where there is no suitable mounting point, access points placed under the seats. Under-seat designs use the crowd itself: human bodies absorb radio signal, so more access points can be packed in without interfering. The catch is that coverage changes a lot between an empty and a full venue, and Cisco calls it a valid but uncommon solution to be judged case by case.

How many people actually join also depends on onboarding. Cisco notes that requiring a portal click keeps connection numbers lower, while automatic onboarding such as OpenRoaming raises them, which changes the capacity plan. On the radio side, the Wi-Fi Alliance says Wi-Fi 6 introduced OFDMA and multi-user MIMO to share channels more efficiently, with stronger performance in dense settings such as large public venues.

When the public network is congested, authorised staff can jump the queue. CISA’s Wireless Priority Service gives enrolled devices priority calling on participating cellular networks when the user dials the *272 service code. CISA says these calls do not preempt calls already in progress or deny the public the use of the network. FirstNet goes further, with a nationwide broadband network created specifically for first responders.

None of this makes capacity unlimited. A DAS, a COW or a Wi-Fi network is still a shared pool, and in a big enough surge the venue’s own operations compete with the crowd for it. Ticket scanners, card readers and staff messaging apps that all depend on the same uplink tend to fail together. How does ticket scanning work without internet? looks at the gates in particular.

Two habits reduce that exposure. The first is separating critical systems: Cisco’s guide gives the example of a separate wireless system with its own dedicated channels, such as a press area inside a stadium. The second is keeping critical traffic small. A gate count, an incident note or a request for a steward is a short text, not a video, and the same logic as Ready.gov’s advice about texting applies.

A third option is to let staff phones talk to each other directly. Phones close together can exchange short messages over Bluetooth LE without using the cell network or Wi-Fi at all, and phones can relay for each other to reach someone out of direct range. It suits small messages, because Bluetooth LE has limited range and throughput, and only between devices running the same app. Offline Protocol’s mesh SDK is one example: it sends MLS-encrypted messages between phones over Bluetooth LE and can forward them across several hops. Used this way, the local link is a fallback for coordination, not a replacement for the venue’s network.