Hi Netgear team, I’ve recently purchased the Orbi 870 system, primarily due to its advertised support for 10Gbps WAN connections. I’m currently on a 10Gbps fibre plan and have the Orbi connected directly to the ONT using a certified Cat7 cable. The port negotiates at 10Gbps full duplex, and all hardware in the chain supports 10Gbps. However, I’ve noticed that the internal speed test built into the Orbi consistently caps out at around 4.5Gbps, regardless of time of day or test server. I understand that the Orbi 870 only has 2.5Gbps LAN ports and that wireless speeds have their own limitations that’s expected. But since the test is run directly from the router, I had assumed it would be able to at least demonstrate close to full WAN throughput (e.g. 8–9Gbps), especially on such a fast connection. My setup: Orbi 870 Router (latest firmware)10Gbps fibre connectionCat7 cable from ONT to Orbi 870’s 10GbE WAN portWAN port confirmed as 10Gbps full duplexInternal speed test peaking at ~4.5Gbps consistentlyFirewalla Pro removed from inline during testing ISP speed tests from ONT are at advertised speed. My questions: Is the Orbi 870 hardware limited in terms of how much WAN throughput it can process internally?Is there a CPU bottleneck or lack of hardware acceleration that prevents the internal speed test from reaching full 10Gbps?Should users expect that the 10Gbps port is more of a marketing spec than an actual performance threshold? Would appreciate any clarification from the Netgear team or other users who’ve tested this in a similar setup

DTN01 Unfortunately, when running the speedtest from the router itself does not tell you what Speedtest server it selected - easily. So you really don't know if you are using the same exact server when running the Ookla speedtest natively. BUT, you can identify the server selected with a bit of work. Start a debug session from the router in a browser. (<router ip address>/debug.htm) then once the debug page comes us, click on the "Start Capture" button. Once the capture starts (the page will refresh with the "Start Capture" greyed out - go back to the router admin screen (<router ip address>/start.htm, click on "Advanced" tab, "Setup", and then "Speedtest". Click on "Test Speed" and let the speedtest run. Once the speedtest completes, go back to the debug page (<router ip address>/debug.htm and click on "Save Debug File" and let it write the debug log. It should save it where your default browser downloads go. Once it has saved it, you can close out the debug session. Open up the debug_log.zip file (by double clicking on it) (this is based on a windows setup, use whatever you have if not windows based) - and you should see a test file called speedtest_result.txt. You can save that off, or just open it up in a text file viewer and it will tell you what speedtest servers it considered using, which on it selected, and also show you the various test results (ping times, upload speeds, download speeds) as it ran through the speedtest data streams. You can at least find out what server it selected to see if you are testing against the same one as the standalone OOKLA tests, and also be able to see if you had some drops of speed during the tests which at least gives NG something to look at (like maybe the router can not handle 10G steady streams). (ETA) - I sure which NG added server information to the Speedtest Results page like they provide with some other NG products. It's something that has been asked for for several years now. The data is present/available - NG just needs to add it to the page.

Alas, the Netgear Team does not participate in the Community Forum. With this being a recent purchase, it might be useful to take advantage of the 90 days of 'complimentary support' that Netgear provides with new purchases and raise the question with Netgear support: https://my.netgear.com/support/contact.aspx Random thoughts.... and a question. Even though Ethernet connections autonegotiate a "speed", it is physically impossible to transmit data over the link at that speed.https://en.wikipedia.org/wiki/AutonegotiationThere is "overhead" in Ethernet transmission, including spaces between packets, so it is possible to get close to the rated speed, but not actually reach that speed.(I regularly measure about 950Mbps on a gigabit Ethernet link.)Thus, no. The Orbi 850 will never actually transmit/receive data at 10Gbps. The Ookla Speed Test software that Netgear bundles into the router firmware claims to be capable of measuring 10Gbps(subject to the overhead limitation mentioned above)https://www.ookla.com/articles/10-gbps-speedtestHowever, that implies that the entire pathway across the internet between the ISP connection and the Ookla server farm is capable of 10Gbps.One of the annoying features of Netgear's Ookla Speed Test is that it does not reveal exactly which Ookla server was used for any specific test.(whereas the Ookla 'app' for most platforms clearly states which server is being used.) DTN01 wrote: ISP speed tests from ONT are at advertised speed. What equipment is used to verify this? (A computer with a 10G Ethernet adapter? There are a number of 10G Ethernet adapters on the market, and it would be interesting to know which was used for this experiment.) How cool to have a computer that can actually process a full 10G Ethernet stream!

