Hotel IPTV Bandwidth and Multicast Reference by Room Count

Hotel IPTV bandwidth is set by the channel lineup on the core and by stream count on each edge port, not by room count. A 60-channel H.264 HD lineup at 8 Mbps needs about 480 Mbps on the multicast backbone whether the hotel has 150 rooms or 600, while each guestroom port only ever carries the one or two streams that its TV is watching.

This reference is written by Singapore-based AV and IPTV integrator Prestige Solutions for hotel IT managers who have to size switches, uplinks and VLANs before an IPTV system is installed or retrofitted. All bitrates below are planning figures as of 2026; confirm the exact encoder settings with the headend supplier before ordering hardware.

Per-stream bitrates to plan with

Use the encoder output bitrate plus about 10% for IP, UDP and RTP overhead, and plan for the highest profile the headend will actually send. The table lists the figures we use at the design stage.

Two practical notes follow from the table. First, switching the lineup from H.264 to HEVC roughly halves backbone load, but only if every guestroom TV decodes HEVC; one older TV model on a floor forces a dual-format headend. Second, UHD channels are the expensive line item: five UHD channels at 28 Mbps consume as much backbone as fifteen HD channels.

Backbone load by channel lineup

With multicast, every channel that at least one TV is watching crosses the core once, so the worst case is the whole lineup flowing at the same time. That worst case is common in the evening and during major sports events, so design for it rather than for average viewing.

The uplink column keeps multicast below roughly 60% of link capacity, which leaves room for guest Wi-Fi backhaul, VOD and management traffic if they share the same uplink. When IPTV has its own physical uplinks, 1 Gbps can run closer to 80% for a pure multicast load.

Edge port and access switch load

A guestroom port carries only the streams its TV has joined, so a 1 Gbps access port is never the constraint. The constraint is the access switch uplink when snooping is misconfigured. With IGMP snooping working, a 48-port floor switch receives only the channels that the TVs on that floor are watching; if 30 rooms watch 18 different channels, the floor uplink carries 18 streams, around 162 Mbps in H.264 HD.

Without IGMP snooping the switch floods every multicast group to every port in the VLAN. The same floor now receives the full 60-channel lineup on every guestroom port, and devices that are not TVs—room controllers, IP phones, minibar sensors—get flooded as well. This is the most common reason for guestroom devices dropping off the network after an IPTV go-live.

Multicast settings that must be in place before go-live

The multicast configuration is a short list, but each item is a known failure point on hotel networks. We check the following on every access and distribution switch before any channel goes live.

• IGMP snooping enabled on the IPTV VLAN on every switch in the path, not only on the core.
• One IGMP querier per VLAN, normally on the core or distribution switch. Without a querier, snooping tables age out after about 260 seconds with IGMPv2 defaults and channels freeze mid-programme.
• IGMP version matched to the TVs: IGMPv2 for most hospitality TVs; IGMPv3 only if the headend uses source-specific multicast.
• Fast leave (immediate leave) on guestroom ports, so a channel change does not leave the old stream running for several seconds.
• Unknown multicast flooding disabled on the IPTV VLAN.
• Multicast group range documented, for example 239.x.x.x administratively scoped addresses, one per channel, with no overlap with other building systems.
• Jumbo frames not required; standard 1500-byte MTU is correct for MPEG-TS over UDP.

VOD and unicast load by room count

Unicast services are the only part of hotel IPTV that scales with room count, because every viewer gets a separate stream. Plan with peak concurrency, not the average.

The concurrency percentages are conservative design assumptions, not measured usage. Actual VOD uptake in hotels with casting and streaming apps on the TV is usually lower, but the VOD server's network interface should still be sized for the design figure. A 1 Gbps server port is tight above roughly 80 concurrent HD streams; use 10 Gbps or bonded links beyond that.

Worked example: 320-room hotel

A 320-room property with a 65-channel lineup, of which 4 are UHD, and a VOD library shows how the figures combine.

• Multicast backbone: 61 HD × 9 Mbps + 4 UHD × 28 Mbps = 549 + 112 = 661 Mbps.
• VOD unicast: 320 × 10% = 32 streams × 11 Mbps = 352 Mbps.
• Peak at the core: about 1.01 Gbps of IPTV traffic.
• Result: 10 Gbps core-to-distribution links; 1 Gbps floor uplinks are acceptable only if snooping limits each floor to fewer than about 60 active streams.

If the same hotel moves the HD channels to HEVC, the multicast figure drops to 61 × 5.5 + 112 = 448 Mbps, and total peak falls to about 800 Mbps. The saving is real, but it depends on TV decoder support, which is why the guestroom TV model list should be fixed before the headend format is chosen.

VLAN and QoS layout

IPTV belongs in its own VLAN, with QoS marking so it is not starved by guest Wi-Fi at peak. A typical layout on a converged hotel network looks like this:

• IPTV multicast VLAN: headend encoders, multicast groups, TVs.
• IPTV management VLAN: TV management server, EPG, portal, firmware updates.
• Guest Wi-Fi VLANs: separate, with client isolation.
• Back-of-house and building systems VLANs: kept out of the IPTV multicast domain.

Mark IPTV traffic at DSCP AF41 or CS4 and trust that marking on the uplinks, so video is queued ahead of best-effort guest traffic. Guest Wi-Fi rate limits should be set per client rather than relying on QoS alone.

Acceptance checks before handover

Bandwidth planning is only confirmed when the network is loaded the way guests will load it. The checks we run at commissioning are:

1. Tune every channel on one TV per floor and confirm the channel change time stays under about 2 seconds.
2. Run all channels at once on a test port and confirm the floor uplink utilisation matches the calculation.
3. Leave a TV on one channel for 30 minutes and confirm no freeze at the IGMP timeout interval.
4. Unplug the querier switch and confirm a backup querier takes over.
5. Check that a laptop on a guestroom data port does not receive multicast traffic it has not joined.

The results should go into the handover pack with switch configurations, the channel-to-multicast-group list and the uplink utilisation figures. More project references are on the Prestige Solutions home page.

FAQ

Why do IPTV channels freeze after a few minutes on a new network?

The usual cause is IGMP snooping without an IGMP querier on the VLAN. The switch stops receiving membership reports, ages out the group after its timeout, and the stream stops until the TV rejoins. Configure one querier per IPTV VLAN.

Can IPTV share the same switches as guest Wi-Fi?

Yes, if IPTV runs in its own VLAN with IGMP snooping, a querier and QoS marking, and the uplinks are sized for full-lineup multicast plus Wi-Fi peak. Shared switches are common in retrofits where new cabling is not practical.

How much internet bandwidth does hotel IPTV need?

Very little for a local headend, because channels are received by satellite or terrestrial feeds and encoded on site. Internet capacity matters for streaming apps and casting on the TV, which should be planned as guest internet traffic, not IPTV.

Recommended next step

Contact Prestige Solutions to review your site drawings and current operating pattern. Call +65 8010 2337, message us on WhatsApp, or email sales@prestigesolutions.com.sg. You can also browse the full product range before the site walk.