Menu
Reply
Kolima
  • 30
  • 0
  • 0
Tuning in
982 Views
Message 1 of 17
Flag for a moderator

Valorant has become unplayable between Jitter and package loss

Hello all,
I've played Valorant for quite a while on the same connection (virgin 200mbs broadband package), same conditions (ethernet over powerline adapter ). But since a week has become unplayable with random ping spike, a super irregular connection rubber ( banding between 20mbps and 120mbps ) and package loss. Run all the possibile diagnostic on the page which keeps saying there is no issue, but this is the result of the trace route (as suggested https://support-valorant.riotgames.com/hc/en-us/articles/360047225674-How-to-Use-Tracert-to-Obtain-N... ) against their server and I think it speaks for itself. What I need to do? Because customer support seems to do not be able to help and I'm getting really frustrated and not sure what to do anymore.

 

Tracing route to 162.249.72.1 over a maximum of 30 hops

  1     4 ms     4 ms     3 ms  192.168.0.1 
  2     *        *        *     Request timed out.
  3    22 ms    11 ms    14 ms  nott-core-2a-xe-913-0.network.virginmedia.net [62.255.229.33] 
  4     *        *        *     Request timed out.
  5     *        *        *     Request timed out.
  6     *        *        *     Request timed out.
  7    24 ms    30 ms    46 ms  86.85-254-62.static.virginmediabusiness.co.uk [62.254.85.86] 
  8     *        *        *     Request timed out.
  9    27 ms    23 ms    31 ms  uk-lon01c-ri2-ae-4-0.aorta.net [84.116.135.50] 
 10    26 ms    24 ms    22 ms  uk-lon01a-rd3-s-4-1.aorta.net [213.46.174.161] 
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.

Trace complete.

 

I've also set up the broadband monitor https://www.thinkbroadband.com/broadband/monitoring/quality/view/724700d04556b1001f9d11ed24308401788...

0 Kudos
Reply
Adduxi
  • 6.08K
  • 511
  • 1.57K
Very Insightful Person
Very Insightful Person
952 Views
Message 2 of 17
Flag for a moderator

Re: Valorant has become unplayable between Jitter and package loss

Your BQM is not working, you need to use the shared link. Trace route is working as expected with a maximum of 46ms, which is good. 

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

0 Kudos
Reply
Kolima
  • 30
  • 0
  • 0
Tuning in
932 Views
Message 3 of 17
Flag for a moderator

Re: Valorant has become unplayable between Jitter and package loss

Hey, sorry I thought I already used the sharing link https://www.thinkbroadband.com/broadband/monitoring/quality/share/46da60212a7aefd130b559f88231ded70d...

The 46ms is acceptable, but Accordingly to valorant docs those timeout sign issues with the ISP
0 Kudos
Reply
Adduxi
  • 6.08K
  • 511
  • 1.57K
Very Insightful Person
Very Insightful Person
923 Views
Message 4 of 17
Flag for a moderator

Re: Valorant has become unplayable between Jitter and package loss

Wrong , it’s quite normal for non responses in Tracert.

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

0 Kudos
Reply
Kolima
  • 30
  • 0
  • 0
Tuning in
916 Views
Message 5 of 17
Flag for a moderator

Re: Valorant has become unplayable between Jitter and package loss

Maybe it is, im not sure who's fault it is, I'm only sure that there is something wrong.

0 Kudos
Reply
Adduxi
  • 6.08K
  • 511
  • 1.57K
Very Insightful Person
Very Insightful Person
859 Views
Message 6 of 17
Flag for a moderator

Re: Valorant has become unplayable between Jitter and package loss

Your BQM is not great, and shows a bit of over utilisation in the evenings.

Post your power levels, Pre and PostRS errors and Network log from your Hub.  Do not use screenshots, just copy and paste.  Thanks.

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

0 Kudos
Reply
Kolima
  • 30
  • 0
  • 0
Tuning in
855 Views
Message 7 of 17
Flag for a moderator

Re: Valorant has become unplayable between Jitter and package loss

Thanks, how would you obtain those info from the hub so that I can post them?

0 Kudos
Reply
Adduxi
  • 6.08K
  • 511
  • 1.57K
Very Insightful Person
Very Insightful Person
848 Views
Message 8 of 17
Flag for a moderator

Re: Valorant has become unplayable between Jitter and package loss

Use your Browser. go to 192.168.0.1 and click on Router Status.  This should bring up a page with all the relevant tabs. 

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

