Logo

MonoCalc

/

Network Capacity Planner

Networking

Link Configuration

⚠️ Moderate – Consider Upgrade Soon

4 of 4 links active · ACTIVE ACTIVE

32.3% headroom

Raw Capacity

40.00 Gbps

4 × 10 Gbps

After Overhead

38.00 Gbps

5% overhead removed

Usable Capacity

26.60 Gbps

70% target

Available Headroom

8.60 Gbps

32.3% free

Capacity Pipeline

Raw Capacity

40.00 Gbps

Effective (after overhead)

38.00 Gbps

Usable (after utilization target)

26.60 Gbps

Current Peak Traffic

18.00 Gbps

Per-Link Utilization

45.0%

Peak traffic spread across 4 active links. Best practice: keep below 70–80%.

Traffic Growth Projection

Exhaustion: 2029
YearProjected TrafficUsable CapacityStatus
202721.60 Gbps26.60 Gbps✅ OK
202825.92 Gbps26.60 Gbps✅ OK
202931.10 Gbps26.60 Gbps⚠️ Exceeds

🔴 Recommend upgrading capacity before 2029. Additional bandwidth needed: 4.50 Gbps.

About This Tool

🌐 Network Capacity Planner – Estimate, Analyze, and Plan Bandwidth

The Network Capacity Planner helps network engineers, IT architects, and system administrators quantify how much usable bandwidth a network segment can deliver — and how long that capacity will last as traffic grows. By combining link aggregation, protocol overhead, redundancy modes, and compound annual growth projections, it turns raw link-speed figures into actionable capacity decisions.

🔢 Core Capacity Formulas

Every result flows through a three-stage pipeline. Start with the raw total capacity — simply the number of active links multiplied by the per-link speed:

Raw Capacity = Active Links × Link Speed

Next, subtract protocol overhead — the bytes consumed by Ethernet frames, TCP/IP headers, and any encapsulation layers (MPLS, IPsec, GRE, VXLAN):

Effective Capacity = Raw Capacity × (1 − Overhead% / 100)

Finally, apply a utilization target to leave headroom for traffic bursts and avoid congestion:

Usable Capacity = Effective Capacity × (Utilization Target% / 100)

🔗 Redundancy Modes Explained

The redundancy mode determines how many physical links contribute to throughput. Choosing the wrong model leads to over-estimated capacity — a common cause of unexpected congestion after a failover event.

ModeActive LinksTypical Use Case
Active-Active (LACP/ECMP)All N linksLAG bonding, ECMP routing
Active-Passive N+1N − 1 linksSingle standby for HA
Active-Passive N+2N − 2 linksDual standby for critical paths
1:1 Hot StandbyN / 2 linksMirror pairs (primary + backup)
ECMPAll N linksEqual-cost load sharing across paths
CustomUser-definedFlexible multi-path topologies

📈 Traffic Growth Projection (CAGR)

Enterprise traffic typically grows 20–40% per year, driven by video conferencing, cloud workloads, and IoT device proliferation. The planner uses the compound annual growth rate (CAGR) formula to project demand year by year:

Projected Traffic (year n) = Current Peak × (1 + Growth Rate / 100)^n

When projected traffic exceeds usable capacity, the tool highlights the capacity exhaustion year and calculates exactly how much additional bandwidth you need to order before that deadline.

⚡ Protocol Overhead Quick Reference

Ethernet (raw frame overhead)

1–3%

TCP/IP over Ethernet

3–5%

MPLS (per label)

~4 bytes/label

IPsec / VPN tunnels

5–15%

GRE encapsulation

~24 bytes/packet

VXLAN overlay

~50 bytes/packet

🎯 Utilization Target Best Practices

A common mistake is provisioning links at 100% of their rated speed. Under bursty traffic — video streams, large file transfers, backup windows — momentary utilization spikes cause queue buildup and packet drops that degrade application performance well before the link is saturated on average.

