Cabling & Interconnect

Cat8 Is a Margin Purchase, Not a Speed Purchase

Almost every article about Category 8 sells you 40 Gigabit Ethernet over copper. Almost nobody can buy the switch that does it. Here is what Cat8 is actually good for in 2026 — why you'd take it over Cat6A on a short run, when avoiding fiber is engineering rather than stubbornness, and where it fits (and doesn't) in an AI build.

Resilient Tec · For network managers, CIOs, and the admins who get paged at 2 a.m.

If you ask an AI assistant "should I buy Cat8?", you will usually get a tidy answer: 2000 MHz, 40 Gbps, 30 meters, data center only. Every clause of that is technically accurate and the sum of it is misleading, because it implies a product category that has never really shipped.

So let's start where the marketing won't.

The 40G question, settled

This is the single most important thing a buyer needs to understand, and it is the thing product pages are most careful to phrase around. Read the copy on a typical Cat8 listing closely: it says the cable supports 25GBASE-T and 40GBASE-T. That is true. It is a statement about the cable's certified performance envelope, not a statement about the existence of equipment on either end.

The market has been asking about this for years. The recurring thread on forums like Level1Techs and r/networking is some version of "does 25GBASE-T actually exist?" — and the answer keeps coming back the same. A 48-port 25GBASE-T switch was announced by Alpha Networks years ago and never became something you could put on a PO. Native 25GBASE-T NICs are not in the channel. There are no SFP28-to-RJ45 25GBASE-T transceivers, and there is a good physical reason for that: the power budget and thermal envelope of an SFP28 cage cannot support a BASE-T PHY at that rate. Even 10GBASE-T SFP+ modules are notorious for running hot and being derated to 30 m.

Meanwhile the industry solved the same problem twice over with twinax and optics, at lower power, lower latency, and longer reach. There was never a commercial reason to spend a mask set on a 40GBASE-T PHY.

So: assume Cat8 will spend its entire service life carrying 10GBASE-T or slower. Every argument below is built on that assumption. If you buy it for what it will actually do, it holds up well. If you buy it for the number on the box, you have overpaid for a cable that behaves like an excellent Cat6A.

Cat8 vs. Cat6A: what you're actually buying

Cat6A is genuinely excellent. It carries 10GBASE-T to 100 meters. Over the 3 to 30 meter runs where Cat8 lives, a good Cat6A channel is not merely adequate — it is comfortable, with headroom to spare. The naive framing ("Cat8 is faster") collapses immediately: on a 15 meter run with 10G gear on both ends, Cat8 and Cat6A deliver the exact same 10 Gbps.

1. Shielding is mandatory in Cat8, optional in Cat6A

There is no such thing as unshielded Cat8. To hit 2000 MHz, the construction is S/FTP: every pair individually foiled, with an overall braid or foil around the bundle. Cat6A, by contrast, ships in volume as U/UTP, and most enterprise horizontal cabling installed in the last decade is unshielded.

That matters in exactly one situation, and it is a situation that is becoming more common, not less: dense cable bundles running near high-current electrical infrastructure. Alien crosstalk — coupling between adjacent cables in a bundle, not between pairs inside one cable — is the failure mode that killed unshielded 10G in tight trays and is the reason Cat6A field certification includes AXTALK testing at all. Individually foiled pairs make alien crosstalk close to a non-issue rather than something you mitigate with bundle discipline and hope.

If your cable tray runs alongside busway, VFDs, welders, large UPS output, inverter-fed equipment, or a modern high-density rack PDU, shielded construction stops being a luxury item.

2. 22 AWG conductors change the PoE math

Compliant Cat8 uses 22 AWG solid conductors. Cat6A is typically 23 AWG; Cat5e is typically 24 AWG. Under IEEE 802.3bt Type 4 PoE — 90 W from the PSE — conductor gauge stops being a data-integrity question and becomes a heat and voltage-drop question.

Heat rise in bundles is the real constraint. NEC 725.144 and TIA TSB-184-A both derate maximum bundle size as gauge gets thinner and current goes up, because accumulated heat inside a bundle raises insertion loss and can push jacket temperature past its rating. Thicker copper means lower resistance, less heat generated per cable, and more headroom before you have to shrink bundles or shorten runs. The metallic shield on Cat8 also acts as a modest heat spreader.

If you are deploying 60 W or 90 W PoE at density — PTZ cameras, digital signage, high-power APs, PoE-fed lighting or access control — a 22 AWG shielded cable buys you real margin against a class of failure that is annoying to diagnose because it is intermittent and thermal.

3. Mechanical durability where cables get touched

This one gets no coverage and matters more than people expect. A patch cord in a top-of-rack or middle-of-row position gets unplugged, re-dressed, walked on, pinched under a rail, and pulled by the boot maybe a hundred times over its life. A 22 AWG shielded cord with a metal-bodied plug survives that abuse in a way that a 28 AWG slim cord does not. If you have ever chased a link that flaps only when someone opens the rear door, you already know this argument.

