Menu
Reply
  • 19
  • 0
  • 0
napalmdeath
Tuning in
531 Views
Message 1 of 21
Flag for a moderator

Constant disconnections, lag spikes and 20 kbps upload

Just like in the title. I've got a VM broadband since not even 2 months and it's performance is extremely pitiful. What I experience is:

- Almost every day the connections drops, usually after 8pm but also during the day. It stays like that for anything between 10 mins - few hours. Sometimes the router says there's nothing wrong, but none of the devices can connect and more often the whole router flashes like a christmas tree and in the settings it says ACCESS DENIED. Reboots and restoring default settings don't help.

- Lags and disconnects on Playstation Network. VERY annoying when playing online. I forwarded psn and games' ports but it still happening.

- Very low upload speeds. When I do a test connection on ps4 pro using 5ghz I have around 95Mbps download but very rarely anything higher than 1Mbps upload, usually it's something around 20-300kbps.

I know a fair share about routers and the Internet so please no reboot your router or maybe there's a channel interference tips please. The area is not congested and there are roughly 3 routers running on channel 1 in the area. 

What I experience is very annoying when playing competitively and I really hope someone can fix it as I rely on my connection quite a lot.

I had to post this message using my phone's hotspot as the internet is not working now either...

 

0 Kudos
Reply
  • 19.32K
  • 1.68K
  • 4.23K
Very Insightful Person
Very Insightful Person
511 Views
Message 2 of 21
Flag for a moderator

Re: Constant disconnections, lag spikes and 20 kbps upload

Would need to check the signal levels if could go to http://192.168.0.1 or if using modem mode http://192.168.100.1 clicking router status top right or bottom of page depending on hub [no need to login - depending on hub] and if could copy/paste the downstream, upstream, network log, don't worry about the formatting we can easily read it.. try and avoid using screen shots..

if you do a direct connection is this more stable/faster?

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

Click to learn more about VIP

Use Kudos to say thanks

 

Mark as Helpful Answer if I've helped

  • 19
  • 0
  • 0
napalmdeath
Tuning in
510 Views
Message 3 of 21
Flag for a moderator

Re: Constant disconnections, lag spikes and 20 kbps upload

Hi, thank you very much for your response. I still have to post using my phone's connection but at least I could log into the router. I don't think it would be different with Ethernet connection as most of the time when that happens the lights on the router are flashing red and green which indicate problems with connection before reaching the router and unfortunately I'm not able to check wired connection at the moment. Anyway, here's the data:

 

Downstream bonded channels

Channel

Frequency (Hz)

Power (dBmV)

SNR (dB)

Modulation

Channel ID

1

186750000

3.5

38

256 qam

7

2

194750000

3.7

38

256 qam

8

3

202750000

4

38

256 qam

9

4

210750000

4.5

38

256 qam

10

5

218750000

4.9

38

256 qam

11

6

226750000

5

38

256 qam

12

7

234750000

5

38

256 qam

13

8

242750000

4.5

38

256 qam

14

9

250750000

4

38

256 qam

15

10

258750000

3.5

38

256 qam

16

11

266750000

3.7

38

256 qam

17

12

274750000

4

38

256 qam

18

13

282750000

4.8

37

256 qam

19

14

290750000

5.5

38

256 qam

20

15

298750000

6

37

256 qam

21

16

306750000

6

38

256 qam

22

17

314750000

5

37

256 qam

23

18

322750000

4.1

37

256 qam

24

19

402750000

3.5

38

256 qam

25

20

410750000

4

37

256 qam

26

21

418750000

4.8

37

256 qam

27

22

426750000

5.4

37

256 qam

28

23

434750000

5.5

37

256 qam

29

24

442750000

5.5

38

256 qam

30




Downstream bonded channels

Channel

Locked Status

RxMER (dB)

Pre RS Errors

Post RS Errors

1

Locked

38.6

11

0

2

Locked

37.6

6

0

3

Locked

37.6

8

0

4

Locked

38.6

9

0

5

Locked

38.6

