Slow as hell
 

Meant to be on 100mb. Upload seems to struggle to even work on speed test.

My phone is also slow and my partners

In the B21 area.

What router stats do I need to post as I cant complete a speed test. Constantly failing on the upload part.

---------- Post added at 20:34 ---------- Previous post was at 20:21 ----------

Been told its high utilisation in my area and Virgin have no idea when it will be fixed but it could be a while.

---------- Post added at 20:36 ---------- Previous post was at 20:34 ----------

https://www.cableforum.co.uk/images/local/2012/07/1.png

---------- Post added at 20:50 ---------- Previous post was at 20:36 ----------

Now been told it will be fixed by 21st August

Re: Slow as hell
 

No way that is a utilisation problem dude. It is either a network fault or your power levels are seriously screwed. Can you post them please. If you have got a vmng300 go to 192.168.100.1 and copy the stuff from the downstream, upstream and config tabs. If you are using the shub go to the same address if in modem mode (I don't know what tabs it is all under) or if in router mode go to 12.168.0.1. I can't wait to see them because I am very curious. I am going to put my money on upstream power being too high.

Re: Slow as hell
 

Is this right?


Downstream Channels Lock Status Channel ID Frequency Modulation Rx Power SNR Pre RS Errors Post RS Errors
Locked 47 315000000 Hz QAM256 -0.4 dBmV 37.8 dB 385 0
Locked 45 299000000 Hz QAM256 -0.2 dBmV 38.4 dB 327 0
Locked 46 307000000 Hz QAM256 -0.3 dBmV 38.3 dB 355 0
Locked 48 323000000 Hz QAM256 -0.5 dBmV 37.8 dB 352 0
Unlocked Unknown 0 Hz Unknown 0.0 dBmV 0.0 dB Unknown Unknown
Unlocked Unknown 0 Hz Unknown 0.0 dBmV 0.0 dB Unknown Unknown
Unlocked Unknown 0 Hz Unknown 0.0 dBmV 0.0 dB Unknown Unknown
Unlocked Unknown 0 Hz Unknown 0.0 dBmV 0.0 dB Unknown Unknown
Upstream Channels Lock Status Channel ID Frequency Modulation Tx Power Mode Channel Bandwidth Symbol Rate
Locked 6 35800000 Hz ATDMA 37.3 dBmV 16QAM 6400000 20480 Kbits/sec
Unlocked 0 0 Hz Unknown 0.0 dBmV Unknown Unknown 0 Kbits/sec
Unlocked 0 0 Hz Unknown 0.0 dBmV Unknown Unknown 0 Kbits/sec
Unlocked 0 0 Hz Unknown 0.0 dBmV Unknown Unknown 0 Kbits/sec

Re: Slow as hell
 

ya, downstream power is virtually perfect but your upstream is borderline low. Do you know how far away from the cabinet you are?

Re: Slow as hell
 

50 foot maybe 75 at a guess.

Re: Slow as hell
 

thats fine!!

Re: Slow as hell
 

that's ok then. What do the error logs in the shub show. Have you got any T3 timeouts - no ranging response received messages?

Re: Slow as hell
 

01/08/2012 04:03:18 82000500 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Mod Edit - MAC removed;CMTS-MAC=00:30:b8:cf:0a:b1;CM-QOS=1.1;CM-VER=3.0;
01/08/2012 02:28:10 66060300 Map Request Retry Timeout;[Mod Edit - MAC removed;CMTS-MAC=00:30:b8:cf:0a:b1;CM-QOS=1.1;CM-VER=3.0;
31/07/2012 19:24:37 73000200 REG RSP not received;[Mod Edit - MAC removed;CMTS-MAC=00:30:b8:cf:0a:b1;CM-QOS=1.1;CM-VER=3.0;
31/07/2012 19:24:34 2436694078 TOD established
31/07/2012 12:30:43 2436694077 TOD server unavailable
31/07/2012 12:30:43 2436694080 TOD resynchronisation failure
31/07/2012 12:30:42 68000200 DHCP FAILED - Request sent, No response;[Mod Edit - MAC removed;CMTS-MAC=00:30:b8:cf:0a:b1;CM-QOS=1.0;CM-VER=3.0;
31/07/2012 12:30:30 82000200 No Ranging Response received - T3 time-out;[Mod Edit - MAC removed;CMTS-MAC=00:30:b8:cf:0a:b1;CM-QOS=1.0;CM-VER=3.0;
31/07/2012 12:30:21 2436694074 CMTS DCC 315000000 MHz

Re: Slow as hell
 

bummer, it is a network fault dude and you'll have to wait for them to fix it. (nice to see the mods are up nice and early :) )

Re: Slow as hell
 

Typical. Its a shame they will not release me from my contract. I have had so many issues with my phone to :(

Re: Slow as hell
 

This is just my understanding of contractual law regarding VM contracts and faults, and its aimed at Centrals above post and nothing else.

It depends on how long the fault is ongoing, and how many times you've raised the issue with them. You have to give them a "reasonable" time, after reporting an issue in which to correct the issues.

If they fail to make repairs within a reasonable timeframe after you reporting it, then they are in breach of contract, and the contract is null and void.

The problem is, the front-line staff are probably unaware of that, and what is classed as a reasonable timeframe is up for argument, and they can always deny that you ever reported it.