cancel
Showing results for 
Search instead for 
Did you mean: 

Packet loss

tattonelectrics
Tuning in

For some reason for the past couple of days I've been receiving upwards of 20% packet loss on my Xbox. Absolutely nothing has changed in my installation to have started causing this so I was wondering if there is a problem from the supply end?

31 REPLIES 31

aacc
Tuning in

Adding to this (and cross posting) as seeing similar for past two days (10 and 11 Nov). Packet loss to Azure/msn.net for PUBG on PC. Measured packet loss was ~14%, varies in game and results in network lag reported in game.

Tested on the Xbox after seeing this, that is reporting similar levels of packet loss on the connection test.

Destination address at time of testing was 20.218.127.109

|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                             192.168.0.1 -  100 |  228 |    1 |    3 |    3 |    3 |    3 |
|                   No response from host -  100 |  228 |    0 |    0 |    0 |    0 |    0 |
|swan-core-2b-ae19-650.network.virginmedia.net -    4 |  984 |  946 |    7 |   11 |   74 |    9 |
|                   No response from host -  100 |  228 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  228 |    0 |    0 |    0 |    0 |    0 |
| telw-ic-5-ae0-0.network.virginmedia.net -    5 |  972 |  931 |   11 |   16 |   87 |   13 |
|    virginmedia.ier03.lon32.ntwk.msn.net -   14 |  737 |  636 |   12 |   17 |   75 |   24 |
|         ae31-0.icr01.lon22.ntwk.msn.net -   14 |  749 |  651 |   13 |   19 |   97 |   16 |
|       be-100-0.ibr01.lon22.ntwk.msn.net -   14 |  749 |  651 |   24 |   31 |  190 |   31 |
|        be-15-0.ibr01.ams30.ntwk.msn.net -   13 |  753 |  656 |   24 |   30 |  168 |   31 |
|        be-14-0.ibr01.fra21.ntwk.msn.net -   12 |  777 |  686 |   24 |   29 |   87 |   27 |
|        ae100-0.icr01.fra21.ntwk.msn.net -   14 |  749 |  651 |   23 |   30 |  100 |   43 |

The connection seems to degrade between telw-ic-5-ae0-0.network.virginmedia.net (62.253.174.186) and virginmedia.ier03.lon32.ntwk.msn.net (104.44.14.51).

Tested briefly by tethering my PC to my mobile phone and the connection was much improved, albeit taking a different route.

My broadband connection seems to have been stable, the dropped packets in this case are reboots of the hub.

broadband.png

Logs from hub:

Downstream

Downstream bonded channels
Channel	Frequency (Hz)	Power (dBmV)	SNR (dB)	Modulation	Channel ID
1	331000000	7.5	38	256 qam	25
2	203000000	8	40	256 qam	9
3	211000000	8	38	256 qam	10
4	219000000	8	40	256 qam	11
5	227000000	7.8	38	256 qam	12
6	235000000	7.5	38	256 qam	13
7	243000000	7.5	38	256 qam	14
8	251000000	7.4	40	256 qam	15
9	259000000	7.5	38	256 qam	16
10	267000000	7.5	40	256 qam	17
11	275000000	7.5	38	256 qam	18
12	283000000	7.8	40	256 qam	19
13	291000000	7.9	38	256 qam	20
14	299000000	8.4	38	256 qam	21
15	307000000	8.3	40	256 qam	22
16	315000000	8.3	38	256 qam	23
17	323000000	7.8	38	256 qam	24
18	371000000	7.1	40	256 qam	26
19	379000000	7.5	38	256 qam	27
20	387000000	7.5	40	256 qam	28
21	395000000	7.5	40	256 qam	29
22	403000000	7.5	40	256 qam	30
23	411000000	7.5	38	256 qam	31
24	419000000	7.1	38	256 qam	32


