Battlefront 2 Error Code 721 | Fix Sign In Servers

Error 721 can feel random because the message looks the same in a lot of situations. The cause usually isn’t random. It’s one of four buckets: EA services are having trouble, your platform network is having trouble, your account session is stuck, or your home network is blocking the handshake.

The fastest way out is to test those buckets in order. Start with status pages, move to a clean sign-out and reboot, then work on the network path only if the quick wins don’t clear it.

What Error Code 721 Means In Battlefront 2

Star Wars Battlefront II needs a working EA session before it can load multiplayer, co-op, events, and anything tied to online progression. Error 721 shows up when that session can’t be created or can’t be refreshed.

The timing matters. If you get 721 right after launch or right after pressing Connect, it points to sign-in and session setup. If you can browse menus yet fail when searching for a match, NAT and routing issues jump higher on the list.

Common Triggers That Match 721

• EA service issue — EA account or game services are degraded, so sign-in requests fail.
• Platform outage — PSN or Xbox services are unstable, so your platform sign-in can’t stay steady.
• Stale login token — Your EA token or platform link needs a refresh after a password change or long gap.
• NAT or DNS trouble — Your network blocks required traffic, or your device resolves EA endpoints inconsistently.

Battlefront 2 Error Code 721 Fix Steps That Work

Do these in order. After each step, launch the game and try one clean connection. If it works, stop right there.

Check Status First

• Check EA Server Status — If EA shows an incident for your platform or account services, wait and retry later. EA Server Status
• Check PlayStation Status — If you’re on PlayStation, confirm services are green before changing any settings. PlayStation Service Status
• Check Xbox Status — If you’re on Xbox, confirm services are healthy, then retry. Xbox Service Status

If the status pages look fine and you still can’t connect, move to a full logout and reboot. That clears the most common “stuck session” cases without touching your router.

Reset The Sign-In Session

• Sign Out — Sign out of the EA app on PC, or sign out of the platform user on console, then restart the device.
• Sign In Again — Sign back in, open the launcher, then start Battlefront II and try to connect once.
• Confirm One Profile — Use the platform profile that’s linked to your EA account, not a second profile on the same device.

Do A Clean Network Restart

• Power Cycle Modem And Router — Unplug both for 60 seconds, plug the modem in first, then the router, then retry.
• Try A Different Path — Test wired Ethernet or a phone hotspot to see if the home network path is the blocker.
• Pause VPN Or Proxy — Turn off VPN and proxy tools, then try again.

If battlefront 2 error code 721 shows up only at certain times of day, your connection may be fine while the route to EA is not. A quick test is to run one match attempt on a hotspot, then one on your home line. Same account, same device, two paths. If one path works every time, you’ve got a clean target to fix.

Home Router Checks That Take Five Minutes

• Check For Updates — Log into your router and install any pending firmware update, then reboot.
• Disable Extra Filters — Turn off parental filters or ad-block features on the router for a test, then try connecting.
• Pause QoS Rules — If you use QoS or traffic priority rules, pause them briefly to see if they’re misclassifying game traffic.

Use This Table To Choose The Next Move

Once the basics are done, use what you’re seeing to pick the next step instead of guessing.

A good sign you’re done is a loop: you can reach the menu, connect once, join a match, then return to menus without getting kicked back to the login screen. If that flow holds for two launches in a row, stop changing settings on the network you play on.

Network Changes That Often Clear Persistent 721

If battlefront 2 error code 721 keeps returning and status pages are green, treat it as a network path issue. Make one change at a time, then test.

Switch To A Reliable DNS

• Set Public DNS — Use Google DNS (8.8.8.8, 8.8.4.4) or Cloudflare (1.1.1.1, 1.0.0.1) on your device or router, then reboot.
• Flush DNS On PC — Run ipconfig /flushdns, then restart the EA app and the game.
• Stick With One Setup — Remove “DNS booster” apps if you change DNS at the router, so results stay consistent.

Get NAT Out Of The Way

• Check NAT Type — On console, run the network test and confirm NAT isn’t strict.
• Enable UPnP — Turn on UPnP in your router so the game can request needed ports during matchmaking.
• Fix Double NAT — If you have two routers, bridge one of them so you don’t stack NAT layers.

Test IPv6 On And Off

• Toggle IPv6 — Disable IPv6, reboot, test Battlefront II, then turn IPv6 back on if it made no difference.
• Restart After Each Change — Reboots matter here since many routers apply IPv6 changes only on restart.

Allow The Game Through Local Security

• Allow In Windows Firewall — Allow Star Wars Battlefront II and the EA app on private and public networks.
• Pause Third-Party Firewalls — Disable extra firewall suites briefly to test, then turn them back on once you’ve added rules.

If you reach the point where port forwarding is the only thing left, keep it tight. Use UPnP first. If you must forward ports, forward only the ports listed for your platform and remove the rules once the issue is gone.

Platform-Specific Fixes

These are the steps that hit each platform’s login layer. They’re worth doing even if your internet looks fine, since 721 often starts with a token that won’t refresh.

PC

• Clear EA App Cache — Use the EA app cache clear option, fully exit the app, then sign in again.
• Repair Game Files — Run the repair option in the EA app, then launch the game.
• Run The Launcher As Admin — Start the EA app with admin rights, then start Battlefront II.

PlayStation

• Sign Out Of The User — Log out of the PlayStation user, restart the console, then sign back in.
• Retest Connection — Run the network test and confirm NAT isn’t strict.

Xbox

• Remove And Add The Profile — Remove the Xbox profile, restart, add it back, then retry.
• Clear Alternate MAC — Clear alternate MAC in network settings, restart, then test again.

Keep It Stable After You’re Back Online

Once you’re connected, a few small habits reduce repeat sign-in failures. This is the part most people skip, then the error returns on the next session.

Reduce Dropouts During Launch

• Use Wired When Possible — Wired links reduce brief Wi-Fi drops that can break session setup.
• Update Router Firmware — Keep firmware current so UPnP behavior stays consistent.
• Avoid Router Chains — Run one router in charge of NAT, not two.

Keep Login Tokens Fresh

• Close The Game Before Switching Users — End the session cleanly before changing platform profiles.
• Wait Between Retries — If login fails, wait a minute before trying again.
• Relink Accounts Carefully — Complete any relink steps in one sitting, then test once.

If all local steps fail and EA status is green, you’ve narrowed it down to an account-side flag or an ISP routing block. At that stage, use the official Battlefront II page on EA Help to reach account tools and contact options. Battlefront II on EA Help

When you’re troubleshooting again later, keep one sentence in mind: start with status, then session, then network. It’s the same order the game relies on to get you into a match.

Send us your feedbackTell us what you thought about this post

⚠Please use a real email you check. If it's fake or mistyped, your message won't reach us and we can't reply — wrong addresses are rejected automatically.

Name *Email *

Your comment *

Quick check — what is …? *

Send feedback