Title: Receiving Apex Client Updates from EU Matches via US (Ashburn)

Hi there,

I'm based in South Africa, and I've been troubleshooting persistent issues with latency, desync, and inconsistent hit registration in Apex Legends. I’ve been monitoring game traffic using tools like Resource Monitor and confirmed the following pattern:

Issue Summary

When I connect to the EU region in Apex, I expect both my game inputs and server updates (enemy actions, world state, etc.) to route between me and an EU-based game server. However, during gameplay, I consistently observe that my Apex client receives most of the server data from AWS IP addresses geolocated in Ashburn, Virginia, USA — even though the game region is set to EU.

What I’ve Done to Confirm This

Used Resource Monitor and NetLimiter to track live IP traffic for r5apex.exe during matches. Observed Received B/sec (which indicates inbound server updates) coming from AWS IPs located in Ashburn, VA (US-East) — not Europe. Matched IPs across multiple sessions, both with and without VPNs, and even across matches set explicitly to EU region.

Some examples of IPs consistently pushing updates:

54.173.150.237

52.41.149.37

35.80.125.82

54.186.201.159

Geolocation confirms these are US-East or US-West AWS regions. This behavior is consistent across multiple games, reboots, and even ISP routing configurations.

Why This Is a Problem

My game sends data to EU (180ms latency), but receives updates from the US (220–250ms). This results in one-way delay imbalance: my damage lands fine, but enemy movement and actions are delayed, leading to poor peek trades, rubberbanding, ghost shots, and general input mismatch. It feels like I'm shooting at players who already moved — which breaks gameplay. When I purposely connect to US servers, gameplay feels identical, confirming that I’m already being routed via US even on EU.

Request

Please investigate this routing behavior. Is there a reason Apex EU matches would deliver client updates from US-based AWS infrastructure? This is not a local ISP issue — multiple ISPs in my country show the same behavior. I understand AWS load-balancing and traffic engineering may play a role, but routing inbound game traffic from US to South Africa for an EU match severely undermines fair play. If this is a result of how Apex's netcode uses AWS edge nodes or how sessions are handed off, we need clarity.

Thanks.