Matchmaking issues

Hello,

I am contacting you regarding a persistent matchmaking and routing issue affecting my Battlefield 6 account (PC, Steam).

For more than two months, my official matchmaking traffic has been consistently routed from Central Europe to US-East (Ashburn, Virginia) instead of European servers. This results in very high latency, poor hit registration, and makes the game nearly unplayable for me.

What I have already tested on my side:

Multiple VPN connections within the EU

DNS changes

Full game reinstall

Clearing all local caches, including:

Battlefield / EA App cache

Steam cache

local configuration and temporary files

Account relog and clean restart after cache removal

Firewall tests, including blocking selected AWS / US IP ranges

IPv4 and IPv6 configuration tests, including:

forcing IPv4 only

enabling IPv6

disabling IPv6

testing dual-stack behavior

Verification that the issue does not occur on community servers

None of these steps provided a stable or permanent solution.

Critical account-based comparison test:

On the same PC, same network, same configuration, I logged in with a different Steam account and played Battlefield 6.

With the other Steam account, matchmaking correctly routed to EU servers

With my Steam account, matchmaking consistently routed to US-East

This clearly confirms that the issue is account-specific, not related to my PC, network, ISP, or Steam installation.

Network diagnostics performed:

PortQry test (UDP 3659 – matchmaking port)

easo.ea.com consistently resolves for my account to 159.153.71.17, part of 159.153.71.0/24 (EA Ashburn / US-East).

UDP 3659 responds as LISTENING or FILTERED (expected behavior for UDP).

Tracerout

Traffic from my connection leaves Europe via Zayo backbone, routes to US-East (Ashburn, VA), and terminates at

ncaa.gos.ea.com [159.153.71.17].

Comparison with community servers

Community servers always remain within Europe with correct latency.

Additional confirmation:

When outbound traffic to 159.153.71.0/24 is blocked at OS firewall level, matchmaking either fails or correctly prefers EU routing, further confirming incorrect backend region assignment.

Conclusion:

Based on all performed tests, this issue is not caused by my local network, PC, ISP, IP version (IPv4/IPv6), cache, or Steam installation.

All evidence points to my EA / Steam account being associated with an incorrect backend region in EA Online Services.

I kindly ask for this case to be escalated to the EA network / infrastructure team, as this appears to be an account-level routing / region assignment issue that cannot be resolved client-side.