Keep getting kicked from GTA Online (XBOX SERIES X)

[andy1027]

I keep getting kicked from GTA Online. Can play for about 5 minutes and then this message comes up. WiFi is always very good and I have never had any issues. Xbox WiFI and multiplayer tests all come back with very good results. Yet when trying to play GTA Online lately I keep getting the message "Connection to the session lost due to an unknown network error. Please return to Grand Theft Auto V and try again".

The Xbox itself never loses connection to my Super Hub 3 
We don't have any issues with the WiFi at present
Rockstar Service Status reports that all their servers are up just fine
Xbox says NAT type shows as open
Rebooted console

Any ideas? 

EDIT: Have included Router Status information incase there is something there that doesn't look right. 

Cable Modem Status
Item	Status	Comments
Acquired Downstream Channel (Hz)	323000000	Locked
Ranged Upstream Channel (Hz)	39400000	Locked
Provisioning State	Online

Downstream bonded channels

Channel	Frequency (Hz)	Power (dBmV)	SNR (dB)	Modulation	Channel ID
1	323000000	-2.7	38	256 qam	24
2	235000000	-2	38	256 qam	13
3	243000000	-2.4	40	256 qam	14
4	251000000	-2.2	40	256 qam	15
5	259000000	-2.2	40	256 qam	16
6	267000000	-2.2	40	256 qam	17
7	275000000	-2.4	38	256 qam	18
8	283000000	-2.2	38	256 qam	19
9	291000000	-2.4	40	256 qam	20
10	299000000	-2	40	256 qam	21
11	307000000	-2.4	40	256 qam	22
12	315000000	-2.7	38	256 qam	23
13	331000000	-2.7	38	256 qam	25
14	339000000	-3	38	256 qam	26
15	347000000	-3	38	256 qam	27
16	355000000	-3	38	256 qam	28
17	363000000	-3	38	256 qam	29
18	371000000	-2.7	38	256 qam	30
19	379000000	-2.7	38	256 qam	31
20	387000000	-3.2	39	256 qam	32
21	395000000	-3.4	38	256 qam	34
22	403000000	-3.5	38	256 qam	35
23	411000000	-3.4	38	256 qam	36
24	419000000	-3.5	38	256 qam	37

Downstream bonded channels

Channel	Locked Status	RxMER (dB)	Pre RS Errors	Post RS Errors
1	Locked	38.9	8994	0
2	Locked	38.9	7925	36
3	Locked	40.3	8308	24
4	Locked	40.3	7887	0
5	Locked	40.3	6495	0
6	Locked	40.3	5733	0
7	Locked	38.9	5557	13
8	Locked	38.9	5202	0
9	Locked	40.3	6116	52
10	Locked	40.3	6634	26
11	Locked	40.3	6658	0
12	Locked	38.9	8137	0
13	Locked	38.9	7312	0
14	Locked	38.9	7669	0
15	Locked	38.9	8355	0
16	Locked	38.9	10043	0
17	Locked	38.9	9353	0
18	Locked	38.9	9740	0
19	Locked	38.6	10815	0
20	Locked	39.8	10966	0
21	Locked	38.9	13477	0
22	Locked	38.9	12437	0
23	Locked	38.9	13124	0
24	Locked	38.6	13767	0

Upstream bonded channels

Channel	Frequency (Hz)	Power (dBmV)	Symbol Rate (ksps)	Modulation	Channel ID
1	39400000	47.5	5120	64 qam	10
2	46200000	47.5	5120	64 qam	9
3	32600000	47	5120	64 qam	11
4	25800000	46.8	5120	32 qam	12

Upstream bonded channels

Channel	Channel Type	T1 Timeouts	T2 Timeouts	T3 Timeouts	T4 Timeouts
1	ATDMA	0	0	4	0
2	ATDMA	0	0	8	0
3	ATDMA	0	0	2	0
4	ATDMA	0	0	4	0

General Configuration

Network access	Allowed
Maximum Number of CPEs	1
Baseline Privacy	Enabled
DOCSIS Mode	Docsis30
Config file	cmreg-vmdg505-bbt060-b.cm

Primary Downstream Service Flow