Downstream bonded channels
Channel	Locked Status	RxMER (dB)	Pre RS Errors	Post RS Errors
1	Locked	38.9	5	0
2	Locked	40.3	5	0
3	Locked	38.9	4	0
4	Locked	40.3	2	0
5	Locked	38.9	5	0
6	Locked	38.9	5	0
7	Locked	38.9	5	0
8	Locked	40.3	0	0
9	Locked	38.9	7	0
10	Locked	40.3	5	0
11	Locked	38.9	5	0
12	Locked	40.3	5	0
13	Locked	38.9	7	0
14	Locked	38.9	19	0
15	Locked	40.3	6	0
16	Locked	38.9	17	0
17	Locked	38.6	4	0
18	Locked	40.3	0	0
19	Locked	38.9	5	0
20	Locked	40.9	5	0
21	Locked	40.3	5	0
22	Locked	40.3	16	0
23	Locked	38.9	16	0
24	Locked	38.9	6	0

Upstream

 

Upstream bonded channels
Channel	Frequency (Hz)	Power (dBmV)	Symbol Rate (ksps)	Modulation	Channel ID
1	49599951	43	5120	64 qam	1
2	23600000	42	5120	64 qam	5
3	30100224	42.3	5120	64 qam	4
4	36600151	42.5	5120	64 qam	3
5	43099966	42.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
5	ATDMA	0	0	0	0

Logs

Network Log
Time	Priority	Description
11/11/2023 18:28:43	notice	LAN login Success;CM-MAC=MAC1-Redacted;CMTS-MAC=MAC2-Redacted;CM-QOS=1.1;CM-VER=3.0;
01/01/1970 00:01:40	critical	No Ranging Response received - T3 time-out;CM-MAC=MAC1-Redacted;CMTS-MAC=MAC2-Redacted;CM-QOS=1.1;CM-VER=3.0;
11/11/2023 16:33:45	notice	LAN login Success;CM-MAC=MAC1-Redacted;CMTS-MAC=MAC2-Redacted;CM-QOS=1.1;CM-VER=3.0;
11/11/2023 06:51:46	critical	No Ranging Response received - T3 time-out;CM-MAC=MAC1-Redacted;CMTS-MAC=MAC2-Redacted;CM-QOS=1.1;CM-VER=3.0;
11/11/2023 06:51:22	critical	Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=MAC1-Redacted;CMTS-MAC=MAC2-Redacted;CM-QOS=1.1;CM-VER=3.0;
11/11/2023 06:51:22	critical	Ranging Request Retries exhausted;CM-MAC=MAC1-Redacted;CMTS-MAC=MAC2-Redacted;CM-QOS=1.1;CM-VER=3.0;
11/11/2023 06:50:38	critical	No Ranging Response received - T3 time-out;CM-MAC=MAC1-Redacted;CMTS-MAC=MAC2-Redacted;CM-QOS=1.1;CM-VER=3.0;
09/11/2023 16:14:18	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=MAC1-Redacted;CMTS-MAC=MAC2-Redacted;CM-QOS=1.1;CM-VER=3.0;
06/11/2023 16:57:0	critical	No Ranging Response received - T3 time-out;CM-MAC=MAC1-Redacted;CMTS-MAC=MAC2-Redacted;CM-QOS=1.1;CM-VER=3.0;
06/11/2023 04:14:17	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=MAC1-Redacted;CMTS-MAC=MAC2-Redacted;CM-QOS=1.1;CM-VER=3.0;
02/11/2023 21:12:38	critical	No Ranging Response received - T3 time-out;CM-MAC=MAC1-Redacted;CMTS-MAC=MAC2-Redacted;CM-QOS=1.1;CM-VER=3.0;
02/11/2023 16:14:17	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=MAC1-Redacted;CMTS-MAC=MAC2-Redacted;CM-QOS=1.1;CM-VER=3.0;
02/11/2023 03:17:15	critical	No Ranging Response received - T3 time-out;CM-MAC=MAC1-Redacted;CMTS-MAC=MAC2-Redacted;CM-QOS=1.1;CM-VER=3.0;
01/11/2023 16:03:57	Warning!	RCS Partial Service;CM-MAC=MAC1-Redacted;CMTS-MAC=MAC2-Redacted;CM-QOS=1.1;CM-VER=3.0;
30/10/2023 04:14:17	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=MAC1-Redacted;CMTS-MAC=MAC2-Redacted;CM-QOS=1.1;CM-VER=3.0;
29/10/2023 07:00:0	critical	No Ranging Response received - T3 time-out;CM-MAC=MAC1-Redacted;CMTS-MAC=MAC2-Redacted;CM-QOS=1.1;CM-VER=3.0;
26/10/2023 16:14:17	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=MAC1-Redacted;CMTS-MAC=MAC2-Redacted;CM-QOS=1.1;CM-VER=3.0;
26/10/2023 15:49:45	critical	No Ranging Response received - T3 time-out;CM-MAC=MAC1-Redacted;CMTS-MAC=MAC2-Redacted;CM-QOS=1.1;CM-VER=3.0;
23/10/2023 04:14:17	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=MAC1-Redacted;CMTS-MAC=MAC2-Redacted;CM-QOS=1.1;CM-VER=3.0;
20/10/2023 02:06:3	critical	No Ranging Response received - T3 time-out;CM-MAC=MAC1-Redacted;CMTS-MAC=MAC2-Redacted;CM-QOS=1.1;CM-VER=3.0;

