angryviper
join:2002-07-11
Chicago, IL
1 edit | Is this normal?
Everytime I speak to a different rep, they tell me I either have the 4 MBPS or 6 MBPS package. Im paying 59.95 a month and here are my results.
1. Chicago, IL
2. Well the sales reps claim I have the 6 MBPS but when I run speed tests I get low 4ks.
3. The issue is consistent throughout the day. Another issue is high ping times during the evening hours.
4.
Moto SB1500
Software Version: SB5100-2.3.7.0-GA-00-NOSH
Hardware Version: 3
MIB Version: II
GUI Version: 1.0
VxWorks Version: 5.4
5. I have a router that I use, it is a DLink DI-524
6. Only have the windows firewall up and running.
I've had ping issues in the past, but speed issue is new.
--------------------------------------------------
Frequency 711000000 Hz Locked
Signal to Noise Ratio 39 dB
Power Level 7 dBmV
Upstream Value
Channel ID 7
Frequency 34400000 Hz Ranged
Power Level 34 dBmV
---------------------------------------------------
 |
|
angryviper
join:2002-07-11
Chicago, IL | Ive started a smoke ping page to track the ping times throughout the day.
»/r3/smokeping.···b2&r=166 |
|
nonymousa
@comcast.net | reply to angryviper
Hey there, mad snake. Post your modem signal levels. |
|
NormanS
Premium,MVM
join:2001-02-14
San Jose, CA
 ·Pacific Bell - SBC