15

0

6

Locked

38.6

10

0

7

Locked

38.9

7

0

8

Locked

38.6

8

0

9

Locked

38.2

11

0

10

Locked

38.2

7

0

11

Locked

38.9

5

0

12

Locked

38.6

11

0

13

Locked

37.6

9

0

14

Locked

37.6

4

0

15

Locked

38.6

10

0

16

Locked

37.6

13

0

17

Locked

38.2

9

0

18

Locked

37.6

5

0

19

Locked

37.6

11

0

20

Locked

37.6

3

0

21

Locked

37.6

11

0

22

Locked

37.6

10

0

23

Locked

37.6

6

0

24

Locked

38.6

4

0

 

 
      

 

Upstream bonded channels

Channel

Frequency (Hz)

Power (dBmV)

Symbol Rate (ksps)

Modulation

Channel ID

1

25799077

5.2

5120

16 qam

4




Upstream bonded channels

Channel

Channel Type

T1 Timeouts

T2 Timeouts

T3 Timeouts

T4 Timeouts

1

ATDMA

0

0

0

0

 

Network Log

Time

Priority

Description

01/07/2019 23:40:58

critical

No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

01/07/2019 23:40:59

critical

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

01/07/2019 23:40:59

critical

No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

01/07/2019 23:41:0

critical

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

01/07/2019 23:41:0

critical

No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

01/07/2019 23:41:1

critical

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

01/07/2019 23:41:2

critical

No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

01/07/2019 23:41:2

critical

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

01/07/2019 23:41:2

critical

No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

01/07/2019 23:41:2

critical

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

01/07/2019 23:41:3

critical

No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

01/07/2019 23:41:4

critical

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

01/07/2019 23:41:4

critical

No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

01/07/2019 23:41:4

critical

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

01/07/2019 23:41:5

critical

No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

01/07/2019 23:41:5

critical

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

01/07/2019 23:41:5

critical

No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

01/07/2019 23:41:6

critical

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

01/07/2019 23:41:7

critical

No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

01/07/2019 23:41:7

critical

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

 

 
    

 

0 Kudos
Reply
  • 19
  • 0
  • 0
napalmdeath
Tuning in
507 Views
Message 4 of 21
Flag for a moderator

Re: Constant disconnections, lag spikes and 20 kbps upload

I guess it'll be more helpful when I post the levels tomorrow IF my internet will work then

0 Kudos
Reply
  • 19.32K
  • 1.68K
  • 4.23K
Very Insightful Person
Very Insightful Person
504 Views
Message 5 of 21
Flag for a moderator

Re: Constant disconnections, lag spikes and 20 kbps upload

strange only having 1 upstream channel, and is showing rather on the high side, would make sure all coax (white) cable are finger tight,

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

Click to learn more about VIP

Use Kudos to say thanks

 

Mark as Helpful Answer if I've helped

  • 19
  • 0
  • 0
napalmdeath
Tuning in
502 Views
Message 6 of 21
Flag for a moderator

Re: Constant disconnections, lag spikes and 20 kbps upload

I've checked the indoor cable very carefully already and it seems very firm and all connections seem tight 

0 Kudos
Reply
  • 4.7K
  • 319
  • 790
Roger_Gooner
Superstar
493 Views
Message 7 of 21
Flag for a moderator

Re: Constant disconnections, lag spikes and 20 kbps upload

You need a technician to come round as there are far too many upstream problems.

--
Hub 3.0, TP-Link Archer C8, TP-Link TL-SG1008D 8-port gigabit switch, V6
My Broadband Ping - Roger's VM Broadband Connection
  • 19
  • 0
  • 0
napalmdeath
Tuning in
491 Views
Message 8 of 21
Flag for a moderator

Re: Constant disconnections, lag spikes and 20 kbps upload

Now the Internet is listed as online on the router home screen but pages load very slow or not at all

the data looks like that:

