Updated November 3, 2026: Revised for SC-QAM, OFDM, and OFDMA. Historical comments remain below; some refer to the earlier explanation.

You open a modem status page or CMTS dashboard and see thousands, perhaps millions, of corrected codewords. How bad is that? Before I would call it a plant problem, I want to know what the counter measures and how long it has been running. A big number alone does not tell us whether service is getting worse. Letโ€™s walk through what these counters mean, how to calculate them correctly, and what to check next.

Codeword statistics help locate impairment when treated as receiver measurements over a defined time window. They do not replace MER, spectrum, profile, traffic, or customer-impact data.

What codeword counters measure

A DOCSIS codeword is a block of encoded symbols carried through the physical layer. Forward error correction adds redundancy so a receiver can recover some corrupted symbols without asking for a retransmission. In legacy single-carrier QAM (SC-QAM), Reedโ€“Solomon (RS) coding is part of that process. The receiver counts blocks that arrived without errors, blocks it corrected, and blocks it could not correctโ€”when the vendor exposes those categories with those definitions.

โ€œReceiverโ€ depends on direction. For downstream, the modem reports what it receives; for upstream, the CMTS reports what it decodes from modem transmissions. A CMTS upstream display is not a modem downstream measurement. Identify interface, direction, and reporting object before comparing values.

RS corrects symbol errors, not an arbitrary count of individual bits. With r parity symbols, a conventional RS code can correct up to floor(r/2) unknown symbol errors in one codeword. A symbol is commonly one byte in this context. In a toy example with 16 data symbols and 2 parity symbols, the 18-symbol block can correct one erroneous symbol. Eight flipped bits in that same symbol still represent one symbol error; one flipped bit in each of two different symbols represents two symbol errors and exceeds that exampleโ€™s capacity. This 18-symbol example illustrates the rule; it is not a claim about a DOCSIS-mandated block size.

FEC does not suddenly switch on when a customer packet exceeds 16 bytes. It operates on the defined encoded blocks. The correction limit depends on the code parameters, and failures beyond that capability can leave corrupted data unrecovered.

Read counters by technology

A counter named โ€œcorrectedโ€ does not mean the same thing on every DOCSIS channel. SC-QAM and DOCSIS 3.1 OFDM/OFDMA use different FEC chains and management semantics, so equal-looking percentages may represent different decode stages.

On a narrow screen, scroll the table horizontally to see all columns.
Channel and direction Receiver What to check
SC-QAM downstream Cable modem Legacy RS codeword counters reported by the modem; confirm the vendorโ€™s exact object definitions.
SC-QAM upstream CMTS Legacy upstream receiver counters. Some โ€œunerroredsโ€ objects count only error-free codewords, so corrected and uncorrectable counts must be added for a total.
OFDM/OFDMA Modem downstream / CMTS upstream Downstream OFDM data uses concatenated BCHโ€“LDPC; upstream OFDMA uses LDPC. Check the direction, profile, and MIB definition. Total-codeword counters are normally inclusive; do not add corrected counts again.

For downstream OFDM data, CableLabsโ€™ PNM primer, section 5.4.5, describes concatenated BCHโ€“LDPC FEC. In that example, codewords that fail a pre-LDPC syndrome check but pass BCH can count as corrected. Depending on the counter definition, corrected percentages near 100% can occur normally. This is not directly comparable to an SC-QAM downstream post-trellis RS rate. Consult the MIB and device documentation for the specific object and measurement point.

Upstream OFDMA uses LDPC without that outer BCH stage. CableLabs describes corrected codewords as failing the pre-decoding syndrome check but passing the post-decoding check, and unreliable codewords as failing the post-decoding check. An unreliable codeword can still contain error-free data bits, so use MAC CRC results and service measurements to establish the impact. This is another reason to read the field definition before treating every dashboard label as interchangeable.

For SC-QAM, Ciscoโ€™s return-path monitoring guide and the MIB provide useful context. One example is docsIf3CmtsCmUsStatusUnerroreds, which counts codewords received without error. If that is your โ€œgoodโ€ count, it excludes corrected and uncorrectable codewords. Some OFDM total-codeword counters, by contrast, are already inclusive. Do not add corrected and uncorrectable counts to a total unless the definition requires it; doing so double-counts codewords.

Calculate an interval rate

First confirm whether you have interval counts or cumulative counters. If you can obtain deltas over the same interval for error-free (E), corrected (C), and uncorrectable (U) codewords, and those three classes are mutually exclusive and exhaustive, calculate:

Uncorrectable rate (%) = 100 ร— U / (E + C + U)

The corrected rate under the same definitions is 100 ร— C / (E + C + U). If the vendorโ€™s โ€œtotalโ€ already includes all codewords, use that total once as the denominator. Do not add the categories again. If the definitions are unclear or overlap, stop before publishing a percentage and resolve the counter semantics first.

