A 100-room hotel network carries far more than guest WiFi. The same cabling and switches typically serve the front desk, the PMS, payment terminals, phones, TVs, door locks, cameras and back-office computers. Design it as one flat network and a single problem, or a single compromised device, affects everything. Design it properly and each system gets the performance and isolation it needs.
This guide walks through the network design we use as a starting point for a 100-room limited- or select-service hotel in Ontario. Every building is different, so treat it as a framework rather than a bill of materials.
1. Start With the Busiest Night, Not an Average One
Size the network for a full house plus an event: a tournament weekend, a wedding block or a conference. A useful planning assumption is two to four connected devices per guest, plus TVs, staff devices and building systems. At 100 rooms that can mean several hundred active devices at once, many of them streaming video. Hotel WiFi usually fails on those nights, not on a quiet Tuesday. (More on that in why hotel WiFi slows down when the hotel is full.)
2. Internet Circuit and Backup
- Primary circuit: business fibre where available. For 100 rooms, many properties land somewhere between several hundred megabits and 1 Gbps or more, depending on guest mix and whether TVs stream over the internet.
- Backup circuit: a second provider or a cellular backup with automatic failover, so check-in, payments, phones and the cloud PMS keep working. See backup internet for hotels.
- Per-device limits: bandwidth limits per guest device so one heavy user cannot slow the whole floor.
3. Separate Networks (VLANs) for Each System
| Network | What is on it | Key rule |
|---|---|---|
| Guest WiFi | Guest phones, laptops, tablets | Client isolation on; internet only; no access to any hotel system |
| Staff / office | Front desk and back-office PCs, printers | No access to guest network; tightly controlled access to payments |
| Payments (PCI) | Payment terminals and payment-connected systems | Isolated and firewalled; only required traffic allowed. See PCI compliance |
| Voice | IP phones, PBX, room phone gateways | Prioritized with QoS for clear calls |
| TV / casting | Hospitality TVs, casting servers | Per-room pairing so guests only cast to their own TV |
| Building systems | Door locks, cameras, thermostats, building controls | Internet access only where the vendor requires it |
| Management | Switches, access points, controllers | Reachable only by administrators, ideally over VPN |
4. Access Points: Placement Beats Power
- Count: many 100-room hotels need roughly 25 to 35 access points, more with concrete or block walls, plus coverage for the lobby, breakfast room, meeting rooms, pool and fitness room. A site survey sets the real number.
- In-room or in-wall vs. corridor: access points in or near guest rooms give the most consistent experience. Corridor-only designs push signal through doors and bathroom walls and often leave the far side of the room weak.
- Lower power, narrower channels: in dense hotel deployments, lower transmit power and 20 or 40 MHz channel widths usually improve roaming and reduce interference between access points. Turning the power up rarely fixes complaints.
- Know your local RF: near airports, some 5 GHz DFS channels can be forced off by radar events. Near Pearson, for example, we often exclude them so access points do not keep changing channels.
- WiFi 6 or newer for new installs, with 5 GHz as the primary band for guests.
5. Switching and Power
- PoE budget: add up the power draw of every access point, phone and camera, then leave headroom. Running out of PoE budget is a common cause of access points randomly rebooting.
- Uplinks: multi-gigabit or 10G uplinks between the core and each floor’s switch, so one floor’s traffic does not bottleneck.
- Battery backup: UPS units for the core, the gateway and each IDF closet so phones and the front desk survive short power cuts.
- Labelled, documented cabling so any technician can trace a fault quickly.
6. Gateway, Firewall and Captive Portal
The gateway enforces the separation between networks, applies bandwidth limits and handles guest login. A captive portal can be simple (a room-number password) or integrated with the PMS so guests log in with their last name and room number. Keep the portal lightweight: pages that load external fonts or scripts often hang before the guest is online.
7. Monitoring From Outside the Building
If the internet goes down, an on-site controller cannot tell anyone. Monitor the hotel from an external service so the outage is caught and acted on before the front desk starts taking complaints. Managed WiFi plans normally include this. See managed IT for hotels.
Example Bill of Materials (Planning Level)
| Component | Typical quantity for 100 rooms |
|---|---|
| Indoor access points | 25 to 35, plus outdoor units if needed |
| PoE access switches | One per floor or IDF closet, sized for PoE budget |
| Core switch | 1, with fibre or multi-gig uplinks |
| Gateway / firewall | 1 (high availability optional) |
| Controller | Cloud-managed or on-site hardware controller |
| UPS | Core and each IDF closet |
| Internet | Primary fibre plus backup circuit |
For budget ranges, see how much hotel WiFi installation costs in Ontario, and for platform choice, TP-Link Omada vs Ruckus vs Aruba for hotel WiFi.
Frequently Asked Questions
How many access points does a 100-room hotel need?
Often around 25 to 35 for guest rooms, plus public areas, but construction makes a big difference. Concrete, block and stone walls can require an access point in or near nearly every room. A site survey gives the real number.
Should guest WiFi and staff systems share a network?
No. Guest devices should be on their own isolated network with internet access only. Front desk, payments, phones, TVs and building systems each belong on separate networks with firewall rules between them.
Do we need a second internet connection?
For most hotels, yes. Check-in, cloud PMS, card payments and VoIP phones all depend on the internet. A backup circuit with automatic failover keeps the hotel running during an outage.
Can we reuse our existing cabling?
Often. If the existing runs reach the right locations and test clean, they can be reused, which saves a significant part of the cost.
Talk to AutoSecure
Planning a new build, renovation or WiFi upgrade? AutoSecure designs and manages hotel networks across Ontario, from site survey to guest WiFi, phones and TV. Call 226-476-3358 or book a free hotel technology assessment.
See also: hotel WiFi login pages and captive portals and hotel TV casting.