Author: Site Editor Publish Time: 09-01-2026 Origin: Site
A practical guide for understanding Ethernet cable distance limits, permanent link design, channel length, patch cord allowance and common installation mistakes in structured cabling projects.
100m Ethernet distance usually refers to the complete channel, including horizontal cable and patch cords.
90m permanent link refers to the fixed installed cable between the patch panel and the work area outlet.
If patch cords are too long, the permanent cable route may need to be shorter to keep the complete channel within the recommended limit.
In structured cabling, the commonly mentioned 100m Ethernet cable limit normally refers to the complete channel from network equipment to end device. This includes the fixed horizontal cable, patch panel connection, work area outlet and patch cords at both ends.
The 90m permanent link is the fixed installed cable route, usually from the patch panel in the telecom room to the work area outlet. The remaining length is typically reserved for patch cords and equipment cords. This design helps installers keep the full channel within the recommended distance while allowing practical connection flexibility.
Design the fixed horizontal cable as a 90m maximum permanent link, then control patch cord length carefully so the complete channel does not exceed 100m.

Permanent link and channel are often confused, but they are not the same. Understanding the difference helps avoid failed tests, unstable links and wrong cable purchasing decisions.
| Term | What It Includes | Typical Maximum | Why It Matters |
|---|---|---|---|
| Permanent Link | Fixed cable from patch panel to work area outlet | 90m | Used for fixed infrastructure design and acceptance testing. |
| Channel | Complete link including patch cords, patch panels, outlets and equipment cords | 100m | Represents the actual end-to-end network connection used by devices. |
In simple terms, the permanent link is the fixed building cabling. The channel is what the network equipment actually uses after patch cords are connected.
A typical office or commercial building Ethernet link includes a patch cord in the telecom room, a patch panel, a fixed horizontal cable, a wall outlet and a work area patch cord.
| Part of Link | Example Component | Included in Permanent Link? | Included in Channel? |
|---|---|---|---|
| Equipment Patch Cord | Switch to patch panel cord | No | Yes |
| Patch Panel | 24-port or 48-port patch panel | Yes | Yes |
| Horizontal Cable | Cat6 or Cat6A solid cable | Yes | Yes |
| Work Area Outlet | Keystone jack or wall plate | Yes | Yes |
| Work Area Patch Cord | Outlet to computer, AP or IP phone | No | Yes |

Ethernet cable length is limited because electrical signals weaken and become more vulnerable to noise, crosstalk and timing issues as distance increases. Longer cable runs create higher insertion loss and can reduce the available performance margin, especially at higher speeds.
The signal becomes weaker as the cable run becomes longer, reducing performance margin.
Longer runs and poor installation can make the link more sensitive to interference and pair-to-pair noise.
For PoE devices, long copper runs can increase voltage drop and heat, especially with high-power loads.
Cable category affects bandwidth and performance margin, but it does not automatically allow unlimited distance. Good installation practice still follows structured cabling design limits.
| Cable Category | Typical Use | Distance Planning Note | Buyer Reminder |
|---|---|---|---|
| Cat5e | General Gigabit Ethernet | Suitable for many standard 100m channel designs. | Check conductor material and certification quality. |
| Cat6 | Gigabit networks, some shorter 10G links | Good for standard office and commercial projects. | Do not assume long 10G performance in every installation. |
| Cat6A | 10G-ready structured cabling | Better performance margin for high-speed links within structured cabling limits. | Watch cable OD, bend radius, pathway fill and termination quality. |
Patch cords are easy to overlook because they are installed at the final stage. However, they are part of the channel length. If patch cords become too long, the total channel may exceed the recommended design limit even if the fixed cable run is acceptable.
| Scenario | Risk | Better Practice |
|---|---|---|
| Long patch cords at both ends | Channel may exceed 100m | Keep patch cords short and plan cabinet layout carefully. |
| Messy cabinet routing | Unnecessary cable slack and bend stress | Use suitable patch cord lengths and horizontal cable managers. |
| Remote device too far from outlet | Work area cord becomes too long | Add a closer outlet, small switch or consider fiber for longer routes. |
| High-power PoE device at long distance | Voltage drop and heat may increase | Use appropriate AWG, pure copper cable and avoid excessive bundles. |

Distance problems are not always caused by cable length alone. Termination quality, bend radius, cable category, patch cord quality and cable routing can all affect the final performance.
90m fixed link plus controlled patch cord length keeps the channel within a safe design margin.
Long cords at both ends can push the total channel beyond the recommended limit.
A copper run beyond the design limit may cause unstable speed, packet loss or failed certification testing.
The simplest way to avoid distance problems is to separate fixed infrastructure planning from patch cord planning.
| Project Condition | Recommended Action | Reason | Checkpoint |
|---|---|---|---|
| Standard office horizontal cabling | Use 90m permanent link design | Leaves room for patch cords at both ends. | Measure actual route before installation. |
| Long route near 100m | Shorten route or use network equipment midpoint | Avoid weak performance margin. | Check channel test result after installation. |
| High-speed 10G requirement | Choose Cat6A and control installation quality | Provides better performance margin for 10G. | Check alien crosstalk, bend radius and termination. |
| Long PoE camera or AP run | Use pure copper cable with suitable AWG | Reduces voltage drop and heat risk. | Avoid CCA cable for PoE loads. |
| Distance beyond copper limit | Use fiber, active equipment or redesign topology | Copper Ethernet is not ideal for very long routes. | Confirm power, data rate and equipment location. |
90m is for fixed cabling. 100m is for the complete working channel. If the real route is close to the limit, shorten the copper run, reduce patch cord length or consider fiber.
For project buyers, cable length planning should be confirmed before ordering bulk cable, patch cords, patch panels and keystone jacks. A good cabling system depends on all components working together.
Confirm Cat5e, Cat6 or Cat6A, conductor material, AWG, jacket type, shielding and cable box or drum length.
Confirm short, medium and long patch cord options based on cabinet layout and work area distance.
Confirm whether the project requires wiremap, channel test, permanent link test or certification report.
A complete Ethernet cabling RFQ should include cable category, length plan, permanent link target, patch cord length, connector type, patch panel type, test requirement and installation environment.
For most structured copper Ethernet cabling designs, the complete channel is commonly planned within 100m.
It means the fixed installed cable path between the patch panel and work area outlet is planned within 90m.
Yes. The channel includes patch cords, equipment cords, patch panel connections, horizontal cable and outlet connection.
Cat6A improves performance margin for 10G applications, but standard structured cabling design still follows the channel length limit.
Consider relocating equipment, adding a network switch, using fiber optic cable or redesigning the topology.
Long PoE links can increase voltage drop and heat, so conductor material, AWG and bundle size should be checked carefully.
ZION Communication can support Cat5e, Cat6, Cat6A bulk cable, patch cords, patch panels, keystone jacks and customized copper cabling solutions for offices, data centers, industrial networks and OEM projects.