For a worked interval, suppose a channel reports 1,000,000 error-free codewords, 20,000 corrected codewords, and 500 uncorrectable codewords. The total for this calculation is 1,020,500. The uncorrectable rate is 100 ร— 500 / 1,020,500, or about 0.049%; the corrected rate is about 1.96%. These are rates of codewords in that sample interval. They are not packet-loss or bit-error rates.

The original articleโ€™s CMTS sample showed 13,861,878 good, 760,804 corrected, and 47,090 uncorrectable codewords. If these are mutually exclusive categories, the combined count is 14,669,772. The uncorrectable share is about 0.321%, and corrected is about 5.186%. Without aligned start and end times, these historical figures do not establish a current rate or service condition.

For cumulative counters, subtract two aligned readings. Check uptime, interface resets, profile changes, and the discontinuity indicator; SNMP counter discontinuities and wrap behavior are defined in RFC 2578. Counters may wrap at their defined maximum or reset; confirm the event and handle wrap using the counter width before calculating. If a reset or discontinuity occurred, discard that interval and establish a new baseline. If no codewords were counted, the denominator is zero: report โ€œno samples,โ€ not zero percent.

What the number can and cannot tell you

An uncorrectable codeword means the receiver could not recover that codeword at the measured FEC stage. It does not, by itself, tell you how many IP packets were lost. A packet can span multiple physical-layer codewords, and counters may aggregate traffic for many modems or channels. Higher layers may recover some impact through TCP retransmission, QUIC recovery, or application retries; latency-sensitive traffic may experience delay, jitter, or loss differently. Correlate the physical-layer interval with packet, transport, and application observations before describing customer impact.

I treat a 1% uncorrectable codeword error rate as a practical action threshold. At and above that level, users can begin noticing service degradation, particularly with real-time applications such as voice. This is a well-established troubleshooting threshold, not a universal boundary where every service suddenly fails. Ciscoโ€™s legacy upstream FEC guidance flags 1% and above in red and warns that voice quality can be affected at that level. Do not wait for 1% before investigating: burst errors and sensitive applications can cause noticeable problems below it. Calculate the percentage over a defined interval, confirm the counterโ€™s meaning, and correlate it with packet loss, latency, and the customerโ€™s symptoms. This threshold concerns uncorrectable codewords, not corrected codewords; do not apply it blindly to OFDMA unreliable-codeword counters.

Likewise, a cumulative corrected counter that rises every day is expected on an active channel. A larger absolute number does not show that conditions are worsening unless you compare normalized rates over comparable intervals and account for changes in traffic volume, channel configuration, uptime, and measurement coverage. Trend interval deltas, not lifetime totals.

Troubleshoot with correlated data

When a rate changes or uncorrectables appear, shorten the collection interval enough to localize the event. Compare aligned codeword deltas with receive MER, spectrum captures, ingress or impulsive noise indicators, clipping, reflections or micro-reflections, and channel/profile changes. For OFDM, examine RxMER by subcarrier and the profile assignment over the same window; a channel-wide average can hide a localized impairment or a profile transition.

Check whether affected channels, service groups, or neighboring receivers show the same time pattern. A shared event points toward a common plant or node condition; a single receiver may indicate a local drop, connector, or device issue. That is a lead to investigate, not proof of root cause. Verify with field measurements and traffic symptoms, and preserve the time window and device state so the evidence can be reproduced.

I recommend starting with a short, repeatable interval, documented counter definitions, uptime, channel/profile identity, and synchronized MER or spectrum data. Then you can compare before and after a plant action.

Frequently asked questions

Are corrected codewords a problem?

Not automatically. FEC is designed to correct errors, and some corrected-codeword countersโ€”especially certain DOCSIS 3.1 OFDM countersโ€”can be high during normal operation. Confirm the decoding stage and trend the rate over a defined interval alongside MER and other evidence.

Do uncorrectable codewords prove subscribers are losing packets?

No. They show that a physical-layer codeword failed at the measured receiver and FEC stage. They do not map one-to-one to IP packets or prove a user-visible loss event. Correlate with packet or application data and the affected traffic path.

Can I compare an OFDM corrected percentage with an SC-QAM percentage?

Generally, not as if they were the same metric. The FEC chain and counter definitions differ, and a DOCSIS 3.1 corrected counter may represent a different stage than legacy RS. Compare like-for-like channels and documented objects, or report the raw values with their definitions.

For deeper context, see OFDM and SC-QAM codeword calculations, DOCSIS timeout descriptions, and T3 timeouts and service impact. For help correlating telemetry with plant conditions, contact Volpe Firm about broadband consulting.