Forum Discussion

2 Replies

  • EA_Aljo's avatar
    EA_Aljo
    Icon for Community Manager rankCommunity Manager
    7 months ago

    Hello. I have relayed this to the team for investigation. Thank you.

  • @EA_Aljo Hi,

    Preface this by saying I obviously don't know the design of your infrastructure in any way, but my IRL job is to fix these sort of things.

    I've read through various comments on here/twitter and the vast majority seem to be on UK BT ISP. I've seen comments saying other UK ISP's (Virgin for example) are working fine.

    This is affecting users on all platforms with BT ISP.

    I can recreate the issue at any time simply by scrolling through players in FUT squad, or SBC's. It works for anywhere between a few seconds to 20 seconds, then there is the "There was a problem connecting to the Football Ultimate team servers. Please try again later" error and you are kicked out. So there is traffic, but seemingly at random points this traffic is not getting through/timing out and causing the disconnect.

    Squad battles disconects after the game and gives you a 3-0 loss every time.

    This affects SOME rivals/rush games (could depend where the game is hosted).

    I don't know your server IP's but I've tried tracert to several FUT URL's and they all end up in LON3 DC in London.

    From my home

    1 1 ms <1 ms <1 ms 192.168.1.254
    2 7 ms 7 ms 6 ms 172.16.17.167
    3 * * * Request timed out.
    4 12 ms 11 ms 11 ms 62.6.204.190 < BT CORE
    5 13 ms 12 ms 12 ms 62.6.204.123 < BT CORE
    6 13 ms 12 ms 13 ms 195.66.224.116 < RACKSPACE
    7 * * * Request timed out.
    8 13 ms 12 ms 13 ms dcpe1-corea.lon3.rackspace.net [134.213.97.149] <RACKSPACE
    9 16 ms 14 ms 13 ms corea-core6.lon3.rackspace.net [164.177.137.13] <RACKSPACE

    Tried from a few different websites to get a different route.

    traceroute to utas.fut.ea.com (212.100.255.80), 20 hops max, 60 byte packets
    1 vl223-ar-02.lon-uk.as59764.net (89.107.56.3) 0.250 ms 0.197 ms
    2 * *
    3 be4113.agr21.lhr01.atlas.cogentco.com (154.25.2.149) 1.140 ms 1.146 ms
    4 be3672.ccr52.lhr01.atlas.cogentco.com (130.117.48.145) 1.058 ms 1.114 ms
    5 be3488.ccr42.lon13.atlas.cogentco.com (154.54.60.13) 2.028 ms 2.079 ms
    6 be2350.rcr21.b023101-0.lon13.atlas.cogentco.com (130.117.51.138) 2.208 ms 2.316 ms
    7 gi0-0-0-18.251.nr11.b025687-0.lon13.atlas.cogentco.com (149.11.161.49) 1.986 ms 2.029 ms
    8 10.25.14.130 (10.25.14.130) 3.410 ms 3.399 ms
    9 134.213.97.211 (134.213.97.211) 2.908 ms 2.994 ms
    10 cored-coreb.lon5.rackspace.net (162.13.232.18) 3.262 ms 3.293 ms
    11 coreb-core6.lon3.rackspace.net (164.177.137.25) 3.331 ms 3.332 ms

    the fist hop to the Rackspace network is different when I try from elsewhere - 195.66.224.116 is missing. It actually seems to hit LON5 which is a different Rackspace DC first.

    Nothing is pingable so I can't check for packet loss, although my tracert hasn't failed at all, and the response times are consistently low.

    But as I prefaced, this is just a logical guess, since I don't know if for sure the server IPs or if London server just hosts the webpages and not the actual game servers (logically they do).

About FC 25 Technical Issues

Having issues with FC 25? Join here to find help with connectivity, performance issues, crashes and more.10,238 PostsLatest Activity: 6 minutes ago