cancel
Showing results for 
Search instead for 
Did you mean: 

Slow upload and packet loss

bengeo
Tuning in

Hi,

I have a Hub 3 in modem mode to a Linksys Mesh Router. All was working well until very recently.

Now getting very slow upload speeds:

speed.png

Also Thinkbroadband checker shows 100% dropped packets:

think.png

stat.pngstat-up.png

down.pngerrors.pnglog.png

I have restarted everything several times.

Thanks for any help,

Andy

 

 

11 REPLIES 11

Adduxi
Very Insightful Person
Very Insightful Person

Your Upstream should all be 64QAM so that needs fixed. As for the BQM you need to allow Respond to ping on the Router. 

I'm a Very Insightful Person, I'm here to share knowledge, I don't work for Virgin Media. Learn more

Have I helped? Click Mark as Helpful Answer or use Kudos to say thanks

Thanks for the info.

Hi bengeo,

Thanks for posting. Sorry to hear of the broadband issues. You were affected by a noise on the line issue. Fault reference is F009543083. The ticket is showing restored but is under monitoring from the field and networks team. 

How's the speeds been since posting?

Best.

John_GS
Forum Team


Need a helpful hand to show you how to make a payment? Check out our guide - How to pay my Virgin Media bill

Hi John,

The speeds seem to be back to normal now, but there are still some oddities.

The Hub 3 is in modem mode and I can only access it via 192.168.100.1 just after it has been restarted. At any other time it says "The connection has timed out". Also, when I first open a browser the first site has a delay before it loads and then it seems normal after that. I still have 1 upload channel at 32 qam.

Info:

Upstream bonded channels

Channel

Frequency (Hz)

Power (dBmV)

Symbol Rate (ksps)

Modulation

Channel ID

1

60300000

49

5120

64 qam

1

2

39400000

46.8

5120

64 qam

4

3

46200000

47.3

5120

32 qam

3

4

53700000

48.5

5120

64 qam

2

 

Upstream bonded channels

Channel

Channel Type

T1 Timeouts

T2 Timeouts

T3 Timeouts

T4 Timeouts

1

ATDMA

0

0

0

0

2

ATDMA

0

0

0

0

3

ATDMA

0

0

0

0

4

ATDMA

0

0

0

0

 

 

       

 

General Configuration

Network access

Allowed

Maximum Number of CPEs

1

Baseline Privacy

Enabled

DOCSIS Mode

Docsis30

Config file

cmreg-vmdg505-bbt062-b.cm

 

Primary Downstream Service Flow

SFID

23696

Max Traffic Rate

402500089

Max Traffic Burst

42600

Min Traffic Rate

0

 

Primary Upstream Service Flow

SFID

23695

Max Traffic Rate

38500089

Max Traffic Burst

42600

Min Traffic Rate

0

Max Concatenated Burst

42600

Scheduling Type

BestEffort

 

 

   

 

Thanks,

Andy

 



 

 

Hi @bengeo 

 

Thank you so much for updating us and I'm so sorry to hear that these drops and messages have been happening! 

 

I know it's been a few days since your last post and the network teams were still monitoring the closed outage so I just wanted to check how things were looking now? 

 

Thank you.

Hi Ash,

The speeds seem to be normal, but there are still some oddities.

The Hub 3 is in modem mode and I still can only access it via 192.168.100.1 just after it has been restarted. At any other time it says "The connection has timed out". Do I need a new hub?

In my last message I said that I had 1 upload channel at 32 qam. Now it is worse:

bengeo_0-1641204406510.png

Thanks,

Andy

 

Hi @bengeo thanks for getting back to us.

When you say "restarted" do you mean rebooting of your hub or a full pinhole reset?  As the pinhole reset essentially takes the hub back to factory settings, but clears most issues.

Regards

 

Lee_R

Hi Lee,

I haven't done a full pinhole reset yet. I am waiting until I have enough time to set everything up again as I will want it back in modem mode.

The status checker is still saying that there are problems.

I'll do that reset soon and report back.

Thanks,

Andy

 

 

Zak_M
Forum Team (Retired)
Forum Team (Retired)

Good morning Bengeo, 

 

Thank you for coming back to us,  I have just taken a further look over your account and I can see that there is an SNR issue in your area, the ETA for fix is today, however with SNR issue they are notoriously difficult to locate the problem area so I would expect this to be delayed somewhat. 

 

Kind regards,

Zak_M