Hey EA team,

I’m based in Washington State (West Coast) and my setup is rock-solid — fiber connection, sub-15 ms local latency, 0 % packet loss, Smart Queues enabled on my UDM.

Despite that, Battlefield 6 matchmaking keeps assigning me to AWS us-east-1 (Virginia) servers, resulting in a constant 85 – 95 ms ping even though nearby West-coast servers are clearly reachable and performing great.

I’ve been running a PowerShell network analyzer, and the data makes it obvious:

Local Akamai / CDN edge: 10 – 20 ms ping, perfectly stable
Once matched on East-coast AWS nodes (e.g. 54.210.180.10, 54.197.155.195), latency jumps to 90 ms +
0 % packet loss, all TCP/UDP 3544, DNS, and IPv4 diagnostics are clean
No local congestion — fq_codel Smart Queues active (900 / 38 Mbps)
Issue: purely matchmaking region assignment, not my network
The Problem

West-coast players like me are being routed to East-coast AWS relays, even when local West-coast or Akamai servers are available and reachable at low latency.

That’s adding 70 – 80 ms of unnecessary delay, hurting hit-reg and gameplay fluidity.
This looks like a matchmaking region bias or misconfiguration on EA’s side.

Technical Context

Location: Woodinville, WA (West Coast US)
ISP: Comcast Gigabit (wired Ethernet)
Router: UniFi Dream Machine (Smart Queues = 900 / 38 Mbps)
IPv6: Disabled, Teredo Off
OS: Windows 10 Pro
Game: Battlefield 6 (EA App – latest build)

I can provide full logs showing:

server IP + reverse DNS (AWS us-east-1)
latency, jitter, loss, timestamp samples
auto-detection when matchmaking hops regions
Request

Please escalate this to the Battlefield 6 server ops / matchmaking routing team.
West-coast players are being unfairly routed across the country, adding massive latency that shouldn’t exist when closer servers are online.

For Other Players

If you’re also on the West Coast (CA, WA, OR, NV) and getting 80 ms+ pings on BF6, please:

Reply with your city/state and average ping.
Include your server IP (found under Options → Network Details or via Resource Monitor).
Click “Me Too” / XP / Upvote so EA can see how widespread this is.

Let’s get this fixed — the data proves it’s not a user-side issue.
EA, please pass this up to the matchmaking routing / server region configuration team.

Thanks for taking it seriously.