Accessing the DOCSIS Signal Page
DOCSIS cable modems expose their signal statistics at 192.168.100.1 — open a browser and type that address. If your ISP provided a combo modem/router gateway, try 192.168.1.1 or 192.168.0.1 and look for a Signal, Status, or Connection tab. On most modems you do not need a password to view the signal page (though some ISPs lock these down). Look for sections labeled “Downstream,” “Upstream,” and “Event Log.”
DOCSIS 3.0 modems bond multiple downstream channels (typically 8, 16, or 24) and multiple upstream channels (typically 4 or 8). DOCSIS 3.1 adds OFDM downstream channels and OFDMA upstream channels alongside the legacy SC-QAM channels. All of them show on this page. Read each channel individually — a bad cable problem often affects just some channels, not all of them.
Downstream Signal Levels
| Metric | Good Range | Marginal | Bad (Call ISP) |
|---|---|---|---|
| Downstream receive power (SC-QAM) | -7 to +7 dBmV | -10 to -8 or +8 to +10 dBmV | Below -10 or above +10 dBmV |
| SNR / MER (QAM64 channels) | >23.5 dB | 20–23 dB | Below 20 dB |
| SNR / MER (QAM256 channels) | >30 dB | 27–30 dB | Below 27 dB |
| OFDM receive power (DOCSIS 3.1) | -15 to +15 dBmV | -18 to -16 or +16 to +18 dBmV | Outside ±18 dBmV |
| Corrected errors | Rising slowly over days/weeks | Rising faster than normal | Rising rapidly by thousands per hour |
| Uncorrected errors | Zero or near-zero | Single-digit per hour | Any nonzero and growing count |
Downstream power that is too low means the signal arriving from the ISP's headend is weak — common causes include a long coax run, too many splitters in the line, or a corroded outdoor tap. Downstream power that is too high means the tap amplifier is overdriving the signal, which can intermodulate and cause errors just as readily as a weak signal.
Upstream Signal Levels
| Metric | Good Range | Marginal | Bad (Call ISP) |
|---|---|---|---|
| Upstream transmit power (SC-QAM) | 38–48 dBmV | 49–51 or 35–37 dBmV | Above 51 or below 35 dBmV |
| OFDMA transmit power (DOCSIS 3.1) | 34–44 dBmV | 45–48 dBmV | Above 48 dBmV |
Upstream power is the most telling single number. It shows how hard your modem is pushing to reach the ISP. When this is high — say, 50 dBmV or above — it means the path from your modem to the ISP's node has high loss. The modem cranks up its transmitter power to compensate. Eventually the modem cannot push hard enough, and you start getting T3 timeouts (ranging failures) followed by disconnections. High upstream power almost always means a problem with the coaxial plant: a bad connector, water intrusion in an outdoor drop, a failing splitter, or a deteriorating drop cable from the tap to your home.
The Event Log: T3 and T4 Timeouts
The event log is the other critical page. Look for entries with DOCSIS time codes. The ones that matter:
- T3 timeout (No Ranging Response received) — your modem sent a ranging request and the ISP's headend did not respond. This is an upstream communication failure. A few T3s after a power outage are normal (the modem is re-registering). Recurring T3s during normal operation are a line problem.
- T4 timeout — your modem lost contact with the headend entirely and had to re-initialize. Each T4 causes a brief internet outage. Any T4 events during a 24-hour period are worth reporting to your ISP.
- MDD Timeout (DOCSIS 3.0/3.1) — the modem did not receive an MDD message from the CMTS, indicating downstream loss or CMTS issues.
- SYNC Timing Synchronization Failure — the modem lost downstream synchronization. Often paired with a modem reboot.
Common Causes and What You Can Fix Yourself
Before calling your ISP with a signal complaint, eliminate the causes you can address yourself. The most common culprit is a splitter on the coaxial line between the wall outlet and the modem. Every two-way splitter adds approximately 3.5 dB of loss on each port; a three-way splitter adds about 5.5 dB. If a cable box or TiVo shares the line with the modem through a splitter, disconnect the splitter and run the modem on a direct line temporarily. If signal levels improve significantly, the splitter is contributing to the problem.
Also check the coaxial connectors at both ends of the cable from the wall to the modem. A loose F-connector that you can wiggle by hand will cause intermittent upstream problems. Hand-tighten it. Check that the cable does not have a sharp kink or a staple through it. If you have any coaxial cable that is older than 15 years, especially the flimsy cable that comes with cable boxes, replace it with a proper RG6 quad-shield cable.
Frequently Asked Questions
My SNR looks fine but I still have issues. What else could be wrong?
SNR is an average across the channel. Impulsive noise — short bursts of interference from a failing power supply, an arcing connector, or outside electrical interference — does not always show up as degraded average SNR. Instead, it shows up as uncorrected errors that spike briefly and then disappear. Check your uncorrected error counts and whether they increase at specific times of day (when an appliance cycles on, when traffic is heavy on the street). Also check the event log for T3 timeouts that correlate with the times you notice problems.
Should all my downstream channels have similar power levels?
Yes, roughly. Channels that share the same coaxial cable path should have similar receive power — within a few dBmV of each other. If one or two channels are significantly weaker or stronger than the others, it can indicate a frequency-dependent issue like a failing splitter that has different loss characteristics at different frequencies, or an outdoor tap that is aging unevenly. Report significant channel-to-channel power variation to your ISP.
What is the difference between corrected and uncorrected errors?
DOCSIS uses Reed-Solomon and LDPC forward error correction to fix errors in received data. Corrected errors are ones the modem fixed using error correction math — the data was received with bit errors but the modem could reconstruct the correct value. These accumulate over time and a slow, steady rise is normal. Uncorrected errors are ones where the error correction failed — too many bits were wrong to recover the data. These cause retransmissions, latency spikes, and in bad cases, TCP session resets. Zero uncorrected errors is the target. Any significant rising count means the raw channel quality is below the threshold where error correction can compensate.
Does rebooting the modem fix signal problems?
A reboot clears the error counters and re-runs the ranging process, which may push the modem to a slightly different upstream power level. But if the underlying signal problem is physical — a bad connector, a corroded drop, a splitter insertion loss — rebooting accomplishes nothing except temporarily clearing the log. Signal problems that reappear within hours of a reboot are line problems, not software problems.