appreciate you taking the time to share this. I totally get the point around Ethernet overhead and that we’ll never see a “true” 10.00Gbps line rate. That’s expected. I’m not chasing perfection here just trying to figure out why my Orbi 870 is consistently capped around 4.5Gbps on the built-in speed test, even under what I’d consider ideal conditions. Ive run multiple speed tests directly from the ONT & Firewalla, bypassing the router, and those easily hit 9+Gbps so I know the connection is solid. But when I use the Orbi’s internal speed test, I never see more than ~4.5Gbps, even at off-peak hours. This has been sustained for a week. I’ve reached out to Netgear Support though it’s through a third-party distributor in my country, so I’m still waiting on a response. Thought I’d also ask here in case anyone else has run into the same thing. The bigger question I’m trying to answer is this: Is the Orbi 870 hardware-limited in such a way that it simply can’t push more than ~4.5–5Gbps on the WAN side, even under perfect conditions? If there’s a technical reason why that’s not possible with this model, I think a lot of us would benefit from knowing that up front. It’s not a complaint just looking for clarity so I know whether to hang onto the system or go a different route.

Also to add. I am using an Ubiquiti 10G Ethernet Adapter to my MacBook Pro.

What are the speeds seen on the Mac using Ooklas Installable speed test app on the Mac? What brand and model# is the ONT? Is the CAT7 cable UTP or STP? Possible the test service being picked by Orbi may not be supporting of 10Gb or service is busy.

Orbi 870 WAN performance | NETGEAR Communities

11 Replies

CrimpOn
Guru - Experienced User
Aug 19, 2025
Alas, the Netgear Team does not participate in the Community Forum. With this being a recent purchase, it might be useful to take advantage of the 90 days of 'complimentary support' that Netgear provides with new purchases and raise the question with Netgear support: https://my.netgear.com/support/contact.aspx

Random thoughts.... and a question.

Even though Ethernet connections autonegotiate a "speed", it is physically impossible to transmit data over the link at that speed.
https://en.wikipedia.org/wiki/Autonegotiation
There is "overhead" in Ethernet transmission, including spaces between packets, so it is possible to get close to the rated speed, but not actually reach that speed.
(I regularly measure about 950Mbps on a gigabit Ethernet link.)
Thus, no. The Orbi 850 will never actually transmit/receive data at 10Gbps.

The Ookla Speed Test software that Netgear bundles into the router firmware claims to be capable of measuring 10Gbps
(subject to the overhead limitation mentioned above)
https://www.ookla.com/articles/10-gbps-speedtest
However, that implies that the entire pathway across the internet between the ISP connection and the Ookla server farm is capable of 10Gbps.
One of the annoying features of Netgear's Ookla Speed Test is that it does not reveal exactly which Ookla server was used for any specific test.
(whereas the Ookla 'app' for most platforms clearly states which server is being used.)

DTN01 wrote:
ISP speed tests from ONT are at advertised speed.

What equipment is used to verify this? (A computer with a 10G Ethernet adapter? There are a number of 10G Ethernet adapters on the market, and it would be interesting to know which was used for this experiment.) How cool to have a computer that can actually process a full 10G Ethernet stream!
DTN01
Aspirant
Aug 19, 2025
appreciate you taking the time to share this.

I totally get the point around Ethernet overhead and that we’ll never see a “true” 10.00Gbps line rate. That’s expected. I’m not chasing perfection here just trying to figure out why my Orbi 870 is consistently capped around 4.5Gbps on the built-in speed test, even under what I’d consider ideal conditions.

Ive run multiple speed tests directly from the ONT & Firewalla, bypassing the router, and those easily hit 9+Gbps so I know the connection is solid.

But when I use the Orbi’s internal speed test, I never see more than ~4.5Gbps, even at off-peak hours. This has been sustained for a week.

I’ve reached out to Netgear Support though it’s through a third-party distributor in my country, so I’m still waiting on a response. Thought I’d also ask here in case anyone else has run into the same thing.

The bigger question I’m trying to answer is this:

