site Search:


 
    All Forums Hot Topics Gallery






how-to block ads


 
Search Topic:
Uniqs:
595
Share Topic
Posting?
Post a:
Post a:
Links: ·Forum Rules ·Forum FAQ ·Bandwidth Limits/Congestion Management ·Copyright Infringement?
AuthorAll Replies

CodyH

join:2011-10-22
Memphis, TN

Comcast Internet Spikes (Again)

Here is the log from my modem

1970-01-01 00:00:21 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:10 3-Critical R002.0 No Ranging Response received - T3 time-out
1970-01-01 00:00:15 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
2012-04-12 07:26:10 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout
2012-04-12 07:25:38 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:00:16 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
2012-04-12 06:54:46 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout
2012-04-12 06:54:13 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2012-04-12 00:33:39 3-Critical T004.0 SYNC Timing Synchronization failure - Failed to receive MAC SYNC frame within time-out period
2012-04-11 08:29:03 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2012-04-10 23:47:42 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2012-04-10 07:58:42 3-Critical T004.0 SYNC Timing Synchronization failure - Failed to receive MAC SYNC frame within time-out period
2012-04-08 19:12:24 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2012-04-07 22:49:10 3-Critical T004.0 SYNC Timing Synchronization failure - Failed to receive MAC SYNC frame within time-out period
2012-04-05 13:19:43 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2012-03-30 22:14:40 3-Critical T004.0 SYNC Timing Synchronization failure - Failed to receive MAC SYNC frame within time-out period
2012-03-28 16:31:28 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:00:16 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:46 3-Critical D002.0 DHCP FAILED - Request sent, No response
1970-01-01 00:00:27 3-Critical D001.0 DHCP FAILED - Discover sent, no offer received
1970-01-01 00:04:48 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout
1970-01-01 00:04:47 3-Critical D002.0 DHCP FAILED - Request sent, No response
1970-01-01 00:01:50 3-Critical D001.0 DHCP FAILED - Discover sent, no offer received
1970-01-01 00:01:24 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:01:22 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:01:21 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:01:21 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:01:21 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:01:17 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:01:17 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:01:17 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:01:16 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:01:15 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:01:14 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:01:12 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:01:12 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:01:08 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:01:07 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:01:05 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:01:05 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:55 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:55 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:44 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:43 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:35 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:35 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:34 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:33 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:18 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:17 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:03 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2012-02-24 10:37:23 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout
2012-02-24 10:37:23 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:29 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:29 3-Critical D002.0 DHCP FAILED - Request sent, No response
1970-01-01 00:00:18 3-Critical D001.0 DHCP FAILED - Discover sent, no offer received
1970-01-01 00:07:35 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout
1970-01-01 00:07:33 3-Critical D002.0 DHCP FAILED - Request sent, No response
1970-01-01 00:05:24 3-Critical D001.0 DHCP FAILED - Discover sent, no offer received
1970-01-01 00:04:18 3-Critical R002.0 No Ranging Response received - T3 time-out
1970-01-01 00:04:12 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:04:11 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:04:11 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:04:05 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:04:04 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:04:00 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:03:59 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:03:56 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:03:55 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:03:52 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:03:52 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:03:42 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:03:42 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:02:36 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:02:36 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:02:36 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:02:36 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:02:34 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:02:34 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:02:32 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:02:32 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:02:32 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:02:32 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:02:32 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:02:31 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:02:31 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:02:30 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:02:29 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:02:29 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:02:29 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:02:28 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:02:28 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:02:28 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:02:28 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:02:28 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:02:27 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:02:27 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:02:23 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:02:23 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:02:22 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing

Modem Signal
Frequency 609000000 Hz Locked
Signal to Noise Ratio 37 dB
Power Level -2 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

I am no sure what is going on the cable started glitching out last night, and now the internet is spiking from good to painfully slow. PLEASE HELP!


gar187er
I do this for a living

join:2006-06-24
Dover, DE
kudos:4

how bout your upstream.....and also make/model modem? it looks like your modem is on the fritz as its not keeping time of day.....and resetting itself quite often...
--
I'm better than you!


CodyH

join:2011-10-22
Memphis, TN

Upstream
Channel ID 2
Frequency 36400000 Hz Ranged
Power Level 41 dBmV

and it is a Motorola Surfboard sb5100


medbuyer

join:2003-11-20
kudos:4

said by CodyH:

Upstream
Channel ID 2
Frequency 36400000 Hz Ranged
Power Level 41 dBmV

and it is a Motorola Surfboard sb5100

where in Memphis are you at? I'm in Bartlett.

Have you tried another modem?

Memphis area is already Docsis 3.0 capable and upgrading your modem to Moto SB6120 will help.

CodyH

join:2011-10-22
Memphis, TN

I am in Bartlett, East Hill area. Im not sure but does it cost extra to upgrade to that modem, I just got a call this morning saying they found a problem in my area and my tech appointment was canceled not sure if it is fixed yet, i just woke up :P


CodyH

join:2011-10-22
Memphis, TN

Did some quick testing playing games, running speed test and such. Looks like everything is back to normal , the true test will be tonight. I also got an email stating that here was a power shortage or outage in my area and that it was causing the problems, guess i will find out :P


medbuyer

join:2003-11-20
kudos:4

reply to CodyH

said by CodyH:

I am in Bartlett, East Hill area. Im not sure but does it cost extra to upgrade to that modem, I just got a call this morning saying they found a problem in my area and my tech appointment was canceled not sure if it is fixed yet, i just woke up :P

I live near Ellis Rd. and have CC Biz 12/2 at home....

I think you can buy your own modem at Best Buy and use it instead or renting from them. Just make sure it's new, legit and not from ebay or some shady craigslist seller.

I guess you're on a different node or something since I usually get notifications from them even though I didn't call to ask....perks of Biz customers...

CodyH

join:2011-10-22
Memphis, TN

I believe I just have regular home CC, i am not sure it is my Grandmothers hold house that i am renting and she had everything already placed. Everything seems to be working fine now, my speed test is a little low 14/3 usually it is up need 22/3 so im not sure what is causing that.


medbuyer

join:2003-11-20
kudos:4

I'd upgrade that modem to a D3 compatible one like the SB6120. What you're using is still D2, an older technology.


Tuesday, 21-May 09:57:30 Terms of Use & Privacy | feedback | contact | Hosting by nac.net - DSL,Hosting & Co-lo
over 13.5 years online © 1999-2013 dslreports.com.
Most commented news this week
Hot Topics