SFID	321332
Max Traffic Rate	230000061
Max Traffic Burst	42600
Min Traffic Rate	0

Primary Upstream Service Flow

SFID	321331
Max Traffic Rate	22000061
Max Traffic Burst	42600
Min Traffic Rate	0
Max Concatenated Burst	42600
Scheduling Type	BestEffort

[andy1027]

Unsure. Its really to address the Post RS errors that were occuring if you read back through the previous posts there had been plenty of them. 

I rebooted the HUB yesterday and haven't had any post RS errors since. However when I rebooted the hub in previous weeks in this thread, I had post RS errors before and after reboot. 

What would be the cause of that? 

Will keep an eye to see if there is a spike in post RS errors again. 

[Gareth_L]

Hi andy1027

Thanks for the update 

How have things been since Sunday 

We know its only been 1 day ,but just wanted to see how it is now 

Gareth_L

[andy1027]

Latest info. Looks like the post RS errors are back. Are these within range?:

Downstream bonded channels

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID

1	323000000	-2.4	38	256 qam	24
2	139000000	-0.2	38	256 qam	1
3	147000000	-0.2	40	256 qam	2
4	155000000	-0.4	40	256 qam	3
5	163000000	-0.5	40	256 qam	4
6	171000000	-0.5	40	256 qam	5
7	179000000	-0.7	40	256 qam	6
8	187000000	-0.7	40	256 qam	7
9	195000000	-1	40	256 qam	8
10	203000000	-1	40	256 qam	9
11	211000000	-1	40	256 qam	10
12	219000000	-1.4	40	256 qam	11
13	227000000	-1.5	38	256 qam	12
14	235000000	-1.7	38	256 qam	13
15	243000000	-1.9	40	256 qam	14
16	251000000	-1.7	40	256 qam	15
17	259000000	-1.7	40	256 qam	16
18	267000000	-1.7	40	256 qam	17
19	275000000	-1.7	38	256 qam	18
20	283000000	-1.7	40	256 qam	19
21	291000000	-1.7	40	256 qam	20
22	299000000	-1.7	38	256 qam	21
23	307000000	-2	40	256 qam	22
24	315000000	-2.2	38	256 qam	23

Downstream bonded channels

Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors

1	Locked	38.9	6209	0
2	Locked	38.9	1505451	15103
3	Locked	40.3	9175	50
4	Locked	40.9	5789	18
5	Locked	40.3	6539	16
6	Locked	40.3	5585	12
7	Locked	40.3	17467	823
8	Locked	40.3	7656	107
9	Locked	40.3	5348	1
10	Locked	40.3	4998	0
11	Locked	40.3	4893	0
12	Locked	40.3	4720	4
13	Locked	38.9	5073	0
14	Locked	38.9	5308	0
15	Locked	40.3	5730	0
16	Locked	40.3	5358	0
17	Locked	40.3	4534	0
18	Locked	40.3	4056	0
19	Locked	38.9	4055	0
20	Locked	40.3	3837	0
21	Locked	40.3	4668	0
22	Locked	38.9	4728	0
23	Locked	40.9	4817	0
24	Locked	38.9	6337	0

Upstream bonded channels

Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID

1	39400000	47	5120	64 qam	10
2	46200000	47	5120	64 qam	9
3	25800000	46	5120	64 qam	12
4	32600000	46.5	5120	64 qam	11

Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1	ATDMA	0	0	5	0
2	ATDMA	0	0	3	0
3	ATDMA	0	0	4	0
4	ATDMA	0	0	3	0

 

Live BQM Graph: https://www.thinkbroadband.com/broadband/monitoring/quality/share/7ff0a3730404893446fa496fa993820232... 

[andy1027]

Network Log

Time Priority Description

05/04/2022 21:06:10	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
04/04/2022 19:18:41	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/04/2022 21:38:25	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/04/2022 07:18:40	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
28/03/2022 23:04:38	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
28/03/2022 19:18:39	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/03/2022 18:10:52	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/03/2022 07:18:39	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/03/2022 06:41:0	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
22/03/2022 04:24:53	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/03/2022 15:29:40	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;