EA Sports FC 26 — Fix the ‘Searching For Opponent’ matchmaking bug
FC 26Disable crossplay first, then reset your network and review official status updates.

“Searching For Opponent” stuck on Rivals, Rush, or Live Friendlies indicates a current Ultimate Team matchmaking issue impacting FC 26 on all platforms. EA has acknowledged the problem, and reports show it began during early access and expanded near launch. While a permanent fix is pending, the steps below can restore matchmaking for many players or provide reliable ways to keep progressing.
Fix ‘Searching For Opponent’ in FC 26 (disable crossplay)
This client-side toggle is the most consistent workaround reported so far. It restricts your pool to same-platform players, which can bypass cross-platform matching issues.
Step 1: Open the in-game Settings from the main menu.
Step 2: Go to the Matchmaking section.
Step 3: Set Crossplay to Off.
Step 4: Return to Ultimate Team and start a new search in Rivals or Rush.
If your opponent pool is thin on your platform or in your region, queue times may still vary. Re-enable crossplay later once official fixes roll out.
Fix stuck matchmaking (power-cycle your router/modem)
Refreshing your local network can resolve routing or data center quirks that block or slow matchmaking.
Step 1: Turn off your router (and modem, if separate). Unplug power cables to fully shut them down.
Step 2: Wait at least 30 seconds to clear cached network states.
Step 3: Power the modem back on, then the router. Wait until the internet connection is stable.
Step 4: Reconnect your console or PC and try searching for an opponent again.
Restart the game and your device
A clean app and OS session can recover from temporary matchmaking handshakes or data center assignments.
Step 1: Fully close FC 26 (don’t just suspend). On console, quit to the dashboard and close the game app.
Step 2: Reboot your console or PC to clear residual network and process states.
Step 3: Launch FC 26, enter Ultimate Team, and start a new search.
Improve connection quality (official EA steps)
If your connection is marginal or inconsistent, optimizing your home network improves stability and reduces matchmaking failures. Follow EA’s guidance here: EA Help: Troubleshoot EA SPORTS FC connection issues.
Step 1: Run EA’s Connection Quality checks to understand your baseline (latency, jitter, packet loss) and identify trends.
Step 2: Change your Wi‑Fi channel if you use 2.4 GHz. Try non-overlapping channels 1
, 6
, or 11
to reduce interference; test each for stability.
Step 3: Update your router firmware. New firmware often fixes bugs and improves wireless stability under load.
Step 4: Disable any VPN while playing. VPNs add latency and can disrupt matchmaking routes.
Step 5: Enable QoS (Quality of Service) on your router to prioritize game traffic, which can reduce spikes when your network is busy.
Modes impacted and reliable alternatives
Reports indicate specific Ultimate Team modes are affected, while others remain playable. Use the table below to plan your session while waiting for fixes.
Mode | Status |
---|---|
Rivals | Affected by “Searching For Opponent”. |
Rush | Affected by “Searching For Opponent”. |
Live Friendlies | Reported impacted for some players. |
Early Access Elimination (Tournament) | Affected by “Unable to find opponent”. |
Friendlies (with friends) | Reported to work via direct invites. |
Squad Battles | Playable; progress and rewards unaffected. |
Moments | Playable; earn stars and packs as normal. |
Availability can change as updates roll out; queue behavior may fluctuate by region and time of day.
When to stop troubleshooting
If disabling crossplay and refreshing your network don’t help, the blocker is likely service-side. At that point, keep an eye on official status and communications, and use Squad Battles, Moments, or direct Friendlies to continue earning rewards until a fix is deployed.
Most players recover matchmaking by turning crossplay off or power-cycling their network. If nothing works, switch to offline modes for steady progress while EA deploys a permanent fix.
Comments