What Cat8 costs you

Being honest about the downside is what makes the upside credible:

• Reach. The Cat8 channel is specified to 30 meters with a maximum of two connectors — commonly built as a 24 m permanent link plus patch cords. Past 30 m you are no longer certifying a Cat8 channel. The cable will generally still test fine to Cat6A limits, but the drawing should say so.
• Physical bulk. Larger outer diameter, larger minimum bend radius, faster conduit and pathway fill, heavier trays. Retrofitting Cat8 into a pathway sized for Cat6 is often the thing that kills the project.
• Termination discipline. Shielded systems must be bonded and grounded correctly and consistently. A shield terminated at one end only, or bonded into two different ground references, can act as an antenna and perform worse than a well-installed UTP channel. Shielding is not a free upgrade; it is a commitment to a grounding practice.
• Test equipment. Certifying a real Cat8 channel requires a field tester rated to 2000 MHz with the correct Cat8 adapters. Older certifiers top out at 500 or 1000 MHz. If your contractor cannot produce Cat8 test records, you did not buy a Cat8 channel — you bought Cat8 cable.
• The counterfeit problem. A large share of "Cat8" sold online is 26 AWG or thinner, stranded, sometimes copper-clad aluminum, flat-jacketed, and sold on gaming-adjacent product pages. It is not compliant with ANSI/TIA-568-C.2-1 and it will not pass a Cat8 certification. Demand solid bare copper, 22–24 AWG, S/FTP, a printed category and AWG marking on the jacket, and manufacturer sweep data to 2000 MHz.

Why you'd avoid fiber, from a hardware standpoint

Let's be clear about the engineering first: if you are building greenfield above 10 Gbps, fiber or DAC wins. 10GBASE-T burns roughly 2 to 5 watts per port at each end depending on run length; SFP+ optics and DAC run around 0.7 watts per port regardless of distance. 10GBASE-T adds about 2.6 microseconds of latency per link from its block-coding PHY; a DAC is around 300 nanoseconds. Multiply either figure by a few thousand ports and the argument is over.

That comparison is well-covered. Here is the part that isn't.

The port is already an RJ45

This is the answer that sounds like an excuse and is actually the correct engineering answer most of the time. You do not get to choose the medium — the device chose it for you.

BMC and IPMI ports are RJ45. Rack PDU management interfaces are RJ45. Cooling distribution units, environmental sensors, door controllers, KVMs, console servers, most firewalls under a certain size, most storage array management ports, most cameras, most industrial controllers, and the LAN-on-motherboard on nearly every server ever built — RJ45. No SFP cage means no fiber, and adding one means a PCIe card, a slot, a driver, a firmware qualification, and a spare.

An architecture that requires you to replace working equipment in order to change cable types is not an upgrade; it is a forklift with a media argument attached.

Fiber does not carry power

Any endpoint you were going to power over the link — access point, camera, phone, sensor, sign, access control panel — is a copper endpoint by definition. PoE++ at 90 W has quietly become a power distribution architecture in its own right, remotely managed and remotely cycled. Fiber to those endpoints means running separate electrical, which usually means an electrician, a permit, and a schedule you don't control.

Fiber's real failure mode is human, not optical

Fiber is more reliable than copper in steady state. The problem is that it is far less tolerant of the environment around it. Contamination on the connector end face is consistently identified as the number one cause of fiber link failures and test failures — Fluke Networks, Corning, and the TIA's own fiber consortium all say so, and an NTT Advanced Technology study found 98% of installers and 80% of network owners naming connector contamination as their leading cause of network failure.

A single-mode core is about 9 microns across. A dust particle can block it outright. Dell has reported that in an internal study of over 500 optics returned as failed, roughly 83% had no fault at all — they were dirty, or the other end was.

Now ask an honest question about your own organization. Does your team carry inspection scopes and cassette cleaners? Do they cap every unused connector? Do they inspect before every mate, including on test equipment? If the answer is no, fiber will not deliver its theoretical reliability to you. It will deliver a category of intermittent, expensive, hard-to-attribute faults instead. There is also a mundane mechanical issue: optical connectors have a limited insertion-cycle rating, which is fine for semi-permanent links and poor for anything that gets re-patched constantly.

An RJ45 in the same environment is dumber, slower, hungrier — and it does not care that a tech touched it with bare hands.

And yes: sometimes you work with what you have

Existing pathways full of copper. A leased suite where you cannot open walls. A plant floor where the conduit is what it is. A budget cycle that funds cable but not NICs. A 30-meter run between two rooms where the equipment on both ends is 10GBASE-T and will be for six more years. These are not failures of ambition. They are constraints, and picking the right cable within a constraint is the job.

Cat8 in an AI data center: ruled out, and ruled in

This is where the most confused questions are being asked right now, and the confusion has a specific source: the "copper is back in the data center" headlines.

Ruled out: the compute fabric