| reply to angryviper
said by angryviper  :Everytime I speak to a different rep, they tell me I either have the 4 MBPS or 6 MBPS package. Im paying 59.95 a month ... Sounds like the unbundled product (HSI only, no TV or telephone). Used to be 4 Mbps for that package, not sure about now.
--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum |
|
angryviper
join:2002-07-11
Chicago, IL
| Downstream Value
Frequency 711000000 Hz Locked
Signal to Noise Ratio 37 dB
Power Level 8 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 7
Frequency 34400000 Hz Ranged
Power Level 34 dBmV |
|
andyross
join:2003-05-04
Schaumburg, IL
1 edit | Please post the HSI portion of your Comcast bill so we know how it's named.
Do you have cable TV from Comcast, or just HSI?
You may be able to see the config file used by your modem in it's logs. You may need to power-cycle the modem if it's entry has been dropped out due to the log length limit. |
|
angryviper
join:2002-07-11
Chicago, IL
| I only have the Internet, no cable tv.
2009-02-22 09:08:26 5-Warning B605.10 Map Reject - Downstream Traffic Flow Not Mapped to BPI+ SAID (EC=8)
2009-02-13 17:18:56 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2009-02-13 12:09:03 5-Warning B605.10 Map Reject - Downstream Traffic Flow Not Mapped to BPI+ SAID (EC=8)
1970-01-01 00:00:12 3-Critical R002.0 No Ranging Response received - T3 time-out
2009-01-05 11:48:42 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2009-01-05 11:48:29 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2009-01-05 11:48:27 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2009-01-05 11:48:27 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2009-01-05 11:48:26 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2009-01-05 11:48:26 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2009-01-05 11:48:24 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2009-01-05 11:48:24 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2009-01-05 11:48:23 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2009-01-05 11:48:23 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2009-01-05 11:48:21 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2009-01-05 11:48:20 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2009-01-05 11:48:20 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2009-01-05 11:48:19 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2009-01-05 11:48:18 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2009-01-05 11:48:17 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2009-01-05 11:48:17 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2009-01-05 11:48:17 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2009-01-05 11:48:16 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2009-01-05 11:48:16 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2009-01-05 11:48:16 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2009-01-05 11:48:15 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2009-01-05 11:48:15 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2009-01-05 11:48:14 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2009-01-05 11:48:14 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2009-01-05 11:48:13 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2009-01-05 11:48:13 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2009-01-05 11:48:13 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2009-01-05 11:48:12 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2009-01-05 11:48:12 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2009-01-05 11:48:12 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2009-01-05 11:48:11 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2009-01-05 11:48:10 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout
2009-01-05 11:48:10 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2009-01-03 10:19:41 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2008-12-15 14:39:38 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-12-15 14:39:37 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-12-15 14:39:37 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-12-15 14:39:36 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-12-15 14:39:36 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-12-15 14:39:35 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-12-15 14:39:35 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-12-15 14:39:35 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-12-15 14:39:34 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-12-15 14:39:34 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-12-15 14:39:34 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-12-15 14:39:26 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-12-15 14:39:26 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-12-15 14:39:25 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-12-15 14:39:25 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-12-15 14:39:23 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-12-15 14:39:23 3-Critical R001.0 No Maintenance Broadcasts for Ranging opportunities received - T2 time-out
2008-12-15 14:38:58 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-12-15 14:38:43 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-12-15 14:38:43 3-Critical R001.0 No Maintenance Broadcasts for Ranging opportunities received - T2 time-out
2008-12-15 14:38:21 3-Critical R002.0 No Ranging Response received - T3 time-out
2008-12-15 14:36:37 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout
2008-12-12 19:20:23 6-Notice E112.0 SW download Successful - Via Config file
2008-12-12 19:19:52 6-Notice E102.0 SW Download INIT - Via Config file d11_m_sb5100_standardtb25_c01.cm
1970-01-01 00:00:06 3-Critical R002.0 No Ranging Response received - T3 time-out
2008-12-10 19:38:49 6-Notice E102.0 SW Download INIT - Via Config file d11_m_sb5101_standardtb25_c01.cm
2008-11-13 15:49:35 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2008-10-29 02:02:40 4-Error E107.0 SW upgrade Failed after download - Incompatible SW file
2008-10-29 02:02:38 6-Notice E102.0 SW Download INIT - Via Config file d11_m_sb5101_standardtb25_c01.cm
1970-01-01 00:00:04 3-Critical R002.0 No Ranging Response received - T3 time-out
2008-10-20 22:32:52 4-Error E107.0 SW upgrade Failed after download - Incompatible SW file
2008-10-20 22:32:29 6-Notice E102.0 SW Download INIT - Via Config file d11_m_sb5101_standard_c01.cm
1970-01-01 00:00:12 4-Error D004.3 ToD request sent- No Response received
2008-10-17 19:55:34 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2008-10-08 00:15:23 5-Warning B605.10 Map Reject - Downstream Traffic Flow Not Mapped to BPI+ SAID (EC=8)
2008-10-02 07:04:35 4-Error E107.0 SW upgrade Failed after download - Incompatible SW file
2008-10-02 07:04:33 6-Notice E102.0 SW Download INIT - Via Config file d11_m_sb5101_standard_c01.cm
2008-10-02 07:04:07 6-Notice E111.0 SW download Successful - Via NMS
2008-10-02 07:03:17 6-Notice E101.0 SW Download INIT - Via NMS
2008-09-29 18:37:43 4-Error E107.0 SW upgrade Failed after download - Incompatible SW file
2008-09-29 18:37:41 6-Notice E102.0 SW Download INIT - Via Config file d11_m_sb5101_standard_c01.cm
1970-01-01 00:00:04 3-Critical R002.0 No Ranging Response received - T3 time-out
2008-09-20 07:10:29 6-Notice E102.0 SW Download INIT - Via Config file d11_m_sb5101_standard_c01.cm
1970-01-01 00:00:04 3-Critical R002.0 No Ranging Response received - T3 time-out
2008-09-19 17:45:15 6-Notice E102.0 SW Download INIT - Via Config file d11_m_sb5101_standard_c01.cm
2008-09-16 16:45:06 3-Critical R002.0 No Ranging Response received - T3 time-out
2008-09-16 16:42:51 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout
2008-09-16 16:42:19 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2008-08-28 06:55:49 4-Error C401.0 DCC-ACK not received
1970-01-01 00:20:18 3-Critical D002.0 DHCP FAILED - Request sent, No response
1970-01-01 00:15:12 3-Critical D001.0 DHCP FAILED - Discover sent, no offer received
1970-01-01 00:14:05 3-Critical R002.0 No Ranging Response received - T3 time-out
1970-01-01 00:14:03 3-Critical R001.0 No Maintenance Broadcasts for Ranging opportunities received - T2 time-out
1970-01-01 00:13:53 3-Critical R002.0 No Ranging Response received - T3 time-out
1970-01-01 00:13:39 3-Critical R001.0 No Maintenance Broadcasts for Ranging opportunities received - T2 time-out
1970-01-01 00:13:29 3-Critical R002.0 No Ranging Response received - T3 time-out
1970-01-01 00:13:10 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:13:07 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:13:02 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:13:01 3-Critical R001.0 No Maintenance Broadcasts for Ranging opportunities received - T2 time-out
1970-01-01 00:12:51 3-Critical R002.0 No Ranging Response received - T3 time-out |
|
angryviper
join:2002-07-11
Chicago, IL | CHSI Performance Lite - 59.95 |
|
R62006
join:2006-05-03
Jacksonville, FL | your plan is correct.
speedtest doesnt necesarilly reveal your true speed due to the POWERBOOST interupption.
your true speed of 6 megs plan= throttled to 3mbs sustained. |
|
NormanS
Premium,MVM
join:2001-02-14
San Jose, CA | Why do you keep spreading that FUD? |
|
