Network Redundancy Concurrent User Capacity Estimator
The Network Redundancy Concurrent User Capacity Estimator estimates how many equal-bandwidth users can still be supported after a specified number of redundant links fail. It combines link count, capacity per link, failure tolerance, a usable-capacity factor, and the target bandwidth per active user. This makes it suitable for resilient access networks, clustered gateways, redundant uplinks, or other designs where user capacity must be evaluated in the degraded state rather than only when every path is healthy.
The calculation answers a failover capacity question: after the modeled failures, how many users can the surviving aggregate bandwidth support at the selected per-user target? The usable-capacity factor gives room for protocol overhead, bursts, and operational reserve. It does not model CPU, session-table, radio, storage, or application limits, so the network result should be compared with other system bottlenecks before being treated as end-to-end capacity.
Calculator inputs
links
Mbps
links
%
Mbps
Result
—
supported concurrent users after failure
Surviving aggregate bandwidth—
Usable failover bandwidth—
Capacity lost to failure—
1. Define the redundant link pool Enter the total number of equal-capacity links that can carry the user traffic.
2. Enter capacity per link Use the sustained link capacity available to this service.
3. Set the failure case Choose how many links may be down at once while service is expected to continue.
4. Reserve operating capacity Apply a usable percentage below 100% when the design needs headroom for overhead and bursts.
5. Set the per-user target Enter the Mbps each active user should receive, then read the whole-user failover capacity.
Result: 300 concurrent users after one link failure.
Interpretation: The surviving three links can support three hundred 8 Mbps users while reserving 20% of the remaining link capacity.
Why does the calculator use the failed state?
Redundancy is valuable only if service remains acceptable when components are unavailable. Evaluating the degraded state shows whether capacity survives the failure scenario the design is meant to tolerate.
Can I use different capacities for different links?
Not in this equal-link model. For mixed circuits, calculate the surviving aggregate bandwidth for each realistic failure case and use the smallest relevant total.
What does the usable-capacity factor represent?
It is a planning reserve applied after failures. You can use it to leave room for overhead, bursts, non-user traffic, or an operational utilization ceiling.
Why is the user result an integer?
The calculator rounds down because each counted user must receive the full selected bandwidth target. The remaining fraction of capacity is shown implicitly as unused residual bandwidth.
Is this the same as session capacity on a firewall or gateway?
No. This is bandwidth-based concurrency. Device session tables, CPU, connection rates, licenses, and application limits can cap users before bandwidth does.