Why Your Office WiFi Dies at 2 PM (and It’s Not Your Internet)

Your office Wi-Fi dies at 2 PM because you run out of airtime, not internet bandwidth. Wi-Fi lets one device transmit at a time per radio, so every laptop, phone and video call queues for the same turn.

Owners almost always open this conversation the same way. They want to know whether they should call the internet provider and buy a bigger circuit.

It is almost never the circuit.

We have watched offices double their internet speed and change nothing about the afternoon. Same complaints. Same hour. The circuit was never the constraint. The air in the room was, and that is a different problem with a different fix. If you want the platform-level view of how we handle the network layer, that sits on our managed firewall and network security page. This is the narrower question underneath it.

Airtime Is the Thing You Actually Ran Out Of

Wi-Fi is a shared radio channel, not a bundle of private wires. Cisco Meraki’s high-density design guidance states it plainly: Wi-Fi is based on CSMA/CA and is half-duplex, which means only one device talks at a time while everything else connected to that access point waits its turn.

So the unit of scarcity is time. Not megabits. Microseconds, handed out one device at a time.

Cisco’s own high client density guide puts the arithmetic in a sentence most owners find clarifying: a single access point radio represents a finite amount of potential bandwidth, shared with every user of that cell. Their example uses 100 Mbps across 10 active users, which leaves roughly 10 Mbps each.

Add twenty more devices and nobody gets a message telling them the pool got smaller. Pages take longer. Teams stutters. Somebody says the internet is slow. It isn’t.

Nothing Breaks at 2 PM. Everything Arrives at Once.

There is no single failure at two o’clock. What there is, in a normal office, is a concurrency peak that nobody planned for.

Morning is staggered. People trickle in, open email, and half the staff is still on the road or in the parking lot. By early afternoon everyone is in the building, every laptop is associated, every phone has joined the wireless on its own, and the calls that got scheduled around lunch are all running at the same time.

Count the radios in your own office sometime. Not the people. The radios. It is rarely one device per person anymore. Laptop, phone, maybe a tablet, a watch that talks to the phone, a wireless printer that beacons whether or not anyone is printing.

Then layer the invisible traffic on top. Cloud sync catching up on the morning’s files. A backup window somebody set for 1 PM years ago and forgot. Windows updates. A guest network carrying a waiting room full of phones that auto-joined because the password has not changed since 2019.

None of that is a fault. It is arithmetic.

The Slowest Device in the Room Sets the Pace

This is the part that surprises people, and it is the reason a single old laptop can make a whole floor feel broken.

Airtime is handed out by turns, not by speed. A device sitting at the far end of the office with two bars negotiates a slower data rate, which means it needs more time on the air to move the same file than a device sitting near the access point. It holds the channel longer. Everyone else waits longer.

One laggard slows the cell for everybody. That is the whole mechanism.

Which explains why “it works fine at my desk” and “it is unusable in the back conference room” are the same problem described from two chairs. The back room is not just slow for the person sitting in it. It is taxing everyone.

We have walked into offices where the fix was moving one access point about fifteen feet and turning off the lowest data rates so ancient devices stop dragging the cell down. No new hardware. No bigger circuit. Just a different seat for the radio.

Three Channels, and Your Neighbors Are in All of Them

The 2.4 GHz band is where most of the misery lives. Cisco’s guide notes the constraint directly: 2.4 GHz has a limited non-overlapping channel count, just three in the United States, alongside a large population of other things transmitting in the same space.

Three usable channels. Every business in your building, the dentist downstairs, the cafe next door, plus microwaves and Bluetooth and wireless headsets, all sharing them.

An access point cannot transmit while it hears someone else transmitting. Before any radio puts a packet in the air, it has to hear quiet first. A busy neighbor is not attacking you. They are talking. Your equipment is waiting politely, which is exactly what it was designed to do.

That third row matters more than it looks. The FCC opened 1,200 megahertz across the 6 GHz band back in 2020. Hardly anyone around you has moved into it. So a business running current access points gets something close to an empty road, at the same hour the older bands are jammed with every neighbor, every printer, and every phone in the building, and the equipment does not have to be exotic to reach it, only recent.