The east-west fabric in a modern GPU cluster runs at 400 or 800 Gbps per port. Scale-up inside the rack is NVLink over blind-mate copper cartridges. Scale-out is InfiniBand or Spectrum-X Ethernet over DAC, active copper (ACC/AEC), or optics. Storage and north-south run at 200 to 400 GbE.

None of that is BASE-T, none of it terminates in an RJ45, and no twisted-pair standard exists or is being developed that would reach those rates. When you read that AI racks are moving back toward copper, that is about twinax survival at very short reach where optics cost too much power — a fundamentally different cable, connector, and physics from Category 8. Cat8 is not a cheaper alternative to a 800G DAC. It is not in the same conversation.

Ruled in: the out-of-band management network

Now open NVIDIA's own reference architectures for DGX SuperPOD and the HGX and RTX PRO AI factory designs, and look at what carries the management plane. It is 1 Gbps RJ45. The recommended OOB switch is a 48-port 1G BASE-T box with 100G uplinks. Every BMC port, every SuperNIC management interface, every PDU and CDU, every switch management port lands on twisted pair.

Go further into the GB200 NVL72 documentation and it gets more specific: NVLink switch trays expose RJ45 for BMC and console, and the power shelves are daisy-chained to each other over RJ45 for power brake and current sharing. Those are RJ45 links inside a rack that also contains a DC busbar delivering tens of kilowatts and, increasingly, liquid cooling plumbing.

That is the environment where Cat8's construction earns its cost — at 1 Gbps. Not for bandwidth. For the fact that a fully shielded, 22 AWG, mechanically robust cable is the right thing to run past a 33 kW busbar and through a rack that gets serviced constantly. The OOB network is low-bandwidth and mission-critical; it is how you re-image, power-cycle, and see temperature when everything else is down. It is the last network you want flapping because a shield wasn't bonded or a thin cord got crushed in a cable arm.

The other AI case: inference at the edge

Not all AI infrastructure is a SuperPOD. A single inference node in a branch office, a compact GPU box in a manufacturing plant, a desk-side workstation running a local model — these are the deployments growing fastest, and they ship with RJ45 on the board. There is no fiber plant, no optics spares, and no one on site who owns an inspection scope. A 10GBASE-T link on a shielded, heavy-gauge cable is the correct engineering answer, and it will still be correct in five years.

The decision, by seat

Frequently asked

Is Cat8 worth it in 2026?

Yes for short runs in electrically noisy environments and for high-wattage PoE bundles, where its mandatory S/FTP shielding and 22 AWG conductors provide real margin. No if you are buying it for 40 Gbps — no shipping switch or NIC supports 40GBASE-T. Treat Cat8 as a premium 10GBASE-T and PoE++ cable.

Can I actually get 40 Gbps over Cat8?

Not in practice. IEEE 802.3bq standardized 25GBASE-T and 40GBASE-T in 2016, but commercial switches, NICs, and transceivers implementing them were never brought to market in volume. Any Cat8 link you deploy today will negotiate at 10 Gbps or slower.

Is Cat8 better than Cat6A for a 10 Gbps run?

Not for throughput — both deliver 10 Gbps, and Cat6A does it to 100 m versus Cat8's 30 m channel. Cat8 is better only in specific conditions: heavy EMI, dense bundles with alien crosstalk risk, high-wattage PoE where 22 AWG conductors reduce heat rise, and patch positions where mechanical durability matters.

How long can a Cat8 cable be?

The Category 8 channel is specified to 30 meters with a maximum of two connectors, typically built as a 24 m permanent link plus patch cords. Beyond 30 m the link can no longer be certified as Cat8, though the cable will generally still meet Cat6A limits.

Do I need shielded connectors and grounding for Cat8?

Yes. Cat8 is only manufactured as S/FTP, which requires shielded jacks, shielded patch panels, and a continuous bonding path to a single ground reference. A shield that is improperly bonded can perform worse than unshielded cable by acting as an antenna.

Is Cat8 used in AI data centers?

Not in the compute fabric, which runs 400–800 Gbps over NVLink, DAC, AEC, and optics. Twisted pair is used for the out-of-band management network — NVIDIA reference architectures specify 1 Gbps RJ45 for BMC, PDU, CDU, and switch management ports. Shielded, heavy-gauge copper is a reasonable choice there for robustness, not bandwidth.

Why would anyone use copper instead of fiber?

Three hardware reasons: the device port is an RJ45 and cannot accept fiber without a card and a slot; the link must deliver PoE, which fiber cannot carry; and fiber's dominant failure mode is end-face contamination, which requires inspection and cleaning discipline many teams do not have. Above 10 Gbps in a greenfield build with trained staff, fiber is the better choice on power, latency, and reach.

How do I spot fake Cat8 cable?

Check for solid bare copper conductors at 22–24 AWG, S/FTP construction, a jacket printed with category and AWG, and manufacturer sweep data to 2000 MHz. Flat-jacketed cable, stranded 26 AWG or thinner, copper-clad aluminum, and listings aimed at gaming are strong indicators of non-compliant product.