Starlink Ethernet Stuck at 100 Mbps? How to Find a Cable, Port or Negotiation Problem

Why a Starlink connection can look slower than it should

If a device connected by Ethernet reports a 100 Mbps link, the local cable path may be limiting the connection before Starlink has a chance to deliver its full service speed. This is different from normal satellite-speed variation. A Starlink connection can slow down because of congestion, obstructions, Wi-Fi interference or a busy home network, but a wired interface that has negotiated at 100 Mbps has already identified a local network problem worth fixing.

The most useful clue is the negotiated link speed shown by the device or network switch:

• 100 Mbps or 100/100 Mbps: usually a cable, connector, wall jack, adapter or port negotiation problem.
• 1 Gbps or higher: the physical Ethernet link is probably healthy; investigate the Starlink connection, router load, Wi-Fi, testing method or upstream congestion instead.
• No link: check power, port selection, cable seating and adapter compatibility first.

Do not start by buying a longer cable or changing Starlink settings. Confirm which part of the path is limiting you.

Before you test

Have these items ready:

• A laptop or desktop with a known-good Ethernet port or USB Ethernet adapter.
• A short, tested Cat5e or Cat6 patch cable.
• Access to the Starlink router, Ethernet adapter, third-party router or switch.
• The device's link-speed view, or a managed switch that shows negotiated speed.
• A simple speed-test method that can be repeated from the same wired device.

Avoid comparing a wired test on one device with a Wi-Fi test on another. Keep the test device, cable, router path and test server consistent while you troubleshoot.

1. Check the negotiated link speed

First, check what the device says about its Ethernet connection. Look for a field called Link speed, Speed, Connection speed or Ethernet status. A value of 100 Mbps is the important finding; it is not the same as a speed-test result of 100 Mbps.

On Linux, a wired interface can usually be checked with a tool such as ethtool. On Windows, open the Ethernet connection properties or status view. On macOS, use the network hardware information for the active Ethernet adapter. The exact menu names vary by operating-system version, so focus on the negotiated value rather than following a particular screenshot.

If the link is already 1 Gbps, do not keep replacing cables at random. Move to the speed-test checks in step 5.

2. Test the shortest possible path

Temporarily remove everything that is not needed:

1. Connect the test computer directly to the Starlink router's Ethernet output, Ethernet adapter or your configured third-party router.
2. Use the short known-good cable.
3. Bypass wall sockets, patch panels, powerline adapters, docks, switches and mesh nodes.
4. Turn off Wi-Fi on the test computer so it cannot silently use another connection.
5. Check the negotiated link speed again.

If the direct connection changes from 100 Mbps to 1 Gbps, the fault is somewhere in the equipment you removed. Add those parts back one at a time until the link drops again.

If the direct connection still negotiates at 100 Mbps, continue with the cable and adapter checks below.

3. Check the cable and connectors

Gigabit Ethernet normally needs all four twisted pairs in the cable path. A damaged pair, poor termination or partially seated plug can leave a connection working at 100 Mbps while preventing a gigabit negotiation.

Work through these checks:

• Unplug and firmly reseat both ends. Look for a latch that does not hold the plug securely.
• Replace the cable with the short known-good Cat5e or Cat6 cable.
• Inspect plugs for bent contacts, cracked housings or cables crushed under furniture.
• If you use a wall jack or keystone, bypass it with a temporary patch cable.
• If the cable was custom-terminated, check that all eight conductors are present and follow the same wiring standard at both ends.
• Do not assume a cable is good because it passes some traffic. A cable can support 100 Mbps while failing the requirements for gigabit.

After each change, check the negotiated link speed. This is faster and more reliable than running a speed test after every cable swap.

4. Check ports, adapters and intermediate equipment

If a known-good cable does not fix the problem, test the other physical components:

• Try a different LAN port on the router or switch, if one is available.
• If the computer uses a USB Ethernet adapter or dock, connect a different adapter or connect directly to the computer's built-in port.
• Check whether a switch port is manually limited to 100 Mbps.
• Temporarily remove an unmanaged switch, powerline adapter or mesh node from the path.
• Confirm that the adapter is not being used through a low-speed USB hub.
• Reboot the router, switch and adapter after changing the physical path, then check the negotiated speed again.

Avoid forcing a port to 1 Gbps full duplex as a first fix. Auto-negotiation is normally the correct setting, and forcing one side can create a mismatch or make the link less reliable. Change manual speed or duplex settings only when you have a documented reason and know how to restore the original setting.

5. Separate a local Ethernet fault from Starlink performance

A 1 Gbps link does not mean Starlink will deliver 1 Gbps on every test. It only tells you that the local wired path is not capped at 100 Mbps.

Once the link is healthy:

1. Run a speed test from the same wired device.
2. Repeat it at different times rather than relying on one result.
3. Close large downloads, cloud backups and video uploads.
4. Compare the result with the Starlink app's current status and obstruction information.
5. If possible, repeat the test with a second wired device.

If two wired devices show similar results, the issue is more likely upstream of the individual computer. If only one device is slow while its link is 1 Gbps, check that device's CPU load, VPN, security software, browser and background transfers.

When using bypass mode or a third-party router, the same principle applies: test the exact Ethernet segment between the Starlink equipment and the router, then the segment between the router and the device. A router-mode change cannot repair a damaged cable or a port that has negotiated at 100 Mbps.

A quick decision tree

The device reports 100 Mbps

• Replace the patch cable.
• Bypass wall jacks, switches and docks.
• Try another port.
• Test another Ethernet adapter or computer.
• Inspect or re-terminate the fixed cable run.
• Recheck the negotiated speed after every change.

The device reports 1 Gbps, but the speed test is slow

• Repeat the test while wired.
• Test at another time.
• Stop competing downloads and uploads.
• Check for VPN, security software or a busy router.
• Compare with another wired device.
• Review Starlink status, obstructions and local network load.

The device has no link

• Confirm the correct port and power.
• Reseat both ends.
• Try the known-good cable.
• Remove intermediate equipment.
• Test another port or adapter.

When the problem is fixed

Leave the network in the simplest known-good layout and document what changed. If a wall jack, switch or USB dock caused the 100 Mbps negotiation, label it rather than quietly putting it back into service.

For a permanent cable run, test the finished path at both ends before closing walls, sealing conduit or moving equipment into its final position. Keep a short known-good patch cable available; it is a useful reference whenever a future speed problem appears.

The final check is simple: the wired device should negotiate at the expected speed, and repeated speed tests should be interpreted separately from that local link result. Fix the physical Ethernet limit first, then tune the Starlink network only if the evidence still points beyond the cable path.