cancel
Showing results for 
Search instead for 
Did you mean: 

apex legends packet loss 2-8%

neopiotr
Tuning in

Hi .

since im having virgin broadband apex legends is unplayable. massive packet loss. I read loads of topics on forum and only one person had it sorted by upgrading router to hub 4. Before anyone ask yes I switched firewall off and yes im using ethernet cable . tryed 3 of them . same issues on ps4 and ps5. I will put my logs here.

contacted virigin media over phone but been told that its not something that they can sort cuz its not in their troubleshooting. asked for engineer to come been told to pay 25 pounds. guy who i was dealing with said his name was Nevil (didnt sound like nevil ;p) Can I have it sorted please. 

when I do traceroute with apex server ip takes ages. I tryed to sort it out with ea games advisor but they are saying its internet provider fault. 

Trace Statistics : traceroute to 217.147.89.101 (217.147.89.101), 10 hops max, 38 byte packets
1 10.53.38.229 (10.53.38.229) 10.000 ms 10.000 ms 10.000 ms
2 brad-core-2b-xe-2019-0.network.virginmedia.net (82.2.241.117) 10.000 ms 10.000 ms 10.000 ms
3 * * *
4 * * *
5 tcl5-ic-7-ae0-0.network.virginmedia.net (213.105.11.198) 10.000 ms 10.000 ms 10.000 ms
6 be20.asr01.thn.as20860.net (195.66.224.207) 20.000 ms 20.000 ms 20.000 ms
7 be500.ncs5500-1.dc5.as20860.net (130.180.202.81) 20.000 ms 20.000 ms 20.000 ms
8 1717.g1.1ug.dc5.as20860.net (87.117.210.26) 20.000 ms 10.000 ms 20.000 ms
9 217.147.89.101 (217.147.89.101) 20.000 ms 20.000 ms 90.000 ms
Trace complete.

thats when ping apex server 

PING 217.147.89.101 (217.147.89.101): 64 data bytes
72 bytes from 217.147.89.101: seq=0 ttl=118 time=30.000 ms
72 bytes from 217.147.89.101: seq=1 ttl=118 time=20.000 ms
--- 217.147.89.101 ping statistics ---
3 packets transmitted, 2 packets received, 33% packet loss
round-trip min/avg/max = 20.000/25.000/30.000 ms



Downstream bonded channels

0/10/2023 17:08:33noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
06/10/2023 20:47:58criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
06/10/2023 10:17:24noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
06/10/2023 10:17:24ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
04/10/2023 16:06:59criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/10/2023 22:17:24noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/10/2023 22:17:24ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/10/2023 19:22:15criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/10/2023 11:36:53Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/10/2023 11:36:47Warning!Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/10/2023 11:36:43criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/10/2023 11:36:42Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/10/2023 11:36:42criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
30/09/2023 16:25:27criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
29/09/2023 10:17:23noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
29/09/2023 10:17:23ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
27/09/2023 21:24:30criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
26/09/2023 00:16:44noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
26/09/2023 00:16:44ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/01/1970 00:01:41criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.



Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1ATDMA0010
2ATDMA0000
3ATDMA0000
4ATDMA0000
5ATDMA0020
6ATDMA000

0

9 REPLIES 9

Client62
Legend

Check if the packet loss exists in the connection to the local VM Data Centre.

https://www.samknows.com/realspeed/

Once the test begins click on: Run full test to see Packet Loss / Latency / Jitter / Upstream

Do share the full test results.

D64747B7-82E5-4D0F-A8D6-A5A7C5D9BFD3.png

neopiotr
Tuning in

I repeated test 3 min later and my speed is 2x 

7B20BED5-A4D5-42C2-9433-DC07E9564841.png

Client62
Legend

In the first test was there another device doing a download or TV catch up on your Hub ?

Both tests show zero packet loss, the packet loss you see in the game is outside your VM connection.

So why only Virgin media users have issues with apex ? It’s clearly vm fault . 
Just put Apex packet loss in search and you will find loads of ppl having issues . Only one person had it sorted by getting modem upgraded.

test was done on same Device no tv at home just broadband. 
my neighbour got sky no packet loss . Game works smooth . 

neopiotr
Tuning in

Seems like no one care . Yesterday had 60 packet loss . Game is unplayable. 

Hey neopiotr, thank you for reaching out and a warm welcome to the community I am so sorry to hear this.

I have done a check and everything is look fine, is it just this game you are having isseus with?

Is there any other games at all? Cheers 

Matt - Forum Team


New around here?

I’m not really playing any other games . 
translation name of server . Ping and packet loss . Should be 0. I’ve tryed 2 different consoles . I tryed with phone as hotspot and it was 0 . sometimes packet loss are even 8 

FBE92F17-AE7D-494F-95E6-A8C5C76B2E0F.jpeg

Reece_MH
Forum Team (Retired)
Forum Team (Retired)

Hi neopiotr 👋

Thanks for providing a further update on this. I'm sorry to hear the issue is ongoing. I've ran some further checks on our side, and cannot identify any issues that may be causing this for you. The signal to your Hub is within specification, and I cannot see any Packet Loss on the line.

It would be best to speak with EA directly and advise that we've run all the possible checks we can, and see if they can assist you further with any potential fixes. For background, I play Apex Legends occasionally (on a Virgin Media home network), and do not see this issue and a few colleagues who play and use our network (various different setups and locations), do not see this either.

Sometimes game server providers can limit, or attempt to block connections from specific IP addresses. As we provide Dynamic IPs, a connection that previously used your IP may have caused the host to log the IP as potentially malicious, but this isn't something we can identify on our side. 

Thanks,

Reece - Forum Team


New around here? To find out more about the Community check out our FAQ