Megabit per second to Gibibit per second

Because ISPs advertise in megabits (Mb) while download managers show megabytes (MB). There are 8 bits in a byte, so 100 Mbps ÷ 8 = 12.5 MB/s. Your connection is working perfectly — it is just a unit mismatch that has confused people for decades.

Netflix recommends 25 Mbps for 4K, YouTube suggests 20 Mbps, and Apple TV+ needs about 25 Mbps. In practice, 50 Mbps gives comfortable headroom for one 4K stream plus normal browsing. A household streaming on multiple devices simultaneously should aim for 100+ Mbps.

Wi-Fi shares bandwidth among all connected devices, loses throughput to interference from walls and other electronics, and uses half-duplex communication (it cannot send and receive simultaneously). A 300 Mbps Wi-Fi router might deliver 100–150 Mbps to a single device in practice, while Ethernet gives you the full rated speed.

Download Mbps measures data coming to you (streaming, browsing), while upload Mbps measures data you send (video calls, cloud backups). Most home connections are asymmetric — 100 Mbps down but only 10–20 Mbps up. Fiber-to-the-home plans increasingly offer symmetric speeds.

Surprisingly little — most online games use only 1–3 Mbps of bandwidth. What gamers actually need is low latency (ping), not high throughput. A 10 Mbps connection with 15ms ping will outperform a 500 Mbps connection with 100ms ping for gaming every time.

At gibibit speeds, 7.4% represents a substantial amount of data. The difference between 10 Gibps and 10 Gbps is 737 Mbps — enough bandwidth for several 4K video streams. When designing storage fabrics or HPC interconnects, misinterpreting the unit can lead to underprovisioned systems.

PCIe specifications are actually defined in GT/s (gigatransfers per second) with specific encoding overhead. PCIe 3.0 uses 128b/130b encoding at 8 GT/s, giving about 985 MB/s per lane — which is closer to binary GiB/s than decimal GB/s. The industry uses both units somewhat loosely.

InfiniBand specifications use decimal rates (HDR = 200 Gbps, NDR = 400 Gbps per port). However, some HPC benchmarks and documentation convert to binary units for consistency with memory bandwidth figures. Always check the document's unit convention to avoid the 7% discrepancy.

Ordering a 100 Gibps fabric when you needed 100 Gbps means overpaying for 7.4% more bandwidth than necessary. Conversely, provisioning 100 Gbps when your workload needs 100 Gibps leaves you 7.4% short, potentially causing congestion during peak loads. At data center scale, these margins translate to real money.

Unlikely. Networking is firmly decimal (Ethernet, fiber optics), while memory and storage have binary roots. The two worlds overlap in storage networking, causing permanent confusion. The best practice is to always explicitly state "decimal" or "binary" in specifications rather than hoping everyone agrees.