Community ManagerThanks everyone for the reports.
We have recently made an update to the available matchmaking regions for Clubs matches in FC 27.
If you are experiencing higher than expected latency in Clubs League matches, please review your matchmaking region in your Clubs Settings to ensure you have the recommended region selected.
FC27 Clubs Middle East servers | EA Forums - 13722049
For other modes, could you please share:
If you’re experiencing this specifically in Clubs, please also refer to the dedicated thread:
Thanks for helping me gather more information.
Hello, what about the other game modes? Take Ultimate Team, for example – for many players, ping doubled following the 29 July update, and several new routes appeared that weren’t there before.
This is happening to many users across different regions. Many people used to have a ping of 24–30 ms; now it’s between 35 and 60 ms, and the game is now unplayable – not to mention those whose ping was originally 35–60 ms; their figures are even worse.
Please take note of these reports; we’re waiting for a response.
About the latency/routing issue in FC 27 | EA Forums - 13710466
Community ManagerHi there,
Please take a look at my full previous message. The reports have already been passed along to the team.
Whenever we request additional information, such as your platform, Gamertag, timestamps, ISP, or screenshots, it’s because these details can help the team investigate more effectively and identify patterns across different regions and setups.
I understand that you’re eager to see this resolved, and we really appreciate your patience. Any additional details you can provide can help support the team’s investigation.
Thank you for your attention.
I am attaching an example of a problematic connection in this part of the game. In FC 26, from 19 July, my ping rose sharply to 35 ms and this problem has persisted to this day. Connection issues are being observed in various regions, regardless of internet service provider or location. I ran a traceroute to one of your servers, and it showed that one of the problematic nodes was on twelve99.net:
6 hu0-1-0-3.rcr21.ods02.atlas.cogentco.com (149.11.56.10) 4.377 ms 4.194 ms 3.687 ms
7 be2045.rcr51.kiv01.atlas.cogentco.com (154.54.72.134) 7.461 ms 7.926 ms 7.726 ms
8 be3513.rcr31.buh01.atlas.cogentco.com (154.54.56.62) 14.987 ms 14.834 ms 14.987 ms
9 * * arelion.buh01.atlas.cogentco.com (130.117.55.94) 15.038 ms *
10 win-bb2-link.ip.twelve99.net (62.115.114.112) 49.772 ms 50.003 ms 49.490 ms
11 * ffm-bb2-link.ip.twelve99.net (62.115.138.22) 50.419 ms *
12 war-b3-link.ip.twelve99.net (62.115.120.21) 51.371 ms 50.649 ms 50.114 ms
13 google-ic-3646167.ip.twelve99-cust.net (80.239.128.179) 41.593 ms 42.656 ms 42.223 ms
This is the ping I’m getting on Polish servers (I used to have a ping of 25–30 ms).
If I use programmes to optimise routing, the ping returns to its usual levels: 25–30 ms, as it connects me to Turkish servers.
