At what point does a company just look at costs to fix this issue rather then move to a solution that is working. I personally have been dealing with a celluar issue since "May 9th 2016" almost a year later with no resolve and have this internet issue as well.
The amount of money and time invested in this is mind boggling that it happens and is allowed. Want to know why we pay so much is because of the money and resources wasted trying to fix something that should have never been released to the public.
This is the classic case of trying to be the "first kid on the block" to have the fastest speeds or the newest hardware but in the end its the customer that has to beta test and accept sub par services.
@Telek Does your Modem have a Black Dot near the power cord on the back? also can you login to the modem and post the signal levels from the "DOCSIS WAN" Page. Lastly any idea what firmware version you are running?
I appreciate the request, however I've been around the block on this one.
I've had nothing but instability ever since it was installed. I've replaced the modem 3 times, and it's always the same.
When I first had the service installed a few weeks ago, the first modem (which was black-dot) was garbage. Completely erratic speeds all over the place, frequently completely dropped out. I replaced the modem, and it was better, for a day or two. First speed test on the new modem had 940/52 speed and I was thrilled!
The the other problems started.
Within about an hour or two, the speed drops down to ~240/20-50. Within about 12 hours after that, it drops down to less than 1mbit down, but will stay at 20-50 mbit upstream. Neither I nor tech support can even complete a speed test, and the only remedy is to reboot. Once I left it for 2 days like this, and it never recovered.
It doesn't matter if I'm hardwired or wireless. Doesn't matter if bridged or gateway mode. In gateway I have all wifi turned off anyway, as I have my own AC3200U access point.
I've spent more than 12 hours in total now on tech support calls through various levels of support agents. I'm infuriated that the tickets get closed within 12-24hr with "problem resolved", even though the problem clearly still exists even at the moment when the ticket is closed. There are enough people online complaining about the Rogers Docsis 3.1 rollout that there is obviously a systemic problem. Closing my tickets with "problem resolved" is a massive insult. This is what is frustrating me the most.
I'm highly technical and am understanding that this is "bleeding edge", but having to reboot the modem twice a day, combined with network support closing my tickets, is driving me up the wall.
Note that none of the modems have had a black dot by the power cord, but they all have the black dot on the box that the modem came in. I was told by tech support that this is the same thing.
My signal quality is amazing, and I don't ever notice missing channels:
|Port ID||Frequency (MHz)||Modulation||Signal strength (dBmV)||Channel ID||Signal noise ratio (dB)|
OFDM Downstream Overview
|Receiver||FFT type||Subcarr 0 Frequency(MHz)||PLC locked||NCP locked||MDC1 locked||PLC power(dBmv)|
|Port ID||Frequency (MHz)||Modulation||Signal strength (dBmV)||Channel ID||Bandwidth|
|1||38595531||ATDMA - 64QAM||38.750||6||3200000|
|2||30596000||ATDMA - 64QAM||35.000||4||6400000|
|3||23700000||ATDMA - 64QAM||35.000||5||6400000|
i,m having the same issue as you on coda modem with black sticker .23 with MDD timeouts
1 591000000 256QAM 6.300 7 40.366
2 567000000 256QAM 6.300 3 40.366
3 573000000 256QAM 5.900 4 38.983
4 579000000 256QAM 6.000 5 38.983
5 585000000 256QAM 6.400 6 40.366
6 561000000 256QAM 6.500 2 40.366
7 597000000 256QAM 6.300 8 38.983
8 603000000 256QAM 6.600 9 40.366
9 609000000 256QAM 6.800 10 38.983
10 615000000 256QAM 6.900 11 38.983
11 621000000 256QAM 7.100 12 40.366
12 633000000 256QAM 6.800 13 40.366
13 639000000 256QAM 7.100 14 38.983
14 645000000 256QAM 7.200 15 38.983
15 651000000 256QAM 7.200 16 38.983
16 657000000 256QAM 7.200 17 40.366
17 663000000 256QAM 6.900 18 38.605
18 669000000 256QAM 7.400 19 38.983
19 675000000 256QAM 7.200 20 38.983
20 681000000 256QAM 6.700 21 38.605
21 687000000 256QAM 6.500 22 38.983
22 693000000 256QAM 6.200 23 38.983
23 699000000 256QAM 6.300 24 38.605
24 705000000 256QAM 6.300 25 38.605
25 711000000 256QAM 5.900 26 38.605
26 717000000 256QAM 5.800 27 38.605
27 723000000 256QAM 5.800 28 38.983
28 825000000 256QAM 5.200 29 37.636
29 831000000 256QAM 4.900 30 37.356
30 837000000 256QAM 4.600 31 37.356
31 843000000 256QAM 5.000 32 37.356
32 555000000 256QAM 6.700 1 38.983
OFDM Downstream Overview
Receiver FFT type Subcarr 0 Frequency(MHz) PLC locked NCP locked MDC1 locked PLC power(dBmv)
0 4K 275600000 YES YES YES 3.700001
1 NA NA NO NO NO NA
Port ID Frequency (MHz) Modulation Signal strength (dBmV) Channel ID Bandwidth
1 30596000 ATDMA - 64QAM 34.250 1 6400000
2 38595824 ATDMA - 64QAM 38.000 3 3200000
3 23700000 ATDMA - 64QAM 33.500 2 6400000
Channel Index State lin Digital Att Digital Att BW (sc's*fft) Report Power Report Power1_6 FFT Size
0 DISABLED 0.5000 0.0000 0.0000 -inf -1.0000 4K
1 DISABLED 0.5000 0.0000 0.0000 -inf -1.0000 4K
As I mentioned earlier this week, Intel is working with Hitron and CASA to resolve the slowly degrading speed issue. They have made some headway and provided me a new firmware today.
Now, I must warn all of you this is completely fresh off the press and this firmware did not undergo any internal testing yet.
This firmware is exactly the same as 22.214.171.124 with a change in some internal Intel settings. In fact, after I load this firmware, the GUI will still display version 126.96.36.199. If you are not experiencing this issue, there is no point in loading this firmware yet.
If anybody wants to receive this firmware (maximum 5 participants today while we perform some testing), please reply below. You must already be a firmware trial program participant. Otherwise, I won’t be able to upgrade your modem.
Reigning heavyweight world champion Deontay "The Bronze Bomber'' Wilder takes on his most dangerous challenger as he defends his WBC title in a rematch against once-beaten Cuban slugger Luis "King Kong'' Ortiz.