Visitor
•
6 Messages
Packet loss to Battlefield 6 official servers only
I have noticed while playing bf6 that when connecting to the official EA servers I have weird rubber banding issues. This is not an issue when connecting to the unofficial servers found in the server browser. I tried to do some troubleshooting and pinging known servers EA uses for bf6 and I loose all packets sent to those servers. Is there anyway I can get Comcast to re-route my traffic or figure out why I am loosing packets? I have attempted to change my DNS with no luck. Any help or advice is appreciated.
XfinityNatalie
Official Employee
•
457 Messages
8 days ago
Hey there, user_8hztzo! Thanks for knocking on our XFINITY Community door. We do not wish for you to go through any packet loss, especially in the middle of your gaming. Rest assured, you have reached the right team to help troubleshoot this issue further. Before we proceed, I would like to confirm if you are connected hardwired or wirelessly when you run into this issue.
7
0
user_46656d
Visitor
•
20 Messages
2 days ago
@user_8hztzo Are you able to run a traceroute to one of the servers you are having issues with (post it here so we can have a look)? This should show you where the packets are being dropped. If they are being dropped on the comcast ibone then comcast may have to look further into it. If it shows outside of the ibone, then the issue lies somewhere outside of Xfinity's control
(edited)
1
EG
Expert
•
114.6K Messages
18 hours ago
@user_8hztzo
FWIW. Just for reference, I'm on the Optimum cable network, and my traceroute does not complete to the destination server either;
C:\Windows\System32>tracert 54.197.155.195
Tracing route to ec2-54-197-155-195.compute-1.amazonaws.com [54.197.155.195]
over a maximum of 30 hops:
1 6 ms 2 ms 2 ms 192.168.1.1
2 * * * Request timed out.
3 9 ms 10 ms 12 ms 67.59.254.101
4 13 ms 13 ms 10 ms 67.59.254.246
5 13 ms 11 ms 13 ms 63.142.20.230
6 12 ms 11 ms 15 ms 64.15.1.153
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
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.
Hop #2 is the CMTS, which they have deliberately configured to reject ICMP-based ping and traceroute packets. Hops 3-6 are Optimum regional routers.
0
0
user_46656d
Visitor
•
20 Messages
16 hours ago
Thanks for testing that outside of a Xfinity network, @EG! I am also getting the same results as @user_8hztzo only my signal is going from AZ to TX and then it stops responding toe ICMP request. So it seems like once it transfer from xfinity to the next routing point is where the issue lays, meaning it's not the Xfinity network.
Looking at the IP it looks like it goes through Amazon servers which can rely on Cloudflare servers. I bring this up as it looks like Cloudflare is currently having issues at this time. I would suggest trying to change your DNS server to go through google (8.8.8.8 and 8.8.4.4) if you happen to have it set up to Cloudflare (1.1.1.1 and 1.0.0.1) at the moment and see if you have any luck with that.
0
0
EG
Expert
•
114.6K Messages
16 hours ago
@user_46656d
Quite welcome ! Good luck all !
0
0