A single GPON PON port delivers 2.5 Gbps downstream but only 1.25 Gbps upstream, and that upstream pipe is time-shared by every ONU hanging under one fiber splitter. How much each household gets depends on the split ratio and how many subscribers are online at the same time — not on the downstream number printed on the spec sheet. Plan a gpon network by the upstream budget and you avoid the most common "why is it slow" complaints.
GPON upstream is 1.25 Gbps shared across all ONUs on the PON port; downstream is 2.5 Gbps and schedules more comfortably.
Per-user upstream ≈ total upstream ÷ (online users × concurrency ratio) — bigger split ratio and higher concurrency mean thinner speed.
When upstream is the bottleneck, lower the split ratio or move to XGSPON (10 Gbps upstream) instead of chasing downstream.
Downstream the OLT broadcasts to every home, so scheduling stays roomy. Upstream is dozens of households fighting for the same 1.25 Gbps channel, each grabbing timeslots when they have data to send. That is why upstream becomes the bottleneck first — camera backhaul, video calls, and large uploads all push against it. In any gpon network this upstream pipe is the shared resource every household contends for.
Note: GPON is an asymmetric design by default: 2.5 Gbps down, 1.25 Gbps up. A slow upstream is normal, not a fault — but it should be budgeted, not ignored.
A rough per-user upstream estimate is: total upstream ÷ (online households × concurrency ratio). The fiber splitter is what divides that 1.25 Gbps upstream among all those homes, so its insertion loss belongs in the same budget math. At 1:64 with 64 homes and 0.3 concurrency, about 19 homes compete, so each gets roughly 1.25 G ÷ 19 ≈ 65 Mbps. Push concurrency to 0.8 and each home drops to about 24 Mbps. Downstream at 2.5 Gbps follows the same math but feels far better because it schedules with more headroom.
| Split ratio | Homes | Concurrency | Per-user upstream (est.) | Per-user downstream (est.) |
|---|---|---|---|---|
| 1:32 | 32 | 0.3 | ~130 Mbps | ~260 Mbps |
| 1:64 | 64 | 0.3 | ~65 Mbps | ~130 Mbps |
| 1:64 | 64 | 0.8 | ~24 Mbps | ~49 Mbps |
| 1:128 | 128 | 0.3 | ~33 Mbps | ~65 Mbps |
High-density communities and camera-heavy installs feel the pinch first. If uploads or video calls stall while downloads look fine, check the split ratio and live concurrency before anything else.
Tip: For uplink-heavy loads, either reduce the split ratio or deploy XGSPON, which raises upstream to 10 Gbps and removes the shared-pipe squeeze.
Is 1.25 Gbps upstream enough? For light browsing, yes. For dense, upload-heavy use — camera backhaul, video conferencing — it gets tight. In those cases lower the split ratio or step up to XGSPON.
Can I run a 1:128 split? Optically it is possible if power budget allows, but 128 homes share 1.25 Gbps upstream, so per-user speed is thin. Confirm upstream is not your bottleneck before committing to 1:128 in a dense community.
Is fast down / slow up normal? Yes. GPON is intentionally asymmetric at 2.5 Gbps down and 1.25 Gbps up. If upstream feels stuck, first check concurrency and split ratio rather than the downstream figure.
GPON upstream is time-shared across the whole PON port, so real per-user speed follows the split ratio and concurrency. In dense communities, budget the upstream first — then set the split ratio with the upload path in mind.
Customer Manager at Shenzhen Rayin Technology Co., Ltd.
