Focused lineup
You keep 18 premium and news channels open upstream all day. Viewers on your panel number in the hundreds.
≈ 18 connections while those 18 pulls stay active.
Guides
Connections Explained
Concurrent upstream connections measure how many live channels your server pulls at the same time — not how many viewers watch afterward.
Definition
What a connection is
In Restream plans, a connection is one concurrent upstream channel pull from your IPTV server (or load balancer that fronts it) to the restream source.
If your server holds 25 different live channels open upstream at the same moment, that typically uses about 25 connections — regardless of how many end users are watching those channels through your panel.
Plans do not imply unlimited viewers, unlimited bandwidth, or content redistribution rights. Actual usage depends on your configuration and simultaneous upstream requests.
Counts toward the plan
Simultaneous live channel pulls from your servers to the upstream source.
Does not equal
Individual end-user seats, device licenses, or “one connection per household viewer.”
Catalogue ≠ load
13,500+ is a listed catalogue figure. Peak concurrent pulls determine the plan size you need.
Examples
How counting looks in practice
Illustrative scenarios only. Your panel’s buffering, restart behaviour, and duplicate pulls can change real usage.
Peak evening load
Daytime pulls stay near 40. At peak you open 95 channels upstream for sports and entertainment.
Plan for ≈ 95 if that peak is regular — not for daytime 40 alone.
Duplicate pulls
Two servers each pull the same 30 channels without sharing one upstream cache. That can approach 60 concurrent pulls.
Design matters — architecture can multiply usage.
Server load
20 channels open
Concurrent upstream
Plan usage
≈ 20 connections
Against your package
Panel viewers
Separate metric
Your redistribution layer
Planning
Tips for choosing a connection count
Measure peak concurrent pulls
Log or observe how many live sources your servers request at the busiest hour. Size the plan to that peak, with a modest buffer if your lineup grows.
Avoid pulling the whole catalogue
Importing a large M3U does not require every entry to be active. Only open upstream the channels you actually need concurrently.
Account for multiple servers
Each independent pull path can add usage. Share caches or centralize pulls where your stack allows, then whitelist every public IPv4 that will request streams.
Validate with a trial
The free trial offers up to 10 connections for 12 hours (starts on first playback). Use it to observe real concurrent pull behaviour before buying.
Next step
Match load to a monthly plan
Published packages start at 30 concurrent connections and scale through 50, 100, 200, and 500. Prices are in EUR and billed monthly. Need a different count? Describe your peak load on WhatsApp.
Paid activation requires public IPv4 whitelisting and is completed manually after payment verification.
FAQ
Connection questions
No. One connection is one concurrent upstream channel pull. Many viewers can watch a channel after it is redistributed inside your infrastructure without each viewer adding an upstream connection.
Listed catalogue size (for example 13,500+) is not the same as active pulls. Connections are consumed when your server requests channels concurrently — not merely because channels appear in a list.
Contact support before you exceed your limit. Monthly plans from 30 to 500 connections are listed on pricing; custom counts can be discussed on WhatsApp.
The free trial includes up to 10 concurrent connections for 12 hours, beginning on first playback.