hanks! I’m aware EA servers run on AWS, but the routing issue happens before that — through EA’s Zayo infrastructure.
Tracing easo.ea.com shows the path being sent through Zayo’s US cluster instead of EU (Frankfurt/Amsterdam), which causes the high latency (~110 ms).
That’s why I’m checking both the matchmaking route and AWS hop chain. There’s no contradiction. I’m tracing the correct part of the route that both EA and the ISP need to see.
A direct traceroute to the AWS game instance would only show the final server, not the matchmaking node that assigns the region.
The routing issue happens earlier, on the EA/Zayo layer — that’s exactly what I’m trying to get fixed with Zayo support.
Mohiczek what's the IP address of the Amazon AWS server? This will tell us where the game server is located.
The active EA connection routes to 159.153.71.17, which resolves to easo.ea.com.Based on traceroute, the traffic goes through Vodafone CZ → Zayo (zip.zayo.com) and terminates in Ashburn, Virginia, which is part of the AWS US-East-1 region.
This confirms that Battlefield 6 is currently connecting EU players (like me, located in the Czech Republic) to the US-East AWS cluster instead of the EU ones (Frankfurt / Amsterdam).
Both Vodafone and Zayo confirmed their routing is correct — so the issue seems to be on EA’s side (region matchmaking or routing assignment).