Downstream bonded channelsChannel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
14027500003.537256 qam25
2186750000438256 qam7
31947500004.138256 qam8
42027500004.438256 qam9
52107500004.538256 qam10
62187500004.938256 qam11
7226750000538256 qam12
82347500005.138256 qam13
92427500004.838256 qam14
102507500004.338256 qam15
112587500003.738256 qam16
122667500004.138256 qam17
132747500004.538256 qam18
142827500005.138256 qam19
152907500005.638256 qam20
162987500006.137256 qam21
17306750000638256 qam22
183147500005.137256 qam23
193227500004.437256 qam24
204107500004.337256 qam26
21418750000537256 qam27
224267500005.637256 qam28
234347500005.837256 qam29
244427500005.638256 qam30


Downstream bonded channelsChannel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1Locked37.61310
2Locked38.672293
3Locked38.61016104
4Locked38.9731208
5Locked38.6404290
6Locked38.6192280
7Locked38.9208217
8Locked38.61690
9Locked38.61710
10Locked38.62280
11Locked38.63140
12Locked38.934311
13Locked38.634135
14Locked38.237535
15Locked38.632940
16Locked37.6259114
17Locked38.624029
18Locked37.61930
19Locked37.61830
20Locked37.62150
21Locked37.62770
22Locked37.32890
23Locked37.617543
24Locked38.610890

 

Upstream bonded channelsChannel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1462004315.2512016 qam1
2257995575.2512016 qam4
3325997415.2512016 qam3
4394004355.2512016 qam2


Upstream bonded channelsChannel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1ATDMA0000
2ATDMA0000
3ATDMA0000
4ATDMA0000

 

0 Kudos
Reply
  • 19
  • 0
  • 0
napalmdeath
Tuning in
491 Views
Message 9 of 21
Flag for a moderator

Re: Constant disconnections, lag spikes and 20 kbps upload

Network LogTime Priority Description
02/07/2019 00:07:42criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/07/2019 00:07:43criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/07/2019 00:07:43criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/07/2019 00:07:44criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/07/2019 00:07:44criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/07/2019 00:07:45criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/07/2019 00:07:45criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/07/2019 00:07:46criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/07/2019 00:07:47criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/07/2019 00:07:47criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/07/2019 00:07:48criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/07/2019 00:07:49criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/07/2019 00:08:42noticeReceived REG-RSP while in REG-HOLD1 state;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/07/2019 00:08:55criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/07/2019 00:10:8criticalRanging Request Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/07/2019 00:10:8criticalUnicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/01/1970 00:01:42criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/07/2019 00:17:45criticalRanging Request Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/07/2019 00:17:45criticalUnicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/07/2019 00:18:9criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
0 Kudos
Reply
  • 607
  • 94
  • 312
Very Insightful Person
Very Insightful Person
397 Views
Message 10 of 21
Flag for a moderator

Re: Constant disconnections, lag spikes and 20 kbps upload

On the face of it, your downstream stats don’t look too bad, a few more errors than I would like to see, but nothing too out of the ordinary. Your upstream figures are hopeless though - the power levels on all four are right at the maximum value, they are all connecting at only 16 qam (that just might be normal for your area but most places are on 64 qam now), and this is all indicative of ingress noise (interference) at lower frequencies (the errors are also concentrated at the lower frequency ranges). The logs back this up, as does the sudden disappearance of three of the upstream channels in your earlier post.

So what to do? The main cause of this is a bad connection between the hub and the street cabinet, you’ve checked the connection to the back of the hub is all nice and tight, you might try checking the connection to the wall socket (if not done already) and if you can get to it easily, the connections in the omnibox on your outside wall where the cable comes in. It can’t harm to check and tighten these if necessary but I really can’t see it helping too much. You need a technician visit to check the signal levels at various points back to the cabinet and adjust as necessary, with call CS and go through the ‘switch it on and off again saga but you really need to dig in and request a visit, or hold on for one of the forum team to find this thread (can take a day or so though) and they will offer to get in touch directly and arrange things - judging by the state of the connection stats above, I don’t think there’ll be any argument about the need for a visit.

John