If your access points are old enough that 6 GHz is not an option, you are competing for a much smaller room than you have to.

Your Own Access Points Are Talking Over Each Other

Offices that added a second and third access point to “get better coverage” often made the afternoon worse, and the reason is unintuitive.

Two access points on the same channel, close enough to hear each other, do not double your capacity. They take turns. You bought a second radio and gave it the same slot in line.

Coverage went up. Capacity did not.

Here is what actually goes wrong in the small offices we see most:

• Consumer gear bought one box at a time over five years, each unit picking its own channel with no coordination between them.
• Access points mounted wherever a cable already existed, which is almost never where the people are.
• Transmit power cranked to maximum on every unit, so each one shouts over the others and clients cling to a distant access point instead of the near one.
• One device doing everything. Router, firewall, switch, and wireless in a single consumer box, sitting in a closet behind a filing cabinet.
• A guest network running on the same radios at the same priority as the people doing billable work.

Meraki’s guidance suggests planning around roughly 25 clients per radio, or 50 per access point, in dense environments. Count your devices, not your employees, then check that number against how many access points you actually have. The arithmetic gets uncomfortable fast in a twenty-person office.

What We Look At, In Order

A site survey comes first, and it is less dramatic than it sounds. Nobody climbs anything. We walk the space with a laptop and measure what the air actually looks like from where people sit, not from the server closet.

Then the questions get specific. How many devices are associated at 2 PM versus 9 AM. Which channels the neighbors are using. Whether your own access points are fighting each other. What the data rates look like at the desks that complain. Whether anything large is crossing the wireless that has no business being there, which is a real pattern for firms moving big design files around and one we wrote about separately in the piece on what large CAD files do to a firm’s network.

Video is usually the symptom, not the cause. Microsoft’s own network guidance notes Teams can deliver HD video in under 1.5 Mbps. That is not much. When calls break up, the bandwidth is rarely missing. The turns are.

VJNetworks does site surveys, wireless design, installation, configuration, and ongoing management. The one piece we bring in help for is physically pulling the cable to a new access point location, and that gets handled as part of the project rather than left with you. More on how that division of labor works sits on our structured cabling and network installation page.

The Fixes, Ranked by What They Return

1. Move people off 2.4 GHz. Band steering pushes laptops and phones to 5 GHz and leaves 2.4 for the printers and sensors that genuinely need the range. Costs nothing on decent equipment. Usually the single biggest improvement available.
2. Fix channel assignment and power. Stop your own access points from sitting on top of each other, and turn transmit power down so devices connect to the nearest unit rather than the loudest. This is configuration work, not a purchase.
3. Separate the guest network and cap it. Visitors should not be competing for airtime with the people billing hours, and keeping that traffic away from your business network is worth doing on its own merits.
4. Raise the minimum data rate. Drop support for the oldest, slowest rates so a decade-old device cannot hold the channel hostage. Test before you commit. Occasionally a scanner or a label printer genuinely still needs those rates.
5. Then, and only then, talk about hardware. Access points placed by measurement rather than by where the cable already ran. More of them if the survey says so, fewer if three are fighting over one room.

Notice where buying things sits on that list. Fourth and fifth. Plenty of offices we have worked in needed only the first two, done properly on a Thursday afternoon, and the complaints stopped.

What Owners Ask Once They Stop Blaming the ISP

One honest note to close on. Wi-Fi complaints rarely arrive as Wi-Fi complaints. They arrive as “Outlook is slow” or “the call dropped again,” and the wireless is the last thing anyone suspects because it worked yesterday. It did work yesterday. There were fewer devices in the room. That is the entire difference.

VJNetworks has run managed IT for Tri-State businesses since 2004, mostly companies of 5 to 60 employees, with a 97% client retention rate and a 15-minute response standard during business hours. Wireless is one of the more fixable things we get called about, and one of the least often diagnosed correctly.