A desktop PC connects to a Wi‑Fi router via Ethernet, while PowerShell shows the wired adapter up at 1 Gbps and Wi‑Fi disconnected.
The tiny lights beside an Ethernet socket can reveal a useful networking problem before you open a browser: on hardware with a speed indicator, they show the connection rate established with the device at the other end of the cable. But there is a catch big enough to trip over behind your desk: green does not universally mean gigabit, and no port light is an internet speed test. Intel’s own documentation provides a particularly clear counterexample—its I210-T1 adapter uses amber for a gigabit link and green for 100Mbps.

MakeUseOf’s Gavin Phillips highlights these often-overlooked indicators as a quick troubleshooting aid. The idea is useful, provided we separate three things that are easily confused: whether a physical link exists, the rate of that link, and how quickly data actually reaches its destination.

A desktop PC connects to a Wi‑Fi router via Ethernet, while PowerShell shows the wired adapter up at 1 Gbps and Wi‑Fi disconnected. What Ethernet lights actually tell you​

On Intel’s I210-T1, two LEDs have distinct jobs:

  • Link/activity: Off means no link, steady illumination means a link exists, and blinking indicates activity.
  • Speed: A separate indicator identifies the established connection rate.

That blinking activity light is not specifically an “internet activity” indicator. Intel documents it simply as activity; it does not certify that an internet connection is working.

Microsoft makes a similar distinction in its Windows driver documentation. The adapter’s link state includes its current transmit and receive link speeds, alongside separate connection-state and duplex information. These are properties of the adapter’s connection—not measurements of a download from an online service.

The practical implication is straightforward: a gigabit link indicator tells you something useful about that Ethernet segment, but it cannot establish the performance of the entire route through your network and out to the internet. That is a diagnostic clue, not a miniature benchmarking laboratory.

Why Ethernet LED colors need a manual​

The safest rule is also the least glamorous: read the LED legend for your exact hardware. Two documented products show why a universal color chart would be misleading.

HardwareSpeed LED offSpeed LED greenSpeed LED amber/orange
Intel Ethernet Server Adapter I210-T110Mbps100Mbps1Gbps
ASUS ROG Strix Z790-F Gaming WiFi IINo link, or a 10/100Mbps connection2.5Gbps1Gbps

Intel’s support article and ASUS’s motherboard manual document these respective meanings. On the ASUS board, the separate link/activity LED helps distinguish a working lower-speed connection from no connection at all.

Notice the trap: green means 100Mbps on one product and 2.5Gbps on the other. An unlit speed LED can also accompany a functioning connection. Judging either device by color alone could send you shopping for replacement hardware you do not need.

These examples do not mean the hardware is behaving strangely. They mean its indicators must be interpreted using its documentation, rather than a remembered rule about another router.

Check Ethernet status from Windows​

If the port is hidden behind a tower—or its lights are ambiguous—Windows offers another route to adapter information.

On a Windows 11 PC, open Windows PowerShell and run:

Get-NetAdapter

Microsoft documents this command as retrieving basic network-adapter properties, with a table as its default output. To inspect all properties for the visible adapters, run:

Get-NetAdapter | Format-List -Property *

This is an inspection step, not a command that changes your network configuration. Microsoft’s documentation explicitly supports retrieving and displaying these adapter properties.

Identify the physical Ethernet adapter rather than assuming the first entry is the wired connection you are investigating. If its identity is unclear, this command narrows the list to physical adapters:

Get-NetAdapter -Physical

Microsoft documents the -Physical option for that purpose. Use the adapter’s reported link information alongside the hardware’s LED legend; neither should be interpreted as an internet throughput measurement.

How to investigate an unexpectedly slow link​

A useful troubleshooting sequence starts with identifying the condition before deciding its cause:

  1. Identify the exact port and device. Record the adapter, motherboard, router, or switch model.
  2. Find the manufacturer’s LED table. Establish which light indicates link/activity and which indicates speed, if any.
  3. Compare the indicated rate with both ports’ capabilities. A faster port at one end does not establish what the other end supports.
  4. Cross-check the computer’s adapter status. Use Windows PowerShell when the light is inaccessible or unclear.
  5. Investigate the connection systematically. Consider the cable, connectors, connected port, and configuration rather than treating one LED color as a verdict.

Intel and ASUS support the model-specific interpretation in the first two steps; Microsoft documents the adapter inspection commands. Cisco’s switch-to-adapter troubleshooting guidance also treats cabling and compatibility/configuration as separate areas to investigate. A lower-than-expected rate is evidence of a condition—not proof that the cable alone caused it.

Success at this stage means confirming that the particular Ethernet connection is operating at the expected rate. It does not yet mean every application or internet download will achieve that rate. Microsoft’s definition of adapter link speed is deliberately narrower than that.

A fast first link can hide a slower middle​

Phillips’s MakeUseOf article describes upgrading a router and Ethernet cable while an older powerline adapter remained the bottleneck. That is the author’s reported experience, not independent testing here, but it illustrates the central limitation well: the router’s Ethernet light cannot describe the performance of the entire powerline path.

The broader troubleshooting lesson follows from the link-specific nature of adapter status: inspect the connection that a light actually represents, then consider the rest of the path separately. Do not assume that one slow segment makes every other port renegotiate to the same rate, or that one fast segment guarantees fast end-to-end performance.

The bottom line: Ethernet lights can save time when you know their documented meaning. Use them to spot an unexpected local link rate, use Windows to corroborate adapter status, and measure throughput when throughput is the question. The LED is a helpful witness—but it should not be asked to testify about a network it cannot see.

 

References

  1. Your Ethernet port’s light color is a speed test you never have to run MakeUseOf 2026-11-16T13:21:38+00:00
  2. Network interface speed and autonegotiation | Ethernet interfaces | Interfaces and Hardware Component Configuration Guide for Cisco 8000 Series Routers, Cisco IOS XR Releases - Cisco cisco.com
  3. How to Read the Status LEDs for Intel® Ethernet Server Adapter I210-T1 intel.com