cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
879 Views
Message 1 of 5

FTTC Downstream stuck at 60,000kbps

Go to solution

Hi,

I had some issues with my Broadband several months ago that caused the line to drop after several days and retrain.  These issues were resolved and, other than a street wide power failure, the connection has been rock solid ever since.

The maximum downstream rate on the HG612 modem is reported as being 72,192kbps with a 7.3dB SNR, but yet the connection has remained stubbornly at 60,000kbps for the last 2 months.

Does this require a DLM reset to allow the connection speed to get closer to the maximum figure?  I've included the Line stats and results from the BT wholesale broadband checker below.

Line stats

Stats summary

Stats recorded 24 Sep 2021 20:26:59

DSLAM type / SW version:	BDCM:0xc190 (193.144) / v0xc190
Modem/router firmware:  	AnnexA version - A2pv6C038m.d24j
DSL mode:               	VDSL2 Profile 17a
Status:                 	Showtime
Uptime:                 	16 days 0 hour 5 min 21 sec
Resyncs:                	1 (since 19 Aug 2021 21:16:27)
			
				Downstream	Upstream
Line attenuation (dB):  	17.2		0.0
Signal attenuation (dB):	Not available on VDSL2		
Connection speed (kbps):	60000		20000
SNR margin (dB):        	7.3		7.3
Power (dBm):            	12.3		6.9
Interleave depth:       	16		1
INP:                    	48.00		0
G.INP:                  	Enabled		Not enabled
Vectoring status:       	5 (VECT_UNCONFIGURED)		

RSCorr/RS (%):          	0.0310		0.0000
RSUnCorr/RS (%):        	0.0000		0.0000
ES/hour:                	0		0.49

Connection stats

xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason:	1
Last initialization procedure status:	0
Max:	Upstream rate = 26220 Kbps, Downstream rate = 72192 Kbps
Bearer:	0, Upstream rate = 20000 Kbps, Downstream rate = 60000 Kbps
Bearer:	1, Upstream rate = 0 Kbps, Downstream rate = 0 Kbps
Link Power State:	L0
Mode:			VDSL2 Annex B
VDSL2 Profile:		Profile 17a
TPS-TC:			PTM Mode(0x0)
Trellis:		U:ON /D:ON
Line Status:		No Defect
Training Status:	Showtime
		Down		Up
SNR (dB):	 7.3		 7.3
Attn(dB):	 17.2		 0.0
Pwr(dBm):	 12.3		 6.9

 

Since Link time = 16 days 5 min 51 sec
FEC:		676337		0
CRC:		323		532
ES:		18		406
SES:		6		26
UAS:		0		0
LOS:		0		0
LOF:		0		0
LOM:		0		0

 

BT wholesale broadband checker

Broadband check 2.PNG

 

0 Ratings
4 REPLIES 4
869 Views
Message 2 of 5

Re: FTTC Downstream stuck at 60,000kbps

Go to solution

Due to all your previous connection problems you connection is now in a banded profile which should release automatically after 3 or 4 weeks of stable connection with no drops including power cuts. Currently looks like you only have 16 days just now. If still nothing in couple weeks post back and we can see if mods will help



If you like a post, or want to say thanks for a helpful answer, please click on the Ratings 'Thumbs up' on left hand side.
If someone answers your question correctly please let other members know by clicking on ’Mark as Accepted Solution’.
0 Ratings
818 Views
Message 3 of 5

Re: FTTC Downstream stuck at 60,000kbps

Go to solution

Hi @japage33,

Thank you for posting. The details @imjolly has posted is correct the connection should recover by itself in around 3-4 weeks as long as the connection remains stable.

If you send me in your details, might be able to help speed up the recovery. 

I have sent you a private message with instructions on how to contact the team.  You can access your messages via the envelope icon at the top right of the screen, or click on this link, Private messages

Thanks,

Paddy

 

0 Ratings
730 Views
Message 4 of 5

Re: FTTC Downstream stuck at 60,000kbps

Go to solution

Hi @japage33,

Thank you for taking my call today. I was happy to hear that your speeds have returned to normal.

Thanks,

Paddy

0 Ratings
709 Views
Message 5 of 5

Re: FTTC Downstream stuck at 60,000kbps

Go to solution

Hi Paddy,

Thanks for your help.  The downstream connection speed is back up to 72Mbps, a 20% improvement on where it was. Much better!!

Thanks,

James