Networking calculators give engineers, students, and IT professionals the numbers behind IP addressing, subnetting, bandwidth planning, and protocol design. Every calculator here covers not just the formula but the specific trap that catches engineers in real deployments: why AWS gives you 251 usable IPs from a /24 instead of 254, why your 100 Mbps connection downloads at 12.5 MB/s, and why /31 subnets are valid for point-to-point links but most CCNA materials still teach /30 as the minimum.
Every networking calculation has a version that works on paper and a version that works in production — and the gap between them is where most deployment problems originate. The standard subnetting formula (2^n − 2 usable hosts) is correct for traditional networks but wrong for AWS VPCs, which reserve 5 IPs per subnet instead of 2. The advertised bandwidth calculation (100 Mbps = 100 megabits per second) is correct but the download speed is 12.5 MB/s — a factor-of-8 conversion that confuses every user who asks why their internet is "slower than advertised." The /30 minimum subnet for point-to-point links is what every CCNA textbook teaches, but RFC 3021 has allowed /31 for over two decades and modern equipment universally supports it. These are the gaps the networking calculators here are built to address.
The subnet calculator computes network address, broadcast address, usable host range, subnet mask, and wildcard mask from any IPv4 address and CIDR prefix. Usable hosts = 2^(32−prefix) − 2. For /24: 2^8 − 2 = 254. For /28: 2^4 − 2 = 14. The −2 removes the network address (all host bits = 0) and broadcast address (all host bits = 1). In AWS, Azure, and GCP VPCs, cloud providers reserve additional IPs beyond the standard two. AWS reserves 5 per subnet: network address, VPC router, DNS server, future use reservation, and broadcast. A /24 in AWS gives 256 − 5 = 251 usable IPs, not 254. Engineers who plan cloud subnets using standard formulas consistently overestimate available capacity by 3 IPs per subnet — enough to cause addressing problems when subnets are tightly sized.
The single most asked networking question from non-technical users is "why is my internet slower than what I pay for?" The answer is almost always the bits-to-bytes conversion. 1 byte = 8 bits. 100 Mbps (megabits per second) ÷ 8 = 12.5 MB/s (megabytes per second) maximum download speed. ISPs advertise in Mbps because larger numbers look better. File sizes are in MB and GB. A 1 GB file download on a 100 Mbps plan takes a minimum of (1,000 MB × 8) ÷ 100 Mbps = 80 seconds — the user sees "1 GB / 12.5 MB/s = 80 seconds" and calls their ISP. The actual speeds are identical. The bandwidth calculator converts between Mbps, Gbps, MB/s, and GB/s and calculates file transfer times for any file size and link speed combination.
5G theoretical peak throughput for mmWave spectrum reaches 20 Gbps under ideal lab conditions. Real-world deployed 5G on Sub-6 GHz spectrum — which covers 95%+ of current 5G deployments — delivers 100 to 400 Mbps download in typical conditions. mmWave 5G delivers 500 Mbps to 2 Gbps but requires line-of-sight, is blocked by buildings and rain, and covers only small outdoor areas in selected dense urban deployments. 4G LTE typical real-world: 20 to 100 Mbps. The gap between theoretical and real-world 5G comes from cell load sharing among many simultaneous users, distance from tower, building penetration loss (signals weaken passing through walls), and spectrum availability at any given location and time. The 5G/LTE throughput calculator shows realistic expected throughput based on spectrum band, distance, and network generation.
The /31 subnet that saves addresses but most engineers don’t know exists: RFC 3021 (published in 2000) allows /31 subnets for point-to-point links — two addresses, both usable, no network or broadcast address needed because there are only two hosts. A /30 (the traditional minimum) has 4 addresses but wastes 2 on network and broadcast, giving only 2 usable IPs for the two router interfaces. At scale: an ISP with 10,000 point-to-point links uses 40,960 addresses with /30 subnets and only 20,480 with /31 subnets — saving a full /18 address block. All modern Cisco, Juniper, Arista, and Linux networking equipment supports /31. Most CCNA materials still teach /30 as the minimum useful subnet, leaving engineers unaware that /31 saves addresses on every point-to-point link in their network.
Total IPs = 2^(32−prefix). Usable hosts (standard) = total − 2. AWS usable = total − 5. Each prefix doubling (e.g., /24 to /25) halves the address space.
| CIDR Prefix | Subnet Mask | Total IPs | Usable (Standard) | Usable (AWS) | Typical Use |
|---|---|---|---|---|---|
| /8 | 255.0.0.0 | 16,777,216 | 16,777,214 | 16,777,211 | Class A, large enterprise |
| /16 | 255.255.0.0 | 65,536 | 65,534 | 65,531 | Class B, large VPC |
| /20 | 255.255.240.0 | 4,096 | 4,094 | 4,091 | Medium campus subnet |
| /22 | 255.255.252.0 | 1,024 | 1,022 | 1,019 | Large VLAN |
| /24 | 255.255.255.0 | 256 | 254 | 251 | Standard office/home VLAN |
| /25 | 255.255.255.128 | 128 | 126 | 123 | Half of /24 |
| /26 | 255.255.255.192 | 64 | 62 | 59 | Small VLAN |
| /27 | 255.255.255.224 | 32 | 30 | 27 | Small department |
| /28 | 255.255.255.240 | 16 | 14 | 11 | Small server subnet |
| /29 | 255.255.255.248 | 8 | 6 | 3 | Minimal server cluster |
| /30 | 255.255.255.252 | 4 | 2 | N/A — avoid in cloud | Point-to-point (traditional) |
| /31 | 255.255.255.254 | 2 | 2 (RFC 3021) | N/A — avoid in cloud | Point-to-point (efficient) |
| /32 | 255.255.255.255 | 1 | 1 (host route) | 1 | Single host, loopback |
Divide Mbps by 8 to get MB/s. These are theoretical maximums under ideal conditions. Real-world throughput is typically 70–90% of link speed on LAN, 50–80% on WAN links due to protocol overhead, TCP acknowledgement overhead, and retransmissions.
| Connection Speed | Max Download (MB/s) | 1 GB File | 10 GB File |
|---|---|---|---|
| 10 Mbps | 1.25 MB/s | 13.3 min | 2.2 hours |
| 25 Mbps | 3.1 MB/s | 5.3 min | 54 min |
| 50 Mbps | 6.25 MB/s | 2.7 min | 27 min |
| 100 Mbps | 12.5 MB/s | 80 sec | 13.3 min |
| 250 Mbps | 31.25 MB/s | 32 sec | 5.3 min |
| 500 Mbps | 62.5 MB/s | 16 sec | 2.7 min |
| 1 Gbps | 125 MB/s | 8 sec | 80 sec |
| 10 Gbps | 1,250 MB/s | 0.8 sec | 8 sec |
Theoretical peak vs typical real-world speeds. Real-world speeds vary by carrier, location, time of day, and distance from tower. All figures are for connected, good-signal conditions.
| Network Generation | Spectrum | Theoretical Peak | Typical Real-World DL | Typical Upload |
|---|---|---|---|---|
| 4G LTE | 700 MHz – 2.6 GHz | 150 Mbps | 20 – 100 Mbps | 10 – 50 Mbps |
| 4G LTE Advanced | Multi-band CA | 1 Gbps | 50 – 200 Mbps | 20 – 75 Mbps |
| 5G Sub-6 GHz | 600 MHz – 6 GHz | 900 Mbps | 100 – 400 Mbps | 30 – 100 Mbps |
| 5G mmWave | 24 – 100 GHz | 20 Gbps | 500 Mbps – 2 Gbps | 100 – 500 Mbps |
| 5G mmWave (indoor) | 28/39 GHz | 10 Gbps | 100 – 800 Mbps | 50 – 200 Mbps |
| Wi-Fi 6 (802.11ax) | 2.4 / 5 GHz | 9.6 Gbps | 400 Mbps – 1.2 Gbps | Same as DL |
| Wi-Fi 7 (802.11be) | 2.4 / 5 / 6 GHz | 46 Gbps | 1 – 5 Gbps | Same as DL |
Mbps vs MBps — the confusion that generates more ISP support calls than any other single misunderstanding: Mbps = Megabits per second (lowercase b). MBps = Megabytes per second (uppercase B). 8 bits = 1 byte. 100 Mbps ÷ 8 = 12.5 MB/s. A 100 Mbps internet plan delivers a maximum of 12.5 MB/s — not 100 MB/s. When a user downloads a 1 GB file and sees "80 seconds remaining" on a "100 Mbps" plan, the math is correct: 1,000 MB ÷ 12.5 MB/s = 80 seconds. ISPs market in Mbps because "100 Mbps" sounds faster than "12.5 MB/s." Operating systems (Windows, macOS, iOS, Android) typically display download speeds in MB/s in their file transfer dialogs. The confusion arises at the intersection of these two conventions. The correct way to verify your internet speed: run a speed test in Mbps, then divide by 8 to get your expected download speed in MB/s.
Use the subnet calculator to practice CIDR and subnetting. For CCNA exam preparation, master these reference points without a calculator: /24 = 254 hosts, /25 = 126, /26 = 62, /27 = 30, /28 = 14, /29 = 6, /30 = 2. The pattern is powers of 2 minus 2. For cloud infrastructure design, always subtract 5 instead of 2 when planning AWS or Azure subnets. For enterprise design: use 10.0.0.0/8 for internal addressing, subdivide using /16 for regions or sites, /24 for VLANs, and /28 or /29 for server subnets where host count is small and predictable.
The bandwidth calculator converts between Mbps and MB/s and calculates realistic file transfer times. For WAN planning, derate link capacity by 20–30% for real-world TCP overhead, retransmissions, and protocol headers. A 100 Mbps WAN link sustains approximately 70–80 Mbps of useful data throughput. For LAN links (Gigabit Ethernet), derate by 10–15%. For backup and replication sizing, calculate in GB/s for large data transfers: a nightly backup of 500 GB over a 1 Gbps link requires 500 GB ÷ 125 MB/s = 66.7 minutes at 100% link utilisation — which is unrealistic. Budget 90 minutes minimum at 80% utilisation.
The BGP AS path calculator looks up Autonomous System Numbers and shows routing path information. Use it to understand why traffic from your network to a destination takes a specific path, identify ISP peering quality for specific destinations, and plan traffic engineering. The NAT/PAT session calculator estimates concurrent session counts for sizing NAT table capacity on firewalls and routers. PAT (port address translation) supports up to 65,535 sessions per public IP per protocol. A small office with 50 users averaging 50 concurrent sessions each needs 2,500 NAT table entries — well within any modern firewall’s capacity. Large ISP or data centre deployments with millions of sessions require hardware-accelerated NAT.
Three calculation errors appear repeatedly across real deployments. First: planning AWS/Azure subnets with standard formulas and discovering 3 fewer usable IPs than expected per subnet — which cascades into addressing conflicts at scale. Second: reporting bandwidth in Mbps to stakeholders who interpret the number as MB/s, creating confusion about actual transfer performance. Third: using /30 subnets for all point-to-point links by habit when /31 (RFC 3021) would save half the address space on each link — multiplied across thousands of point-to-point links in a service provider network, this is a material IPv4 address savings.
Most used tools across all 14 categories