EA FC 26 Ultimate Team Unable to Connect to EAS FC Servers June 2026

What is the FC 26 Ultimate Team EAS Server Connection Error?

After the June 2026 Ultimate Team mid-cycle patch (live-services build 26.0.1.6.18), thousands of FC 26 players are stuck on Unable to connect to EAS FC servers. Please check your internet connection and try again. The dialog appears with no error code, which makes it look like a single error — but it actually fires at four different stages of the UT flow, each with a different root cause. The fix depends entirely on where in the flow you got kicked, and applying the wrong fix wastes hours.

The four stages are: login (you can't reach the UT hub), squad load (you reach the hub but your squad won't populate), match queue (squad loads but Division Rivals or Champions can't find a match), and result save (the match ends but the result and rewards never write to the server). EA acknowledged the stage-specific behaviour in their [EA Help status post](https://help.ea.com/en/ea-sports-fc/ea-sports-fc-26/) on June 14, 2026.

When does it occur?

• At the EA app launch into FC 26 Ultimate Team (stage 1: login)
• After clicking Play Ultimate Team from the main FC 26 menu (stage 1: login)
• After UT hub loads but squad slots show as empty cards (stage 2: squad load)
• On the matchmaking screen for Division Rivals, Champions, or Squad Battles (stage 3: queue)
• At the post-match results screen when coins and XP fail to credit (stage 4: result save)
• During peak hours 18:00-23:00 UTC and on Friday Champions release night
• After a Windows 11 KB5094126 or KB5095149 install on PC

Common causes

• Stale EA login token after the June 2026 patch — the new live-services build invalidated session tokens minted before June 14
• EA companion app session conflict — the Web/Mobile UT companion holds an exclusive lock that blocks the PC/console session
• DNS resolution caching the old EAS endpoint — the patch moved EAS to a new CDN; cached DNS still points to the dead one
• Strict NAT blocking the Champions matchmaking handshake — Champions uses different ports than Rivals
• Match result write timeout on EA's EU cluster — confirmed by EA on the [official tech bulletin](https://www.ea.com/games/ea-sports-fc/ea-sports-fc-26)
• Windows 11 June 2026 cumulative update breaking the EAAntiCheat network filter driver
• Outdated PS5/Xbox Series X system software (under 25.06) missing the EAS root CA refresh

Step-by-step fixes

1. Identify your stage first — this is the most important step — when the error fires, note exactly where you were. (1) Couldn't reach the hub at all = stage 1. (2) Hub loaded but squad cards are blank or you see Loading squad... for over 10 s = stage 2. (3) Stuck on Searching for opponent past 60 s = stage 3. (4) Match completed but the result screen says Unable to save match = stage 4. Each stage has a different mandatory fix.
2. Stage 1 (login) — re-login to the EA app and refresh DNS — close FC 26 and the EA app fully. Open Command Prompt as admin → ipconfig /flushdns. Then open EA app → click your profile → Log Out → wait 15 s → log back in. Launch FC 26. This invalidates and re-mints your session token, which is mandatory for accounts that connected before June 14.
3. Stage 1 (login) — switch to Cloudflare DNS — Settings → Network & Internet → your adapter → Edit DNS settings → manual → 1.1.1.1 and 1.0.0.1. The EAS CDN move on June 14 means your ISP's cached resolver may still point at the dead endpoint for up to 48 hours. Cloudflare picks up the new endpoint within 5 minutes.
4. Stage 2 (squad load) — kill every companion session — the Web Companion (fc.ea.com) and Mobile Companion both hold an exclusive UT session lock. Open every browser tab that has the web companion and click Sign out. Force-quit the Mobile Companion on your phone (swipe up, swipe away). Wait 60 s, then return to FC 26 and click Try again — the squad will populate within 5 s if this was the cause.
5. Stage 2 (squad load) — clear the Ultimate Team cache — close FC 26. Delete C:\Users\{user}\AppData\Local\Electronic Arts\EA Desktop\CEF\Cache and C:\Users\{user}\AppData\Local\EA SPORTS FC 26\UT_cache. On PS5: Settings → Storage → Console Storage → Saved Data → EA SPORTS FC 26 → delete the UT-CACHE entry only (keep UT-SAVE). Relaunch.
6. Stage 3 (queue) — open Champions and Rivals ports — Champions uses a different port range than Rivals. On your router forward TCP 443, 9988, 17500-17506 and UDP 3659, 9988-9990, 17502-17510 to your console/PC. Set NAT type to Open or Type 2. Test by queueing one Rivals match (should find in 30 s) and one Champions match (should find in 45 s).
7. Stage 4 (result save) — wait, then verify before re-queueing — when the result-save fails, do not click Retry immediately and do not quit to dashboard. EA's UT result writer queues the save for up to 5 minutes. Wait 5 full minutes on the error screen, then click Continue. Check your coin balance — if it credited, you're good. If it didn't, file a case at help.ea.com immediately with the match timestamp; EA's June 2026 manual credit team has a 48-hour turnaround.
8. All stages — repair EAAntiCheat after Windows 11 KB5094126 — open the FC 26 install folder, right-click EAAntiCheat.Installer.exe → Run as administrator → Repair. Then in Services (services.msc) confirm EA AntiCheat Service is set to Automatic (Delayed Start) and is Running. The June 2026 cumulative breaks the AC network filter driver, which silently blocks the EAS handshake on all four stages.

If it still doesn't work

If you've worked through your stage's fixes and the error persists, the root cause is almost certainly an EA-side cluster routing issue, not a client problem. Check the [EA Help server status page](https://help.ea.com/en/ea-sports-fc/ea-sports-fc-26/) and @EAFC_Direct on X. On Friday Champions release nights (Friday 18:00 UTC) the EU and NA clusters routinely degrade for 60-90 minutes; no client-side fix helps and the only durable action is to wait or queue on a different cluster by changing your EA app region temporarily.

For the related crash where FC 26 closes to desktop instead of showing the connection error, see the [EA FC 26 access violation crash guide](/en/errors/ea-fc-26-crash-access-violation-pc). For the World Cup mode-specific server error, see the [EA FC 26 World Cup tournament crash guide](/en/errors/ea-fc-26-world-cup-mode-tournament-crash-pc). For the related Steam authentication failure that prevents the EA app from even launching after the June 2026 patch, see the [Steam authentication failure guide](/en/errors/steam-authentication-failure-june-2026-disconnect).