Gigabits per second to Megabits per second (Gbps to Mbps)
Last updated:
Gigabits-per-second to megabits-per-second conversions break down Gbps-scale aggregate bandwidth budgets into the Mbps-scale per-port, per-tenant, per-circuit, and per-stream allocations that operational systems actually deliver. Cloud network engineers slicing per-VM Mbps shares from Gbps-scale tenant uplinks, network analyser tools reporting per-flow Mbps against aggregate Gbps interface capacity, last-mile fibre engineers splitting Gbps-PON downstream into per-subscriber Mbps shares, and software-defined-WAN admins allocating per-application Mbps QoS budgets from Gbps-class WAN edges all run this conversion at every per-tenant or per-flow allocation step. The math is a clean three-decimal-place shift, with Gbps-to-Mbps scaling up by 1000 in decimal SI.
How to convert Gigabits per second to Megabits per second
Formula
Mbps = Gbps × 1000
To convert gigabits per second to megabits per second in decimal SI, multiply the Gbps figure by 1000 — equivalently, shift the decimal three places to the right. The relationship is exact in decimal SI and is universal across network-equipment specs, ISP product naming, and modern bandwidth dashboards. The mental math is trivial: 1 Gbps = 1000 Mbps, 10 Gbps = 10,000 Mbps, 100 Gbps = 100,000 Mbps. As with the inverse conversion, note the bits-vs-bytes distinction: Gbps and Mbps measure bits per second, while GB/s and MB/s measure bytes per second, and the two differ by a factor of 8. A 1 Gbps connection is 125 MB/s at theoretical maximum, not 1 GB/s.
Worked examples
Example 1 — 1 Gbps
One gigabit per second converts to 1 × 1000 = 1000 Mbps in decimal SI. That is the standard gigabit Ethernet capacity and the basis for the canonical Gbps-to-Mbps relationship used in network-equipment specs, ISP product naming, and most modern bandwidth dashboards. The 1 Gbps / 1000 Mbps figure is one of the most common bandwidth references in everyday IT work.
Example 2 — 10 Gbps
Ten gigabits per second converts to 10 × 1000 = 10,000 Mbps. That is a typical 10 Gbps enterprise WAN edge, a common 10 GbE data-centre server-NIC speed, or an XGS-PON downstream capacity shared across 32 subscribers. Per-flow, per-VM, and per-subscriber slicing of this 10,000 Mbps total drives the per-tenant or per-user service tier allocations.
Example 3 — 100 Gbps
One hundred gigabits per second converts to 100 × 1000 = 100,000 Mbps. That is a 100 GbE data-centre spine-switch port speed, a typical multi-tenant cloud-region uplink, or a small CDN-edge aggregate capacity. Per-flow Mbps detail at this scale typically surfaces in network analysis tools rather than in the network-design documents, which work at the 100 Gbps aggregate level.
Gbps to Mbps conversion table
| Gbps | Mbps |
|---|---|
| 1 Gbps | 1000 Mbps |
| 2 Gbps | 2000 Mbps |
| 3 Gbps | 3000 Mbps |
| 4 Gbps | 4000 Mbps |
| 5 Gbps | 5000 Mbps |
| 6 Gbps | 6000 Mbps |
| 7 Gbps | 7000 Mbps |
| 8 Gbps | 8000 Mbps |
| 9 Gbps | 9000 Mbps |
| 10 Gbps | 10000 Mbps |
| 15 Gbps | 15000 Mbps |
| 20 Gbps | 20000 Mbps |
| 25 Gbps | 25000 Mbps |
| 30 Gbps | 30000 Mbps |
| 40 Gbps | 40000 Mbps |
| 50 Gbps | 50000 Mbps |
| 75 Gbps | 75000 Mbps |
| 100 Gbps | 100000 Mbps |
| 150 Gbps | 150000 Mbps |
| 200 Gbps | 200000 Mbps |
| 250 Gbps | 250000 Mbps |
| 500 Gbps | 500000 Mbps |
| 750 Gbps | 750000 Mbps |
| 1000 Gbps | 1000000 Mbps |
| 2500 Gbps | 2500000 Mbps |
| 5000 Gbps | 5000000 Mbps |
Common Gbps to Mbps conversions
- 0.1 Gbps=100 Mbps
- 0.5 Gbps=500 Mbps
- 1 Gbps=1000 Mbps
- 2.5 Gbps=2500 Mbps
- 5 Gbps=5000 Mbps
- 10 Gbps=10000 Mbps
- 25 Gbps=25000 Mbps
- 40 Gbps=40000 Mbps
- 100 Gbps=100000 Mbps
- 400 Gbps=400000 Mbps
What is a Gigabit per second?
One gigabit per second (Gbps) equals 1,000,000,000 bits transmitted per second under the SI decimal convention used universally by IEEE, ITU-T, 3GPP, and OIF standards. The Gbps-to-GB/s conversion is exact: 1 Gbps ÷ 8 bits/byte = 0.125 GB/s = 125 MB/s of theoretical maximum file-transfer throughput, with TCP/IP, Ethernet, and link-layer overhead reducing practical effective throughput by 5–15% to roughly 110–120 MB/s under favourable conditions. The symbol Gbps (uppercase G, lowercase b, lowercase ps) is distinct from GB/s (uppercase G, uppercase B, slash s) by the same factor of 8 that separates bits from bytes at every prefix tier. Gbps is the standard unit for Ethernet-and-Fibre-Channel switching-fabric capacity (IEEE 802.3 family), for PCIe-link bandwidth in modern host bus adapters and NICs, for cellular peak-data-rate quotes (3GPP Release 16 5G mmWave at 20 Gbps theoretical peak), and for the per-wavelength capacity of coherent DWDM optical transponders. At the multi-Tbps scale of modern undersea-cable systems, Gbps is the unit of single-wavelength capacity from which aggregate per-pair and per-cable Tbps figures are summed.
Gigabits per second became the working unit of enterprise and data-centre networking with the IEEE 802.3z Gigabit Ethernet standard ratified in June 1998 — a 1 Gbps full-duplex link over fibre or copper that displaced 100BASE-TX (Fast Ethernet) as the LAN-server-uplink baseline through the early 2000s and as the desktop wired-Ethernet baseline by 2010. The 10 Gigabit Ethernet standard (IEEE 802.3ae) followed in June 2002, then 40 GbE and 100 GbE (IEEE 802.3ba, 2010), 25 GbE (IEEE 802.3by, 2016), 200 GbE and 400 GbE (IEEE 802.3bs, 2017), and 800 GbE (IEEE 802.3df, 2024) — the rate ladder that hyperscaler data-centre fabrics from AWS, Azure, Google Cloud, and Meta have followed for the leaf-and-spine switching topologies underneath every cloud workload. The cultural inflection that pushed gigabit out of enterprise specification sheets and into consumer expectation came on 26 July 2012, when Google Fiber went live in Kansas City, Kansas with a 1 Gbps symmetric residential plan at $70/month — at a time when the median US residential broadband connection was 6 Mbps and incumbent ISPs offered "extreme" tiers at 50–100 Mbps. Google Fiber expanded to a handful of additional metros (Austin, Provo, Atlanta, Charlotte, Nashville) before construction was paused in 2016, but the competitive pressure forced AT&T, Comcast, Verizon Fios, and Cox to roll out their own gigabit residential tiers across most major US markets between 2014 and 2020, and 1 Gbps residential FTTH had become the default new-build target by 2024 with 2/5/10 Gbps consumer tiers now available from AT&T Fiber, Frontier, Ziply, and Sonic. The defining gigabit-per-second platform of the 2020s is the long-haul DWDM fibre-optic network. Coherent 400 Gbps and 800 Gbps single-wavelength transponders introduced by Ciena, Infinera, and Nokia between 2020 and 2024 multiplexed 80–96 wavelengths per fibre pair to deliver 32–76.8 Tbps per pair, the capacity that anchors the modern global undersea-cable buildout. The MAREA Microsoft–Facebook–Telxius transatlantic cable went live in 2018 at 160 Tbps and was upgraded to 224 Tbps in 2022; the Google-funded Equiano cable from Portugal to South Africa launched in 2022 at 144 Tbps; the Meta-funded 2Africa cable, the longest in the world at 45,000 km, completed its first segment in 2023 at 180 Tbps. 5G NR theoretical peaks under the 3GPP Release 16 specification reach 20 Gbps in mmWave deployments under ideal conditions, with Release 18 (5G-Advanced, 2024) raising the peak to 50 Gbps.
Data-centre fabric switching is the gigabit-per-second unit's most active 2026 domain. Hyperscaler leaf-and-spine fabrics at AWS, Azure, Google Cloud, and Meta are now built around 400 Gbps and 800 Gbps switch-to-switch trunks, with 200 Gbps and 100 Gbps to-server downlinks on top-of-rack switches. Arista, Cisco Nexus, NVIDIA Spectrum and Juniper QFX product lines all spec their port densities and aggregate switching capacity in Gbps and Tbps; a typical 51.2 Tbps switch ASIC (Broadcom Tomahawk 5, NVIDIA Spectrum-4) drives 64× 800 Gbps ports or 128× 400 Gbps ports at line rate. Cloud-customer-facing virtual-NIC bandwidth tiers, AWS placement-group inter-AZ throughput limits, and Azure ExpressRoute / Google Cloud Interconnect dedicated-circuit options all denominate in Gbps tiers (1, 10, 40, 100 Gbps). GPU-accelerator interconnects sit at the high end of the Gbps tier. NVIDIA NVLink generation 4 delivers 900 GB/s aggregate per H100 GPU across 18× 50 Gbps lanes (450 Gbps unidirectional or 900 GB/s bidirectional in NVLink-language); the InfiniBand NDR (400 Gbps) and XDR (800 Gbps) standards from the InfiniBand Trade Association anchor AI-training-cluster east-west traffic; the AMD Infinity Fabric on MI300X-class accelerators sustains 5.3 TB/s of HBM3 bandwidth per package. The 2024–2026 AI-training data-centre buildout has driven Gbps-tier per-port pricing down by an order of magnitude relative to general-purpose-cloud networking. Long-haul fibre-optic backbones, undersea cables, and metro-DWDM systems are denominated in per-wavelength Gbps and per-cable Tbps. Coherent 400 Gbps and 800 Gbps single-wavelength DWDM transponders from Ciena, Infinera, Nokia, and Cisco-acquired Acacia Communications now dominate new long-haul deployments; legacy 100 Gbps wavelengths from the 2010s remain in service across regional and metro networks. Telecommunications carriers (Lumen, Zayo, GTT, Telia Carrier, Tata Communications) sell wavelength-services in 100, 400, and 800 Gbps tiers, IP-transit in 10 and 100 Gbps port-rate tiers, and Ethernet Private Line services across the same tier ladder. Cellular peak-data-rate marketing has crossed into Gbps territory under 5G NR. T-Mobile, Verizon, and AT&T all publish "5G Ultra Wideband" or "5G+" mmWave-deployment Gbps peaks in dense-urban hot spots, with verified consumer-device achievements in the 1–4 Gbps range under line-of-sight conditions. The 3GPP Release 16 specification fixes the 5G NR theoretical peak at 20 Gbps download / 10 Gbps upload; Release 18 ("5G-Advanced", finalised June 2024) raises the peak to 50 Gbps with new spectrum bands and 8×8 MIMO configurations. Storage and peripheral interface standards have converged on the Gbps tier alongside networking. USB4 (announced August 2019, USB-IF) runs at 20 Gbps or 40 Gbps full-duplex per port over USB-C connectors and is the basis for Thunderbolt 4, which the Intel-led Thunderbolt programme standardised at 40 Gbps with mandatory PCIe-tunnelling and DisplayPort-tunnelling capabilities; Thunderbolt 5, announced September 2023 and shipping on Apple M4 Pro and M4 Max devices in 2024, runs at 80 Gbps symmetric and 120 Gbps asymmetric ("Bandwidth Boost" mode) for high-resolution external-display workloads. NVMe SSD interfaces have followed PCIe generation: a PCIe 4.0 ×4 NVMe drive runs at 64 Gbps raw signalling (~7 GB/s practical sequential reads); a PCIe 5.0 ×4 NVMe drive runs at 128 Gbps raw (~14 GB/s); a PCIe 6.0 ×4 NVMe drive at 256 Gbps raw. The convergence has eliminated the historical separation between "networking-fast" and "storage-fast" — both categories now sit in the 40–800 Gbps band and are bottlenecked by the same physical-layer signalling generations (NRZ vs PAM4, retimer-and-redriver count, copper-vs-fibre PHY). Consumer-grade Wi-Fi marketing has crossed the Gbps boundary on every premium router. Wi-Fi 6 (802.11ax) AX6000 and AX11000 routers advertise 6 Gbps and 11 Gbps aggregate radio capacities; Wi-Fi 7 (802.11be) BE19000 and BE33000 routers advertise 19 Gbps and 33 Gbps aggregate; the per-device sustained throughput at the client end is one band at a time and tops out at 2–3 Gbps even on the highest-tier 320 MHz Wi-Fi 7 channels — the same aggregate-vs-sustained gap that mbps-tier routers show, scaled up.
What is a Megabit per second?
One megabit per second (Mbps) equals 1,000,000 bits transmitted per second under the SI decimal convention used universally by network engineers, ISPs, and standards bodies — not the binary 2²⁰ that the storage-prefix convention implies for bytes. The IEC and IEEE both treat "Mbps" as 10⁶ bps in IEEE 802.3 (Ethernet), 802.11 (Wi-Fi), 3GPP cellular standards, ITU-T G.9961 powerline, DOCSIS cable, and the relevant ITU-R radio-spectrum recommendations. The Mbps-to-MB/s conversion is exact: 1 Mbps ÷ 8 bits/byte = 0.125 MB/s, so a 100 Mbps connection delivers a maximum of 12.5 MB/s before TCP/IP, Ethernet, and link-layer protocol overhead reduces effective throughput by 5–15% to roughly 11.0–11.9 MB/s. The symbol distinguishes case carefully: Mbps (uppercase M, lowercase b, lowercase ps) is megabits per second; MB/s (uppercase M, uppercase B, slash s) is megabytes per second; the 8:1 ratio between the two is identical to the bit/byte distinction, and is the most consequential unit-conversion in consumer technology.
Megabits per second became the consumer-facing unit of internet speed in the late 1990s and has remained the dominant marketing-and-regulatory unit through every successive broadband generation. Cable modem rollouts under the DOCSIS 1.0 specification published by CableLabs in March 1997 advertised peak shared-segment capacity of 38 Mbps downstream, with per-subscriber tiers initially marketed at 1.5 Mbps and 3 Mbps; ADSL deployments by US RBOCs and European incumbents through the same period advertised 1.5–8 Mbps downstream. The unit was inherited from earlier wide-area networking — the T1 carrier specification standardised by AT&T in the 1960s ran at 1.544 Mbps, and the European E1 carrier at 2.048 Mbps — and from the IEEE 802.3 Ethernet original 10 Mbps shared-coaxial specification of 1983. The Wi-Fi family carried the convention forward: 802.11b (1999) at 11 Mbps, 802.11g (2003) at 54 Mbps, 802.11n (2009) at 150–600 Mbps, 802.11ac (2013) at 433–6,933 Mbps, 802.11ax / Wi-Fi 6 (2019) at up to 9.6 Gbps aggregate, 802.11be / Wi-Fi 7 (2024) at 46 Gbps theoretical peak. Cellular followed the same path: 3G HSPA at 14–42 Mbps, 4G LTE Cat 4 at 150 Mbps and Cat 16 at 1 Gbps, 5G NR sub-6 GHz at hundreds of Mbps, 5G mmWave at theoretical multi-Gbps peaks. Regulatory definitions of "broadband" have tracked the consumer-marketing tier with a lag — the FCC defined broadband as 4/1 Mbps in 2010, raised it to 25/3 Mbps in 2015, and to 100/20 Mbps in March 2024, the threshold below which a connection is no longer counted toward the National Broadband Map's "served" status.
Residential broadband plans denominate every advertised tier in Mbps or Gbps. Comcast Xfinity 2026 retail tiers run from 75 Mbps Connect through 1,200 Mbps Gigabit and 2,000 Mbps Gigabit X2; Spectrum runs 300/500/1,000 Mbps tiers; Verizon Fios runs 300/500/1,000/2,000 Mbps fibre-to-the-home tiers; AT&T Fiber runs 300/500/1,000/2,000/5,000 Mbps tiers. The marketed downstream rate is what every ISP's sales material leads with, the regulatory upload-rate disclosure (under the FCC Broadband Nutrition Label rules effective April 2024) is the second-line figure, and the typical-during-peak-hours figure is the third-line disclosure that the FCC requires in 8-point or larger type. Comparison shopping at the household level — Cox versus Spectrum versus T-Mobile Home Internet — is conducted entirely in Mbps until the gigabit-tier transition. Streaming-service minimum-bandwidth requirements published by Netflix, YouTube, Disney+, Apple TV+, Hulu, and Max all denominate in Mbps. Netflix recommends 3 Mbps for SD, 5 Mbps for 1080p HD, 15 Mbps for 4K UHD; YouTube recommends 3 Mbps for 1080p, 20 Mbps for 4K HDR; Apple TV+ 4K Dolby Vision streams at sustained ~25 Mbps peaks. The "minimum required Mbps" figure published in every help-centre article is the speed-test threshold consumers run against to diagnose buffering — the typical Speedtest.net or Fast.com result expressed in Mbps download / Mbps upload — and the household-Wi-Fi troubleshooting workflow (router placement, channel selection, mesh-node sizing) is conducted entirely in Mbps observed at the device. Wi-Fi router and mesh-system marketing collapses all per-band capacities into a single aggregate-Mbps figure (AX5400, AX6000, BE9300, BE19000) that nominally sums the 2.4 GHz, 5 GHz, and 6 GHz radio capacities — a marketing-aggregate that no single device ever achieves because connections use one band at a time. The actual per-device sustained Mbps is determined by client radio capability (Wi-Fi 5 vs 6 vs 6E vs 7), spatial stream count, channel-bandwidth selection (20/40/80/160/320 MHz), and signal-strength-dependent modulation/coding rate. The gap between the printed-on-the-box AX5400 and the device-facing 600 Mbps is roughly 9× and is one of the larger consumer-marketing inflation factors in any product category. Cellular speed-tier marketing follows the same Mbps convention. T-Mobile, Verizon, and AT&T all publish "typical 5G download" Mbps ranges by market, and the FCC's Mobile Broadband Performance Report quarterly publishes nationwide Mbps medians. 5G NR sub-6 GHz typical user-plane throughput in 2026 is 150–500 Mbps in dense-urban deployments and 50–150 Mbps in rural; 5G mmWave urban hot-spot delivery exceeds 1,000 Mbps; LTE-Advanced legacy delivery sits at 25–100 Mbps where re-farmed for 5G overlap.
Real-world uses for Gigabits per second to Megabits per second
Cloud network engineers slicing per-VM Mbps from Gbps tenant uplinks
Cloud network teams (AWS VPC, Azure VNet, GCP VPC) provision per-tenant uplinks at Gbps scale (1 Gbps, 10 Gbps, 25 Gbps) and slice into per-VM Mbps allocations against per-instance NIC limits. A 10 Gbps tenant uplink converts to 10,000 Mbps of aggregate slicable bandwidth, which a 100-VM tenant divides into nominal 100 Mbps per-VM shares before applying QoS, micro-burst absorption, and per-flow rate-limit policies. Per-VM Mbps allocations track in cloud monitoring; per-tenant Gbps totals appear in cloud billing.
Network analyser tools per-flow Mbps reporting against Gbps interface
Network analysis platforms (SolarWinds NPM, Wireshark, ntopng, Kentik) report per-flow throughput in Mbps for individual TCP/UDP sessions while aggregating against Gbps-scale interface capacity. A 10 Gbps WAN interface with 800 active flows averaging 12 Mbps per flow shows 9600 Mbps of aggregate throughput at 96% utilisation. The per-flow Mbps detail drives troubleshooting and per-application capacity planning; the Gbps interface aggregate drives circuit-upgrade decisions.
Last-mile fibre engineers splitting Gbps PON into per-subscriber Mbps
Passive optical network (PON) engineers running GPON, XGS-PON, or NG-PON2 fibre access split Gbps-class downstream capacity (2.5 Gbps for GPON, 10 Gbps for XGS-PON) across 32 or 64 subscribers per OLT port, with per-subscriber Mbps service tiers (100 Mbps, 500 Mbps, 1000 Mbps) sliced from the shared bandwidth. A 10 Gbps XGS-PON downstream converts to 10,000 Mbps of shared capacity across 32 subscribers, supporting 32 × 300 Mbps service tiers (9600 Mbps total) at 96% subscription before contention shows on peak-hour speed tests.
SD-WAN admins allocating per-application Mbps QoS from Gbps WAN edge
Software-defined WAN administrators (Cisco Meraki, Fortinet Secure SD-WAN, Palo Alto Prisma) allocate per-application QoS bandwidth in Mbps against Gbps-class WAN edge capacity. A 1 Gbps WAN edge converts to 1000 Mbps of allocable bandwidth, which the admin partitions: 200 Mbps guaranteed for voice/video, 400 Mbps for SaaS, 300 Mbps for general internet, and 100 Mbps reserved for management traffic. Per-application Mbps allocations show on the QoS dashboard; per-edge Gbps capacity shows on the capacity-planning report.
When to use Megabits per second instead of Gigabits per second
Use megabits per second when the allocation precision is at the per-port, per-tenant, per-VM, per-subscriber, or per-application level — anywhere a Gbps budget needs to be partitioned into operational service tiers. Stay in gigabits per second when the figure is naturally Gbps-scale — aggregate WAN edges, data-centre interface speeds, cloud-region uplinks, CDN-edge capacities, and contract-tier negotiations. The boundary is at the slicing or allocation transaction where a Gbps-class budget has to be partitioned into Mbps-scale operational shares. Both layers are kept: Gbps in the capacity-planning view, Mbps in the per-flow operational view, with reconciliation happening at every QoS-policy review, subscription-ratio recalibration, and capacity-upgrade cycle.
Common mistakes converting Gbps to Mbps
- Treating a 1 Gbps interface as capable of delivering 1 Gbps of usable application throughput. Real-world throughput on a 1 Gbps link is typically 940–960 Mbps after Ethernet, IP, and TCP overhead, with the 4–6% gap representing protocol headers and inter-frame gap. Capacity calculations against the gross 1000 Mbps figure overestimate available bandwidth by a small but meaningful margin.
- Allocating 100% of Gbps-class capacity to per-tenant Mbps shares without contention reserves. PON last-mile networks routinely sell more aggregate per-subscriber capacity than their shared Gbps backhaul can deliver simultaneously, relying on subscription-ratio (typical 4:1 to 10:1) and time-of-day usage patterns to keep peak-hour saturation acceptable. Allocating without subscription-ratio thinking leads to peak-hour congestion complaints.
Frequently asked questions
How many Mbps in 1 Gbps?
One gigabit per second equals 1000 megabits per second in decimal SI. The relationship is exact and is the basis for the "gigabit Ethernet" naming convention used in network-equipment specs since the late 1990s. The conversion is universal across modern bandwidth dashboards, ISP product naming, and capacity-planning tools.
How many Mbps in 10 Gbps?
Ten gigabits per second equals 10,000 Mbps in decimal SI. That is a typical 10 GbE enterprise server-NIC speed, a common 10 Gbps WAN edge, or an XGS-PON downstream capacity shared across 32 subscribers. The 10,000 Mbps figure is the basis for per-flow, per-VM, and per-subscriber slicing on dashboards.
Is 1 Gbps the same as 1000 MB/s?
No — 1 Gbps (gigabits per second) is 125 MB/s (megabytes per second), not 1000 MB/s. The two differ by a factor of 8 because there are 8 bits per byte. After protocol overhead, real-world byte throughput on a 1 Gbps link is typically 110–120 MB/s, and the "MB/s vs Mbps" distinction is one of the most common bandwidth-arithmetic confusions.
How many Mbps in 100 Gbps?
One hundred gigabits per second equals 100,000 Mbps in decimal SI. That is a 100 GbE data-centre spine port speed, a typical multi-tenant cloud-region uplink, or a small CDN-edge aggregate capacity. Per-flow Mbps detail at this scale typically only surfaces in network analysis tools rather than design documents, which work at the 100 Gbps aggregate.
How do I convert Gbps to Mbps in my head?
Multiply by 1000 in decimal SI — a three-decimal-place shift. For 1 Gbps that gives 1000 Mbps; for 10 Gbps it gives 10,000 Mbps; for 25 Gbps it gives 25,000 Mbps. The mental math is trivial and is the basis for everyday bandwidth-allocation reporting.
Why do PON networks oversubscribe Gbps backhaul to Mbps subscribers?
Last-mile PON networks rely on the time-of-day usage pattern of residential subscribers to deliver advertised per-subscriber Mbps speeds without provisioning the full simultaneous capacity. A 10 Gbps XGS-PON serving 32 subscribers at 1000 Mbps each would need 32 Gbps of dedicated capacity for full simultaneous speed, but typical peak-hour aggregate usage stays below 6 Gbps because subscribers are not all at peak simultaneously. The subscription ratio (typical 4:1 to 10:1) makes the economics work.
How precise should Gbps-to-Mbps be for QoS allocation?
Mbps precision is sufficient for QoS allocation because QoS classes typically work at 50–100 Mbps granularity for individual application categories. A 1 Gbps WAN edge allocates as 200 Mbps voice + 400 Mbps SaaS + 300 Mbps general internet + 100 Mbps management, with the per-class Mbps figures reading directly on the SD-WAN policy console. Sub-Mbps precision rarely matters except in specialised low-latency applications.