How to Find the Right Subnet Size When Your Office Network Runs Out of Addresses
Your office ran out of IP addresses. Count what you really have, double it, and pick the subnet size that fits, with a worked example.
It starts with a small annoyance. A new starter's laptop will not get an address, or the printer drops off the network every Monday morning when everyone arrives at once. You check the router and the DHCP pool is full. Your office did not get hacked and nothing is broken. You simply ran out of addresses, and the subnet you picked years ago was sized for a smaller office than the one you have now.
I have seen this exact moment in offices that grew one desk at a time. Nobody notices the address count creeping up, because each new device takes one address and the pool looks big enough, right up until the day it is not. Fixing it means picking a new subnet size, and doing the count properly this time so you are not back here in eighteen months.
Count everything, not just the laptops
The first step is a real count, and the count is always bigger than people expect. Walk the office and list every device that holds an address. Laptops are the obvious ones, but they are rarely even half the total. Phones on the office Wi-Fi take an address each. So do printers, the Wi-Fi access points themselves, the meeting room screens, the door entry panel, the CCTV cameras, the smart thermostat, the NAS box, the servers, and the VoIP phones if you have them. Then add guests. A client in the meeting room, a contractor on site for a week, a training day with twenty visitors, all of them take addresses from the same pool.
Static addresses count too. Your servers, printers and access points probably have fixed addresses, and those still sit inside the subnet even though DHCP never hands them out. Write the list down, in one place, with a number next to each type. If you guess, you will guess low. Every office I have counted has come in at least a third higher than the first guess.
The maths in one minute
A subnet size is written as a slash number, like /24, and it decides how many addresses the subnet holds. Each step down the list doubles the size. Two addresses in every subnet are never handed out: the first names the network itself and the last is the broadcast address. So the usable count is always two fewer than the total.
The sizes you will actually meet in an office are these. A /27 holds 32 addresses, 30 usable. A /26 holds 64, 62 usable. A /25 holds 128, 126 usable. A /24 holds 256, 254 usable. A /23 holds 512, 510 usable. A /22 holds 1,024, 1,022 usable. You do not need to memorise this. Our Subnet Calculator works out the network address, broadcast address, usable range and host count for any prefix you type in, so you can check a size in seconds instead of doing binary in your head.
A worked example: the 35-person office
Here is a real count from an office I helped size. Thirty-five staff, each with a laptop and a phone on Wi-Fi, that is 70 addresses. Four network printers, three access points, two servers and one NAS, that is 10 more. The meeting room screen and the door panel add 2. That is 82 devices on a normal day. On a busy day, with guests and a training session, it reaches about 100.
Now the growth rule. Take today's count and double it. That sounds generous, and it is meant to be. It covers new hires, the second floor you might take next year, and the slow creep of devices nobody plans for. One hundred doubled is 200 usable addresses needed. A /25 gives 126, which is already too small today, let alone after growth. A /24 gives 254, which fits with room to spare. A /23 gives 510, which is more than this office needs and leaves half the range empty forever.
So the answer for this office is a /24. It is the default size for a small office for a reason: big enough for a couple of hundred devices, small enough to keep tidy, and every router and printer on earth understands it.
The mistake that forces a renumber
The classic mistake is sizing for today and nothing else. Someone counts 60 laptops, sees that a /25 holds 126, and picks it because it fits. Then the phones join the Wi-Fi, then the printers, then a hot-desking day fills the pool, and the subnet is full within a year. Widening a subnet after the fact is not a setting you flip. You either renumber every static device and rebuild the DHCP scope, or you add a second subnet and live with routing between them. Both jobs are far more disruptive than picking a bigger prefix on day one.
There is a second trap worth naming. If your staff VPN in from home, do not pick the same private range their home routers use. Half the home routers in the world sit on 192.168.1.0/24, and if your office uses the same range, a remote worker's laptop cannot tell office addresses from home addresses and the VPN quietly fails for some of them. A range in 10.x.x.x, for example 10.20.30.0/24, dodges the collision almost every time. If you are unsure what your office currently uses, our IP Lookup shows your public address and the network you are reaching us from, which is a useful starting point for the conversation with whoever manages the router.
What to do first
Do the count today, before the next device arrives. List every device type, add the guests, double the total, and pick the smallest prefix that holds the doubled number. Run your chosen size through the Subnet Calculator to confirm the usable range and the broadcast address, then hand the numbers to whoever manages the router. If your count lands near the top of a /24, take the /23. Address space in the private ranges costs nothing, and a subnet with breathing room is a problem you never have to think about again. If you are also setting up a static address for a device at home, our post on working out the right IP range before you set a static IP at home walks through the same counting habit on a smaller scale.
A new post lands here every day. If there is a topic you want covered, email ask@websmartstudios.com.