Is the Orbi 870 hardware-limited in such a way that it simply can’t push more than ~4.5–5Gbps on the WAN side, even under perfect conditions?

If there’s a technical reason why that’s not possible with this model, I think a lot of us would benefit from knowing that up front. It’s not a complaint just looking for clarity so I know whether to hang onto the system or go a different route.
DTN01
Aspirant
Aug 19, 2025
Also to add. I am using an Ubiquiti 10G Ethernet Adapter to my MacBook Pro.
FURRYe38
Guru - Experienced User
Aug 19, 2025
What are the speeds seen on the Mac using Ooklas Installable speed test app on the Mac?

What brand and model# is the ONT?

Is the CAT7 cable UTP or STP?

Possible the test service being picked by Orbi may not be supporting of 10Gb or service is busy.
- DTN01
  Aspirant
  Aug 19, 2025
  Hitting almost constant 9.1Gb via the Nokia ONT.
  - FURRYe38
    Guru - Experienced User
    Aug 19, 2025
    What model# is the ONT?
    
    Is the CAT7 cable UTP or STP?
    
    When testing direct to the ONT, which test server are you picking?
TC_in_Montana
Virtuoso
Aug 19, 2025
DTN01

Unfortunately, when running the speedtest from the router itself does not tell you what Speedtest server it selected - easily. So you really don't know if you are using the same exact server when running the Ookla speedtest natively. BUT, you can identify the server selected with a bit of work.

Start a debug session from the router in a browser. (<router ip address>/debug.htm) then once the debug page comes us, click on the "Start Capture" button.

