SG Broadband Community

As of yesterday, my internet is intermittent. Also it cuts out when i have 2 comouters running and streaming video. I disconnected my splitter, which got me back onlone. And now without splitter all sudden this is going on. It has snowed here, and its melting (dont know if this has anything to do with it). About 3 months ago the cable company, came out and redug and placed new wiring from home to the drop (about 300 feet away)

Here are my signals........

Frequency 603000000 Hz
Signal to Noise Ratio 37 dB
Downstream Modulation QAM256
Network Access Control Object ON
Power Level 12 dBmV The Downstream Power Level reading is a snapshot taken at the time this page was requested. Please Reload/Refresh this Page for a new reading

Upstream Value
Channel ID 1
Frequency 32000000 Hz
Ranging Service ID 7433
Symbol Rate 5.120 Msym/s
Power Level 54 dBmV
Upstream Modulation [1] QPSK[3] 16QAM[2] 64QAM
Signal Stats Value
Total Unerrored Codewords -1997142449
Total Correctable Codewords 50
Total Uncorrectable Codewords 0











2009-03-05 21:55:34 4-Error S101.1 Service Add aborted - No RSP
2009-03-05 21:55:08 4-Error S101.1 Service Add aborted - No RSP
2009-03-05 21:52:38 4-Error S102.1 Service Change aborted - No RSP
2009-03-05 19:27:49 7-Information B401.0 Authorized
2009-03-05 19:25:11 7-Information B401.0 Authorized
1970-01-01 00:01:48 3-Critical R02.0 No Ranging Response received - T3 time-out
1970-01-01 00:01:43 3-Critical R02.0 No Ranging Response received - T3 time-out
1970-01-01 00:01:42 3-Critical R02.0 No Ranging Response received - T3 time-out
1970-01-01 00:01:40 3-Critical R02.0 No Ranging Response received - T3 time-out
1970-01-01 00:01:34 3-Critical R02.0 No Ranging Response received - T3 time-out
1970-01-01 00:01:30 3-Critical R02.0 No Ranging Response received - T3 time-out
1970-01-01 00:01:28 3-Critical R02.0 No Ranging Response received - T3 time-out
1970-01-01 00:01:28 3-Critical R02.0 No Ranging Response received - T3 time-out
1970-01-01 00:01:24 3-Critical R02.0 No Ranging Response received - T3 time-out
1970-01-01 00:01:22 3-Critical R02.0 No Ranging Response received - T3 time-out
1970-01-01 00:01:19 3-Critical R02.0 No Ranging Response received - T3 time-out
1970-01-01 00:01:17 3-Critical R02.0 No Ranging Response received - T3 time-out
1970-01-01 00:01:17 3-Critical R02.0 No Ranging Response received - T3 time-out
1970-01-01 00:01:11 3-Critical R02.0 No Ranging Response received - T3 time-out
1970-01-01 00:01:09 3-Critical R02.0 No Ranging Response received - T3 time-out
1970-01-01 00:01:04 3-Critical R02.0 No Ranging Response received - T3 time-out
1970-01-01 00:01:01 3-Critical R02.0 No Ranging Response received - T3 time-out
1970-01-01 00:00:56 3-Critical R02.0 No Ranging Response received - T3 time-out
1970-01-01 00:00:53 3-Critical R02.0 No Ranging Response received - T3 time-out
1970-01-01 00:00:52 3-Critical R02.0 No Ranging Response received - T3 time-out
1970-01-01 00:00:51 3-Critical R02.0 No Ranging Response received - T3 time-out
1970-01-01 00:00:51 3-Critical R02.0 No Ranging Response received - T3 time-out
1970-01-01 00:00:50 3-Critical R03.0 Ranging Request Retries exhausted
1970-01-01 00:00:49 3-Critical R02.0 No Ranging Response received - T3 time-out
1970-01-01 00:00:46 3-Critical R02.0 No Ranging Response received - T3 time-out
1970-01-01 00:00:45 3-Critical R02.0 No Ranging Response received - T3 time-out
1970-01-01 00:00:42 3-Critical R02.0 No Ranging Response received - T3 time-out
1970-01-01 00:00:40 3-Critical R02.0 No Ranging Response received - T3 time-out
1970-01-01 00:00:35 3-Critical R02.0 No Ranging Response received - T3 time-out
1970-01-01 00:00:30 3-Critical R02.0 No Ranging Response received - T3 time-out
1970-01-01 00:00:25 3-Critical R02.0 No Ranging Response received - T3 time-out
1970-01-01 00:00:24 3-Critical R02.0 No Ranging Response received - T3 time-out
1970-01-01 00:00:22 3-Critical R02.0 No Ranging Response receive

Have you called the ISP first yet? That would be my first move if both computers are having the same issue when directly connected to the modem.

yes, they are sending atech out today. Do those readings i posted look bad?

i am connected to netgear router, which i have never had any probs with

Upstream Power Level 54 dBmV

This is quite high, just barely lower than the maximum of 55. Probably it fluctuates, so could be causing problems:
http://www.speedguide.net/read_articles.php?id=1197

Anyone else see this as a problem?

PastTense wrote:Upstream Power Level 54 dBmV

This is quite high, just barely lower than the maximum of 55. Probably it fluctuates, so could be causing problems:
http://www.speedguide.net/read_articles.php?id=1197

Anyone else see this as a problem?

Yep. Upstream number is the level that the cable modem transmits back to the headend at. its adjusted by the headend on the fly to keep you at or about 0dBmV at the node.

Since they have it this high it means they are having some trouble hearing your modem. Their sides SNR may be fairly low and a little change in the weather could cause you some issues.

Modems are finiky and cheap products. One might have no problem transmitting at 55 all day long but another gets flaky over 53... YMMV.

My cable company here has specified to their techs that over 50 is a reason for concern.


Try pinging your isp gateway.

get it by tracert first. It will be the first hop outside your network.

then C:>ping -n 50 "Your Gateway IP" and post those back here...


By the way on your receive side +12dBmV means your modem hearing the node loud and clear... SNR 37, Im jealous...

Your transmit levels are to high, the recommendation is 50 or lower and the receive levels of 12 is to high, the recommendation is +7 to -10. You have a issue that can be anywhere from your modem giving a false reading, bad cabling, splitters, or the main plant itself. At your street, the transmit should be approximately 38 and you would take that number and add to it with each splitter, example, 4 way splitter will bring the transmit to 45. There isn't really a loss in the transmit on the cable itself unless the cable is bad.