Industry-recommended utilization targets by link type:

  • Enterprise LAN uplinks: 70–80% — balances cost and burst headroom.
  • WAN and internet circuits: 60–70% — higher latency sensitivity.
  • Data centre interconnect (DCI): 50–65% — strict SLA environments.
  • ISP peering/transit: 40–60% — traffic engineering margins.

🏢 Primary Use Cases

This tool is designed for planning scenarios including:

  • Data centre interconnect (DCI) — sizing 10/40/100 GbE links between sites with redundancy and growth margins.
  • Campus and enterprise WAN — aggregating branch uplinks and verifying that MPLS or SD-WAN circuits can sustain peak loads.
  • Hybrid-cloud uplink sizing — calculating how many dedicated connections or VPN tunnels are needed for cloud-bound traffic.
  • Disaster-recovery link planning — confirming standby circuits can carry full production load after a failover event.
  • Network refresh and upgrade budgeting — producing quantified capacity gap reports to justify hardware procurement requests.

📊 Understanding the Output Metrics

The planner produces a complete capacity pipeline: raw → effective → usable → headroom. Each stage shows a concrete bandwidth figure so you can trace exactly where capacity is being consumed. The per-link utilization metric shows what fraction of each individual link's rated speed is being used — useful for identifying whether LACP hashing is distributing traffic evenly. The SLA coverage check verifies that committed information rates (CIR) are protected even after derating for overhead and utilization targets.

Results are auto-scaled into the most readable unit (bps, Kbps, Mbps, Gbps, or Tbps) so you always see 26.6 Gbps rather than 26,600 Mbps.

Frequently Asked Questions

Is the Network Capacity Planner free?

Yes, Network Capacity Planner is totally free :)

Can I use the Network Capacity Planner offline?

Yes, you can install the webapp as PWA.

Is it safe to use Network Capacity Planner?

Yes, any data related to Network Capacity Planner only stored in your browser (if storage required). You can simply clear browser cache to clear all the stored data. We do not store any data on server.

How does the Network Capacity Planner work?

Enter the number of links, their speed and unit, protocol overhead, redundancy mode, and utilization target. The tool computes raw capacity, derates it for overhead and safe utilization, then compares it against your current peak traffic. If you supply a growth rate and planning horizon, it projects year-by-year demand and flags the year capacity will be exhausted.

What redundancy modes are supported?

Six modes are available: Active-Active (all links forward traffic), Active-Passive N+1 (one standby link), Active-Passive N+2 (two standby links), 1:1 Hot Standby (half the links are standby), ECMP (equal-cost multipath, all links active), and Custom (you specify how many links are active). Each mode changes how many links contribute to usable throughput.

Why should I set a utilization target below 100%?

Running a link at 100% causes queuing delays, buffer bloat, and packet loss during traffic spikes. Industry best practice is to plan for 70–80% peak utilization so burst headroom is always available. Setting a utilization target of 70% means the tool treats 70% of effective link capacity as the safe operational ceiling.

How is the capacity exhaustion year calculated?

Using the compound annual growth rate (CAGR) formula: Projected Traffic (year n) = Current Peak × (1 + Growth Rate / 100)^n. The tool finds the first year n where projected traffic exceeds usable capacity. If traffic already exceeds usable capacity, the exhaustion year is flagged immediately as the current year.

What does protocol overhead mean and how much should I use?

Protocol overhead accounts for TCP/IP headers, Ethernet framing, and encapsulation bytes added by the protocol stack. Typical values: raw Ethernet ≈ 1–3%, TCP/IP ≈ 3–5%, MPLS adds ~4 bytes per label, IPsec/VPN adds 5–15%, GRE adds ~24 bytes, VXLAN adds ~50 bytes. For most enterprise WAN planning, 5% is a safe default.

How accurate are the results for real network planning?

Results are mathematically precise given the inputs. Real-world throughput also depends on TCP window size, round-trip latency, packet loss, hardware forwarding rate, and burst behaviour. Use these results as a planning baseline and add a 10–20% safety margin when making procurement decisions.