Short answer: more than the rule everyone still uses, and the number that matters is not how fast your internet is. It is how many devices are sitting on it at nine o’clock at night.
The question a hotelier usually asks their internet provider is “how fast is the line?”. It is the wrong one, and it is why properties keep paying for more megabits and keep getting the same complaints.
A 500 Mbps line sounds enormous. Split it between three hundred devices on a Friday night and it is not. What decides whether your guests are happy is not the size of the pipe — it is how many things are drinking from it, and whether anything stops one guest taking most of it.
So the useful questions are: how many devices, doing what, at the same time — and what happens when one of them misbehaves.
Every planning rule written before about 2018 assumed a guest brought a phone and maybe a laptop. That guest no longer exists.
The Wi-Fi Alliance put the global average of connected devices per person at more than nine by 2025, and hospitality sees the highest concentration of anywhere.
A single occupied guest room now typically holds three to five things that want the network: phones, a laptop, a tablet, a watch, and increasingly a television streaming in 4K.
More than eight in ten guests travel with at least two devices. Planning for one per guest under-counts your network by a factor of three before anybody has checked in.
The rule to retire: allocating a flat 5–10 Mbps per room. It was reasonable a decade ago. It is now roughly a third of what a full room needs on a bad evening.
Nobody uses their full share at once, which is the only reason any of this works. Network people call the assumption a contention ratio, and it is worth understanding because it is where the planning actually happens.
A contention ratio of 50:1 means you are betting that only one device in fifty is pulling hard at any moment. On a 250 Mbps line with two hundred devices connected, that maths gives you roughly four devices genuinely active, and about 62.5 Mbps each when they are.
That is a comfortable number. The bet fails when the assumption fails — a rainy afternoon in low season, a conference in the function room, or a school holiday when every family is streaming at once.
Which is why the ratio is only half the answer. The other half is a ceiling on what any single device can take, so that when the bet fails it fails gently rather than all at once.
46-room resort, beach club open to the public
Rooms at 70% occupancy × 4 devices = ~129 devices
Beach club and restaurant = ~40 devices
Staff and back of house = ~15 devices
Total: ~184 concurrent devices
On a 250 Mbps line at 50:1, that is comfortable. At 20:1 — a wet afternoon, everybody indoors — it is nine active devices sharing 250 Mbps, and it holds only because nobody is allowed to take more than their cap.
A remote coastal resort put in satellite internet so it could finally promise guests something reliable. Three days later a $2,847 overage bill arrived.
One guest had been streaming 4K on three devices and had used 89 GB in forty-eight hours. Nothing was broken. Nobody had done anything against the rules, because there were no rules — the network had no per-guest ceiling, no session limit and no data cap, so it did exactly what it was asked.
This is the specific risk for properties on satellite or metered connections, which in practice means a great many resorts in Indonesia, Thailand and the Philippines. A speed cap is not about being mean to guests. It is about the difference between a predictable monthly cost and an unpredictable one.
Speed — a ceiling per device, so one guest cannot take the line.
Session length — access that ends on its own rather than running until somebody notices.
Devices per stay — so one room is not running fifteen tablets, and a shared password cannot be passed around a car park.
All three are enforced by the equipment itself, not promised on a page. What that looks like →
These are starting points, not laws. The right answer depends on your line, your occupancy and whether your connection is metered. But a property with no limits at all is better off with these than with nothing.
Comfortable for email, browsing, video calls and one stream. Session runs to checkout with the grace period you set.
A guest paying five times the rate notices the Wi-Fi too. Rate code picks the plan automatically.
Enough to be useful at the beach club or restaurant. Short enough to keep the tables turning.
Speed limits alone will not stop a 4K stream running all night. Pair them with a daily allowance — 500 MB free, more on request.
Per-guest speed, time and device limits are enforced by the equipment running your guest network, not by a box we sell you. Most hotel-grade Wi-Fi already supports it.
Aruba · Ruckus SmartZone · Cisco WLC · Meraki
Forty makes have their own page saying plainly what they can and cannot do. See the full list → — or send us a photo of the box your Wi-Fi comes from and we will tell you.
At around 70% occupancy and four devices a room, expect roughly 140 guest devices plus staff and public areas. A 200–300 Mbps line handles that comfortably with per-device caps in place, and struggles badly without them. The caps matter more than the headline speed.
Three is the usual answer for a standard room and five or six for a suite. Below three you will annoy a family; above six you are effectively allowing one room to run a small office.
Not at sensible numbers. Ten megabits streams high definition and runs a video call at the same time. What upsets guests is not a cap — it is the evening when someone else has taken the whole line and nothing loads.
Almost certainly not. Speed, time and device limits are standard on hotel-grade equipment and on most of the smaller gear too. Forty makes are listed on our supported equipment page, and the answer for the great majority is that one setting changes.
A travel router lets one credential serve a dozen devices, which is exactly what a per-stay device limit exists to prevent. Limits applied per credential rather than per MAC address are the ones that hold, because a MAC address can be changed and a login cannot.
Tell us the property and what the Wi-Fi runs on, and we will tell you what it can enforce today — and what it cannot.