0 Kudos
Reply
Kolima
  • 30
  • 0
  • 0
Tuning in
837 Views
Message 9 of 17
Flag for a moderator

Re: Valorant has become unplayable between Jitter and package loss

Network log:

11/12/2021 18:52:0	notice	LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/01/1970 00:01:37	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/12/2021 19:20:31	notice	LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/12/2021 19:19:30	Warning!	LAN login FAILED : Incorrect Username / Password / ConnectionType;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/01/1970 00:01:37	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
04/12/2021 21:54:20	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
03/12/2021 10:27:25	Warning!	RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/01/1970 00:01:37	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/12/2021 13:11:16	Warning!	RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/12/2021 01:34:28	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/11/2021 09:15:43	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/11/2021 09:05:14	critical	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/11/2021 09:03:10	Warning!	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/11/2021 09:03:5	Warning!	RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/11/2021 09:03:5	critical	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/11/2021 09:03:5	Warning!	RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/11/2021 09:03:4	critical	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/11/2021 09:03:4	Warning!	RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
22/11/2021 22:19:20	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
22/11/2021 17:22:52	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;


Pre/Post RS/power level downstream

Downstream bonded channels
Channel	Frequency (Hz)	Power (dBmV)	SNR (dB)	Modulation	Channel ID
1	235000000	6.8	38	256 qam	13
2	243000000	6.8	38	256 qam	14
3	251000000	7	40	256 qam	15
4	259000000	7	40	256 qam	16
5	267000000	7	38	256 qam	17
6	275000000	7.4	40	256 qam	18
7	283000000	7.4	40	256 qam	19
8	291000000	7.8	40	256 qam	20
9	299000000	8.4	40	256 qam	21
10	307000000	8.1	40	256 qam	22
11	315000000	8.6	40	256 qam	23
12	323000000	9	40	256 qam	24
13	331000000	9	40	256 qam	25
14	339000000	9.9	40	256 qam	26
15	347000000	9.3	40	256 qam	27
16	355000000	8.5	40	256 qam	28
17	363000000	8.6	40	256 qam	29
18	371000000	8.4	40	256 qam	30
19	379000000	8.3	40	256 qam	31
20	387000000	8.5	40	256 qam	32
21	395000000	8.3	40	256 qam	33
22	403000000	8.1	40	256 qam	34
23	411000000	8.6	40	256 qam	35
24	419000000	8	40	256 qam	36


Downstream bonded channels
Channel	Locked Status	RxMER (dB)	Pre RS Errors	Post RS Errors
1	Locked	38.9	159	0
2	Locked	38.9	189	0
3	Locked	40.3	238	0
4	Locked	40.3	242	0
5	Locked	38.9	297	0
6	Locked	40.3	329	0
7	Locked	40.9	405	0
8	Locked	40.3	366	0
9	Locked	40.3	462	0
10	Locked	40.3	439	0
11	Locked	40.3	548	0
12	Locked	40.9	587	0
13	Locked	40.3	742	0
14	Locked	40.3	722	0
15	Locked	40.3	830	0
16	Locked	40.3	907	0
17	Locked	40.3	1028	0
18	Locked	40.9	1231	0
19	Locked	40.3	1440	0
20	Locked	40.3	1255	0
21	Locked	40.3	1729	0
22	Locked	40.9	1696	0
23	Locked	40.3	1682	0
24	Locked	40.3	1777	0

  upstream

Upstream bonded channels
Channel	Frequency (Hz)	Power (dBmV)	Symbol Rate (ksps)	Modulation	Channel ID
1	60300000	44.3	5120	64 qam	1
2	53700000	43.5	5120	64 qam	2
3	46200000	43.3	5120	64 qam	3
4	39400000	43	5120	64 qam	4


Upstream bonded channels
Channel	Channel Type	T1 Timeouts	T2 Timeouts	T3 Timeouts	T4 Timeouts
1	ATDMA	0	0	1	0
2	ATDMA	0	0	1	0
3	ATDMA	0	0	0	0
4	ATDMA	0	0	0	0
0 Kudos
Reply
John_GS
  • 14.4K
  • 737
  • 1.34K
Forum Team
Forum Team
765 Views
Message 10 of 17
Flag for a moderator

Re: Valorant has become unplayable between Jitter and package loss

Hi @Kolima

Thanks for posting. Apologies for the broadband issues. I am unsure if it'll sort the gaming issue out but all your downstream channels are out of spec. This will need a tech to attend the property. I shall send you a PM now. 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

0 Kudos
Reply