007 First Light Multiplayer Connection Error Online Fix

What is the 007 First Light Multiplayer Connection Error?

After the June 2026 launch of IO Interactive's *007 First Light*, players reported being unable to enter online co-op or PvP modes. Symptoms include "Connection to Bond Network lost", "Matchmaking failed (code MI6-0271)", "Authentication timeout — please restart" and the lobby spinning indefinitely after pressing Play Online. The game itself launches fine offline, which makes the issue specifically a backend, NAT, or anti-cheat handshake failure rather than a crash.

When does it occur?

• Immediately after pressing Find a Match or Quick Play in the multiplayer menu
• When accepting a party invite from a friend (party fails to load)
• During the Epic Online Services (EOS) login splash after game start
• After a Steam offline-mode session where DRM token has not refreshed
• On strict-NAT consoles (PS5/Xbox Series X|S) behind double NAT routers
• After the day-one patch 1.0.3 if Easy Anti-Cheat did not auto-update

Common causes

• Xbox Live / PSN service outage affecting the Bond Network backend (check status pages first)
• EOS authentication token expired — login session must be refreshed
• Strict (Type 3) NAT on console or symmetric NAT on PC blocking peer-to-peer hole punching
• UDP ports 5222, 5223, 9000-9100 and TCP 80/443 blocked by ISP or router firewall
• Easy Anti-Cheat installation corrupted after the day-one patch
• Steam DRM ticket failure when game is launched too quickly after Steam start
• IPv6 enabled at router level but disabled at game side, causing NAT mismatch

Step-by-step fixes

1. Check service status first. Visit status.ioi.dk, status.epicgames.com, status.playstation.com, and support.xbox.com/xbox-live-status. If any are red, the issue is server-side — wait for IOI's confirmation.
2. Restart EOS and clear token cache (PC). Quit the game, then delete the folder %LOCALAPPDATA%\EpicOnlineServices\IOI\007FL\ (Steam) or C:\Users\<you>\AppData\Local\EpicGamesLauncher\Saved\ (EGS). Relaunch — you'll be re-prompted to sign in.
3. Repair Easy Anti-Cheat. Navigate to Steam\steamapps\common\007 First Light\EasyAntiCheat\ and run EasyAntiCheat_Setup.exe. Select 007 First Light from the dropdown → Repair Service. Reboot.
4. Open required ports on your router. Forward UDP 5222, 5223, 9000-9100 and TCP 80, 443, 3478-3480 to your console/PC's static local IP. On PS5, this drops NAT to Type 2; on Xbox to Open.
5. Disable IPv6 at game side (PC). In Control Panel → Network → Adapter Properties → uncheck Internet Protocol Version 6 (TCP/IPv6). Many EOS deployments still fail when IPv6 is half-configured.
6. Steam: roll back to depot manifest 8094112233407. If patch 1.0.3 broke your auth, open Steam console with steam://open/console, then run download_depot 3247280 3247281 8094112233407 (the pre-patch build) while you wait for the hotfix.
7. Console: change DNS to 1.1.1.1 / 8.8.8.8. Settings → Network → Manual DNS. Many ISP DNS resolvers cache stale bondnetwork.ioi.dk records that point to retired matchmaking shards.
8. Reinstall the Microsoft Gaming Services package (Xbox app on PC). Run PowerShell as admin: Get-AppxPackage *gamingservices* | Remove-AppxPackage -AllUsers then reboot and reinstall from the Microsoft Store. Required if you use cross-play between Xbox app and Steam friends.

If it still doesn't work

If you've exhausted the steps above and the lobby still hangs at "Connecting to Bond Network", capture the EOS log at %LOCALAPPDATA%\007 First Light\Saved\Logs\EOS.log and the network trace from Resource Monitor → Network → 007FL.exe, then open a ticket with IO Interactive Support attaching both files plus your DXDIAG. Also confirm via ping bondnetwork.ioi.dk that DNS resolves to an IP block in the AWS us-east-1 / eu-west-1 ranges — if it resolves to an unexpected region, your ISP routing is the issue and you should test with a wired connection or a low-latency VPN (Mullvad WireGuard works without triggering EAC bans).