Any help much appreciated.

Donkyle
Tuning in

I've been having the same problem for the last couple of days. Virgin saying there's no problem on their end, clearly must be.

Donkyle_0-1699727970994.png

This Is what I'm dealing with, I use game pass to stream games so the packet loss is just kicking me off

CampFreddy
Tuning in

I've been seeing similar issues. I mainly play PUBG on PC and not only am I seeing network lag in games (usually attributed to poor quality broadband rather than speed, and in this case packet loss is high), but my actual speeds are about half of what they should be.

Things were fine on Thursday night, but really bad since early evening yesterday, continuing into today.

ThisIsTom
On our wavelength

Using the gigabit FTTP service and have been having similar issues (although on a PC and trying to play PUBG). Only affecting people with VM at the moment, everyone else I know on other ISPs are not seeing the issue. It's making games unplayable.The issue started a few days ago.

Exactly the same for me. Friday evening it started and both PUBG and Rainbow six siege showing packet loss issues and when I run a connection test on the Xbox it shows this...

20231111_225533.jpg

aacc
Tuning in

I've contacted support and gone through the usual checks (reset hub etc.). It's clear where the connection is degrading with trace route. I didn't have any traction with escalation, hoping someone can escalate from this and other threads.

As is, support have asked me to contact them in 72 hours if the issue persist. They'll want to send a technician then.

Extract from trace route. 

|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| telw-ic-5-ae0-0.network.virginmedia.net -    0 |  123 |  123 |   11 |   15 |   46 |   23 |
|    virginmedia.ier03.lon32.ntwk.msn.net -   11 |   89 |   80 |   13 |   18 |   46 |   17 |
|         ae29-0.icr01.lon24.ntwk.msn.net -   11 |   89 |   80 |   14 |   20 |   38 |   17 |

I reckon it's an issue with peering between Virgin and Microsoft judging from the hostnames. (Telehouse West?)

 

Responding to this thread to bump as aacc's data needs to be looked at, bunch of us with the same issue that needs to be resolved better than a phone agent telling us to restart our routers and wait 24-72 hours!

Not going to lie, I have absolutely no idea what any of that data means that you've included but thankyou for doing so! Hopefully it helps to shed some light that it's something that needs looking into

daryl-t
Tuning in

I've not been able to game since 02:30 12/11/23 due to massive lag (packet loss). Also my land line has stopped working, looks like VM done something to the backend and routing and broke the network again but they are keeping quiet about it. According to them my connection is fine, then now they are saying that there is an issue locally (but phone line is ok when it is not). Lots of people are having problems again all over. At one stage I could not log into their app to check report the issue. Really regret switching to VM.