Once the capture starts (the page will refresh with the "Start Capture" greyed out - go back to the router admin screen (<router ip address>/start.htm, click on "Advanced" tab, "Setup", and then "Speedtest". Click on "Test Speed" and let the speedtest run. Once the speedtest completes, go back to the debug page (<router ip address>/debug.htm and click on "Save Debug File" and let it write the debug log. It should save it where your default browser downloads go.

Once it has saved it, you can close out the debug session.

Open up the debug_log.zip file (by double clicking on it) (this is based on a windows setup, use whatever you have if not windows based) - and you should see a test file called speedtest_result.txt.

You can save that off, or just open it up in a text file viewer and it will tell you what speedtest servers it considered using, which on it selected, and also show you the various test results (ping times, upload speeds, download speeds) as it ran through the speedtest data streams.

You can at least find out what server it selected to see if you are testing against the same one as the standalone OOKLA tests, and also be able to see if you had some drops of speed during the tests which at least gives NG something to look at (like maybe the router can not handle 10G steady streams).

(ETA) - I sure which NG added server information to the Speedtest Results page like they provide with some other NG products. It's something that has been asked for for several years now. The data is present/available - NG just needs to add it to the page.
CrimpOn
Guru - Experienced User
Aug 19, 2025
Thanks for this information. On my RBR50 system, the results are in the folder "tmp" in a file "ookla_speedtest_result" (not ".txt", but clearly a text file)

serverid: 14236 isp: Spectrum latency: 12 jitter: 0.26 upload: 12239 download: 476591 packet loss: 0.32%

Server 14236 is hosted by Frontier in Los Angeles, CA.

Perhaps the 870 router records more information. i.e.

TC_in_Montana wrote:
also be able to see if you had some drops of speed during the tests
- TC_in_Montana
  Virtuoso
  Aug 20, 2025
  CrimpOn
  
  The format/location/data is a bit improved in the later series (later than RBR50).
  
  Here's a cut/paste from mine...
  
  [2025-08-19 19:35:04.940] [info] Ping 1: 42.09 ms (42.09ms min, 0.00ms jitter)
  [2025-08-19 19:35:04.988] [info] Ping 2: 47.10 ms (42.09ms min, 5.01ms jitter)
  [2025-08-19 19:35:05.024] [info] Ping 1: 55.08 ms (55.08ms min, 0.00ms jitter)
  [2025-08-19 19:35:05.032] [info] Ping 3: 44.54 ms (42.09ms min, 3.79ms jitter)
  [2025-08-19 19:35:05.032] [info] Final Ping: 42.09 ms
  [2025-08-19 19:35:05.033] [info] Stage 1 completed
  [2025-08-19 19:35:05.045] [info] Ping 1: 66.18 ms (66.18ms min, 0.00ms jitter)
  [2025-08-19 19:35:05.076] [info] Ping 2: 52.70 ms (52.70ms min, 2.39ms jitter)
  [2025-08-19 19:35:05.079] [info] Ping 1: 58.99 ms (58.99ms min, 0.00ms jitter)
  [2025-08-19 19:35:05.085] [info] Ping 1: 71.22 ms (71.22ms min, 0.00ms jitter)
  [2025-08-19 19:35:05.087] [info] Ping 1: 58.39 ms (58.39ms min, 0.00ms jitter)
  [2025-08-19 19:35:05.090] [info] Ping 1: 52.82 ms (52.82ms min, 0.00ms jitter)
  [2025-08-19 19:35:05.091] [info] Ping 1: 53.52 ms (53.52ms min, 0.00ms jitter)
  [2025-08-19 19:35:05.112] [info] Ping 2: 67.13 ms (66.18ms min, 0.95ms jitter)
  [2025-08-19 19:35:05.133] [info] Ping 3: 56.91 ms (52.70ms min, 3.30ms jitter)
  [2025-08-19 19:35:05.133] [info] Final Ping: 52.70 ms
  [2025-08-19 19:35:05.133] [info] Stage 1 completed
  [2025-08-19 19:35:05.141] [info] Ping 2: 61.93 ms (58.99ms min, 2.94ms jitter)
  [2025-08-19 19:35:05.142] [info] Ping 2: 52.05 ms (52.05ms min, 0.77ms jitter)
  [2025-08-19 19:35:05.143] [info] Ping 2: 51.83 ms (51.83ms min, 1.69ms jitter)
  [2025-08-19 19:35:05.146] [info] Ping 2: 58.98 ms (58.39ms min, 0.60ms jitter)
  [2025-08-19 19:35:05.158] [info] Ping 2: 72.85 ms (71.22ms min, 1.63ms jitter)
  [2025-08-19 19:35:05.163] [info] Ping 1: 38.88 ms (38.88ms min, 0.00ms jitter)
  [2025-08-19 19:35:05.180] [info] Ping 3: 67.92 ms (66.18ms min, 0.87ms jitter)
  [2025-08-19 19:35:05.180] [info] Final Ping: 66.18 ms
  [2025-08-19 19:35:05.180] [info] Stage 1 completed
  [2025-08-19 19:35:05.183] [info] Ping 1: 55.88 ms (55.88ms min, 0.00ms jitter)
  [2025-08-19 19:35:05.193] [info] Ping 3: 50.77 ms (50.77ms min, 1.03ms jitter)
  [2025-08-19 19:35:05.193] [info] Final Ping: 50.77 ms
  [2025-08-19 19:35:05.193] [info] Stage 1 completed
  [2025-08-19 19:35:05.195] [info] Ping 3: 51.80 ms (51.80ms min, 0.86ms jitter)
  [2025-08-19 19:35:05.195] [info] Final Ping: 51.80 ms
  [2025-08-19 19:35:05.195] [info] Stage 1 completed
  [2025-08-19 19:35:05.203] [info] Ping 2: 39.82 ms (38.88ms min, 0.94ms jitter)
  [2025-08-19 19:35:05.203] [info] Ping 3: 61.80 ms (58.99ms min, 1.53ms jitter)
  [2025-08-19 19:35:05.203] [info] Final Ping: 58.99 ms
  [2025-08-19 19:35:05.203] [info] Stage 1 completed
  [2025-08-19 19:35:05.205] [info] Ping 3: 58.77 ms (58.39ms min, 0.40ms jitter)
  [2025-08-19 19:35:05.205] [info] Final Ping: 58.39 ms
  [2025-08-19 19:35:05.205] [info] Stage 1 completed
  [2025-08-19 19:35:05.231] [info] Ping 3: 72.82 ms (71.22ms min, 0.83ms jitter)
  [2025-08-19 19:35:05.231] [info] Final Ping: 71.22 ms
  [2025-08-19 19:35:05.232] [info] Stage 1 completed
  [2025-08-19 19:35:05.239] [info] Ping 2: 55.83 ms (55.83ms min, 0.06ms jitter)
  [2025-08-19 19:35:05.242] [info] Ping 3: 38.87 ms (38.87ms min, 0.94ms jitter)
  [2025-08-19 19:35:05.242] [info] Final Ping: 38.87 ms
  [2025-08-19 19:35:05.242] [info] Stage 1 completed
  [2025-08-19 19:35:05.295] [info] Ping 3: 55.94 ms (55.83ms min, 0.08ms jitter)
  [2025-08-19 19:35:05.295] [info] Final Ping: 55.83 ms
  [2025-08-19 19:35:05.295] [info] Stage 1 completed
  [2025-08-19 19:35:05.297] [info] server selected: 5856
  [2025-08-19 19:35:05.297] [info] Server id: 5856
  [2025-08-19 19:35:05.297] [info] Name: Billings, MT
  [2025-08-19 19:35:05.297] [info] Country: United States
  [2025-08-19 19:35:05.297] [info] Asn:
  [2025-08-19 19:35:05.297] [info] Sponsor: Spectrum
  serverid: 5856
  isp: Spectrum
  [2025-08-19 19:35:05.297] [info] Running TCP test suite
  [2025-08-19 19:35:05.310] [info] Running Speedtest against host:port blngmt-speedtest-ookla-01.st.charter.com:8080
  [2025-08-19 19:35:05.310] [info] Starting stage 1 of type 2
  [2025-08-19 19:35:05.335] [info] Resolved address 1: 69.144.192.154
  [2025-08-19 19:35:05.335] [info] Resolved address 2: 2600:6c66:0:8::6:2
  [2025-08-19 19:35:05.335] [info] Opening socket to '69.144.192.154'
  [2025-08-19 19:35:05.390] [info] Ping 1: 8.88 ms (8.88ms min, 0.00ms jitter)
  [2025-08-19 19:35:05.399] [info] Ping 2: 8.84 ms (8.84ms min, 0.04ms jitter)
  [2025-08-19 19:35:05.408] [info] Ping 3: 8.82 ms (8.82ms min, 0.03ms jitter)
  [2025-08-19 19:35:05.418] [info] Ping 4: 10.03 ms (8.82ms min, 0.42ms jitter)
  [2025-08-19 19:35:05.427] [info] Ping 5: 8.80 ms (8.80ms min, 0.62ms jitter)
  [2025-08-19 19:35:05.427] [info] Final Ping: 8.80 ms
  [2025-08-19 19:35:05.427] [info] Stage 1 completed
  latency: 8
  jitter: 0.62
  [2025-08-19 19:35:05.428] [info] Starting stage 2 of type 4
  [2025-08-19 19:35:06.429] [info] Upload test: Received 4481560 bytes 6% complete 4973984 bytes/sec avg
  [2025-08-19 19:35:07.429] [info] Upload test: Received 5163568 bytes 13% complete 5071045 bytes/sec avg
  [2025-08-19 19:35:08.429] [info] Upload test: Received 4940576 bytes 19% complete 4998546 bytes/sec avg
  [2025-08-19 19:35:09.429] [info] Upload test: Received 5099856 bytes 26% complete 5032712 bytes/sec avg
  [2025-08-19 19:35:10.429] [info] Upload test: Received 4994152 bytes 33% complete 5013729 bytes/sec avg
  [2025-08-19 19:35:11.430] [info] Upload test: Received 5111440 bytes 39% complete 5036648 bytes/sec avg
  [2025-08-19 19:35:12.430] [info] Upload test: Received 5085376 bytes 46% complete 5043647 bytes/sec avg
  [2025-08-19 19:35:13.430] [info] Upload test: Received 5010080 bytes 53% complete 5051587 bytes/sec avg
  [2025-08-19 19:35:14.430] [info] Upload test: Received 5173704 bytes 59% complete 5059404 bytes/sec avg
  [2025-08-19 19:35:15.430] [info] Upload test: Received 4973880 bytes 66% complete 5063252 bytes/sec avg
  [2025-08-19 19:35:16.431] [info] Upload test: Received 5121576 bytes 73% complete 5067334 bytes/sec avg
  [2025-08-19 19:35:17.431] [info] Upload test: Received 5020216 bytes 79% complete 5066335 bytes/sec avg
  [2025-08-19 19:35:18.431] [info] Upload test: Received 5083928 bytes 86% complete 5077072 bytes/sec avg
  [2025-08-19 19:35:19.431] [info] Upload test: Received 5115784 bytes 93% complete 5077943 bytes/sec avg
  [2025-08-19 19:35:20.432] [info] Upload test: Received 5092616 bytes 99% complete 5079608 bytes/sec avg
  [2025-08-19 19:35:21.432] [info] Stage 2 completed
  [2025-08-19 19:35:21.432] [info] Upload test: Received 467704 bytes 100% complete 5079732 bytes/sec avg
  upload: 40637
  [2025-08-19 19:35:21.432] [info] Starting stage 3 of type 3
  [2025-08-19 19:35:21.482] [info] Packet loss sent=319, received=311, dupes=0, maxId=318
  [2025-08-19 19:35:21.498] [info] Resolved address 1: 192.161.70.17
  [2025-08-19 19:35:21.498] [info] Resolved address 2: 2604:ff40:0:300::5
  [2025-08-19 19:35:21.498] [info] Opening socket to '192.161.70.17'
  [2025-08-19 19:35:21.519] [info] Resolved address 1: 63.224.243.198
  [2025-08-19 19:35:21.519] [info] Opening socket to '63.224.243.198'
  [2025-08-19 19:35:21.527] [info] Resolved address 1: 158.120.47.243
  [2025-08-19 19:35:21.527] [info] Resolved address 2: 2604:9440:2301::5060
  [2025-08-19 19:35:21.527] [info] Opening socket to '158.120.47.243'
  [2025-08-19 19:35:23.433] [info] Download test: Received 149079752 bytes 9% complete 102943615 bytes/sec avg
  [2025-08-19 19:35:24.434] [info] Download test: Received 124029688 bytes 16% complete 111542214 bytes/sec avg
  [2025-08-19 19:35:25.434] [info] Download test: Received 130500288 bytes 22% complete 118662038 bytes/sec avg
  [2025-08-19 19:35:26.434] [info] Download test: Received 157039944 bytes 29% complete 132175263 bytes/sec avg
  [2025-08-19 19:35:27.434] [info] Download test: Received 105967181 bytes 36% complete 125845031 bytes/sec avg
  [2025-08-19 19:35:28.435] [info] Download test: Received 148599888 bytes 42% complete 131339020 bytes/sec avg
  [2025-08-19 19:35:29.435] [info] Download test: Received 134401176 bytes 49% complete 132529176 bytes/sec avg
  [2025-08-19 19:35:30.435] [info] Download test: Received 122007768 bytes 56% complete 131775833 bytes/sec avg
  [2025-08-19 19:35:31.435] [info] Download test: Received 128369544 bytes 63% complete 131752714 bytes/sec avg
  [2025-08-19 19:35:32.435] [info] Download test: Received 117212704 bytes 69% complete 132076633 bytes/sec avg
  [2025-08-19 19:35:33.436] [info] Download test: Received 110575072 bytes 76% complete 131910462 bytes/sec avg
  [2025-08-19 19:35:34.436] [info] Download test: Received 152870800 bytes 83% complete 132770091 bytes/sec avg
  [2025-08-19 19:35:35.436] [info] Download test: Received 138076936 bytes 89% complete 133114148 bytes/sec avg
  [2025-08-19 19:35:36.437] [info] Download test: Received 111957912 bytes 96% complete 133274745 bytes/sec avg
  [2025-08-19 19:35:37.094] [info] Stage 3 completed
  [2025-08-19 19:35:37.094] [info] Download test: Received 152668432 bytes 100% complete 133996811 bytes/sec avg
  download: 1071974
  [2025-08-19 19:35:37.097] [info] final result - serverid: 5856 ping: 9 download: 1071974 upload: 40637
  [2025-08-19 19:35:37.097] [info] latency 9ms jitter: 0.62ms packet loss 2.51%
  [2025-08-19 19:35:37.097] [info] total download bytes: 1983357085
  [2025-08-19 19:35:37.097] [info] total download stage duration: 15107.765000 ms
  [2025-08-19 19:35:37.097] [info] total upload bytes: 75936016
  [2025-08-19 19:35:37.097] [info] total upload stage duration: 15017.000000 ms
CrimpOn
Guru - Experienced User
Aug 20, 2025
Thanks for posting the Speed Test information. LOTS more to look at!

Forum Discussion

Orbi 870 WAN performance