02-03-2026 09:14 AM
Im having a fiber connection 1000/1000 delivered via my ISP.
I have plugged in the google mesh network, and the cable, and day 1, it worked fine 1000/1000, running the cable from the main point to my pc.
Then on day 5 i was downloading a steam game, and saw it capped at 100/100, so i looked into windows settings and saw it indeed had registerd as a 100/100 connection all of the sudden.
Then i went on debugging, to debug the cable i tried a different router NighthawkR7000 and could get a 1000/1000 connection right from the get go no issues. Decided to try and factory reset the google mesh network, cause some post on reddit said they did that and it worked, it then had a 1000/1000 connection.
This evening i started my PC and we are back to a 100/100 connection on the google nest wifi pro, the wifi states 1000/1000, but the cable connection is limited to 100/100... WTF is going on ? (how do i fix this without having to replace my google nest wifi pro setup? (some posts on reddit suggest that i should run the wifi mesh network in bridge mode, would look something like this fiberbox -> nighthawkR7000 -> google mesh in bridge mode, but im unsure if that is even possible)
02-05-2026 09:25 AM
Hello @MarcHenriksen
Any time I see an Ethernet link running at 100Mbps instead of 1Gbps (or falling back to that speed), I focus on the cable itself, or how it's connected to one end or the other. 100Mbps doesn't need all eight wires in the cable to connect, but 1Gbps does. It sounds like your cable is likely not the issue itself (though that's not a guarantee when issues like this are intermittent). But, one common issue is getting extremely stiff cables (like Cat6 or higher) to keep the outer pins connected reliably when the cable bends near the port it's connected to. If you can use more flexible Cat 5e (or even Cat 5) cables, they may be more reliable and are still designed for 1Gbps connections. If you must use stiffer Cat6 or higher cables, you may need to pay special attention to how much side-to-side pressure is on them on either end of the connection.
I would focus on solving the problem at this layer before considering any more radical topology or equipment changes.