FC 27 (PC): match ping 33-42ms → 50+ms after October maintenance — evidence
Hi EA team and everyone reading this.
I want to report a server-side routing problem that started right after the October server maintenance. Everything below is measured and verified data, not guesses.
MY SETUP
- Location: Ufa, Russia (Urals)
- ISP: Ufanet, wired connection, stable, no issues on my side
- Game: EA SPORTS FC 27, PC
- Platform: PC (the same behavior in every match, not related to specific opponents)
TIMELINE AND SYMPTOMS
- FC 27 launched on September 17, 2026. From launch day until mid-October my in-game match ping was consistently 33-42 ms. Smooth, stable, no problems at all.
- Immediately after the October server maintenance the situation changed overnight: ping is now 50 ms and above (very rarely dips to 48, rises higher when servers are loaded), with visible packet loss and connection instability.
- In the worst cases the connection to the opponent drops completely mid-match.
- These disconnections trigger unfair sanctions against me: reduced coin rewards and uncredited objectives. I am being penalized for something that is happening on the server side.
EVIDENCE 1 — WHERE MY MATCH TRAFFIC ACTUALLY GOES
I captured game traffic during live matches using pktmon (the built-in Windows packet monitoring tool — no third-party software, no risk of triggering anticheat).
Match traffic (ports 3659 / 9999 / 52054 / 52055, over 600,000 packets total) goes to exactly two Google Cloud hosts:
- 35.217.3.225 — 353,286 packets
- 35.217.34.79 — 271,330 packets
All other EA endpoints exchanged only about 112 packets each — those are clearly background services, not the match itself.
Conclusion: my matches are served from two Google Cloud IPs. There is no way to influence which ones — they are assigned by EA's server infrastructure.
EVIDENCE 2 — MY PATH TO THOSE SERVERS IS CLEAN
Traceroute to both hosts, zero packet loss across all hops:
- Hops 1-10 (inside my ISP network): 3-5 ms, no loss
- Hop 12 (ISP border, 81.27.252.150): 29 ms
- Hop 14 (first Google network node, 72.14.220.22): 42 ms
- Beyond that Google does not respond to probes (normal for their internal network)
This means my ISP delivers traffic to the Google network edge in 42 ms with zero loss. The path is excellent. Therefore the extra latency, the packet loss and the disconnections originate inside EA's hosting side — not on my connection.
EVIDENCE 3 — THE TIMING MATCHES THE MAINTENANCE EXACTLY
The change happened overnight, immediately after the October maintenance, with no changes on my side: same ISP, same router, same cables, same game version. If my connection was the problem, the ping would not jump from 33-42 ms to 50+ ms in one night.
WHAT I BELIEVE HAPPENED
The October maintenance changed the region-to-data-center mapping: accounts from my region (Russia, Ufa area) are now assigned to a farther data center instead of the closer one that served us from launch until the maintenance. This is consistent with reports from other players in Russia in this forum section describing the same symptoms after the same maintenance.
WHAT I AM ASKING EA TO DO
1. Confirm which data center is currently assigned to my account for FC 27 matches.
2. Check whether the region-to-data-center mapping for Russia was changed during the October maintenance.
3. Restore the closer data center that served my region from launch until the maintenance.
4. Review the unfair sanctions (reduced coin rewards, uncredited objectives) I received because of disconnections that were not my fault.
I can provide full packet captures and traceroutes at any time — just ask.
P.S. Side note for the EA team: the help.ea.com portal does not create cases for my account — submitted reports never appear in "My Cases" and no confirmation email ever arrives (tried different browsers, private mode, English site version). Because of that I could not open a formal ticket, which is why I am reporting this here. I would appreciate it if a Community Manager could open a manual case for this issue.
Thank you.
