"Cat6 speed" gets answered with one number, and the one number is wrong. Cat6 does not have a speed. It has a set of rates, each with its own distance limit, and which of them you actually get depends on the ports at both ends of the link.

Quick answer

RateDistance on Cat6Where it shows up
100BASE-TX100 mLegacy devices, well inside the cable’s capability
1000BASE-T100 mThe standard horizontal rate
2.5GBASE-T100 mNBASE-T, common on access points
5GBASE-T100 mNBASE-T, mid-range access points and uplinks
10GBASE-T55 mServer links, short backbone runs

The figure worth remembering is the last one. Everything above it is comfortable; 10 Gigabit is the rate where Cat6 has a real limit.

Bandwidth is not throughput

250 MHz is a frequency, not a data rate, and the confusion between the two causes a lot of bad procurement decisions.

Bandwidth describes the range of frequencies a cable can carry while still meeting its crosstalk and return-loss limits. Throughput is how many bits per second the electronics can push through that range. A cable with more bandwidth gives the electronics more room to work with, which is why higher rates become possible — but the bandwidth figure does not translate into a bit rate, and a 250 MHz cable is not "250 Mbps fast".

For scale: 1000BASE-T, which runs happily on Cat5e at 100 MHz, uses far less bandwidth than the cable’s ceiling. It gets its throughput by using all four pairs in both directions at once, with sophisticated encoding to separate the two directions. Raising the rate means using the available bandwidth harder, which is where the margin disappears.

Why 10 Gigabit stops at 55 meters

The standard writes the 100-meter 10GBASE-T channel against a 500 MHz cable, which is Cat6A. On a 250 MHz cable the same signal can only be held over a shorter distance, because the impairments that grow with frequency and length — insertion loss and crosstalk — exhaust the budget sooner. The figure the standard settles on for Cat6 is 55 meters.

That is a specification, not a warning label. It is also the single fact that decides a large share of cable upgrades: a building with a 70-meter maximum run cannot use Cat6 for 10G no matter what the switch ports support.

Real installations land inside that limit rather than at its edge. Documented results put 10GBASE-T on Cat6 at 110 feet (33.5 meters) in some installations and 165 feet (50 meters) where alien crosstalk is low. Both are within the 55-meter limit, and both suggest treating Cat6 at 10G as a short-run proposition.

What actually limits throughput in a building

The cable is rarely the only constraint, and sometimes it is not the constraint at all.

What "how fast is Cat6" really means

Four honest answers, depending on who is asking:

For a desk or an access point on Gigabit equipment: 1 Gbps, 100 meters, with margin to spare.

For a modern access point or uplink on 2.5G or 5G hardware: 2.5 or 5 Gbps across the full channel.

For a server or backbone link that needs 10G: 10 Gbps, up to 55 meters, and not one meter further.

For a link where somebody measured a filesystem copy and got 112 MB/s: that is 1 Gbps, and the cable is almost certainly not the reason.

Where 2.5G and 5G fit

The two intermediate rates are the ones that changed the Cat6 calculation, and they get skipped in comparisons that jump straight from 1G to 10G.

2.5GBASE-T and 5GBASE-T were written to extend the working life of the cabling already in the ground. 2.5G runs over Cat5e across the full 100-meter channel; 5G needs Cat6 for the same distance. Neither requires Cat6A, and neither forces a move to fiber.

For access points this is the tier that decides the design. An access point with a 2.5G uplink is an ordinary configuration now, and it is satisfied by cabling many buildings already have. For workstation uplinks, 2.5G makes a visible difference on large transfers without putting a 10G switch and 10G network cards at both ends.

Both rates include a downshift behavior: where the cabling cannot hold the highest rate the two ends have in common, the link steps down instead of failing. That is convenient, and it also means a marginal channel can sit at a lower rate indefinitely without anyone noticing. Read the negotiated rate off the switch rather than assuming it from the port label.

Field scenarios

A school with 1G switches and Cat6 cabling, planning for "faster Wi-Fi". The cabling is not the constraint. Upgrading access points to 2.5G ports and the switch uplinks to 2.5G or 5G will deliver more than any cable change.

A studio with 10G switches and a 62-meter run to a render node. Cat6 will not carry it. Either the run moves, an intermediate switch is added, or the horizontal is replaced with Cat6A.

A warehouse with a 90-meter run to a camera. Fine at 1G, which is what the camera needs. The cable was never the issue.

FAQ

Is Cat6 10 Gigabit? It is specified for 10GBASE-T to 55 meters, and for 1G, 2.5G and 5G across the full 100-meter channel.

Is Cat6 faster than Cat5e? It supports higher rates at full distance: 5G where Cat5e tops out at 2.5G. At 1G the two are identical.

Does Cat6 give me Gigabit internet? Your internet speed comes from your provider. Cat6 removes the local network as a bottleneck, which matters if your connection exceeds 1 Gbps.

What is 250 MHz in Mbps? Nothing directly. 250 MHz is the frequency range the cable is rated to carry; the data rate depends on the encoding and the number of pairs in use.

Will Cat6 run 10G at 70 meters? No. The specified limit is 55 meters. Beyond that, Cat6A is the copper answer.

Does a longer patch cord reduce my speed? It reduces the channel budget available to the permanent link. Whether that costs you speed depends on how close the run already is to its limit.

Related reading on this site