It's starting to get annoying.
In RedSec, the constant game crashes, endless loading screen freezes, keystroke issues, and many other bugs are becoming increasingly frustrating. If you don't fix them, you'll continue to lose players. Free alternatives don't have these problems; we buy the game and it has a great atmosphere, but the continuation of these issues is unacceptable.
Couldn't load some data
So apparently the problem started last night when I got kicked out of the game session and it sent me back to the login menu. I already tried to relaunch the game, restart the device as well as restore license but the same problem occurred as it says "Couldn't load". So please EA do fix this problem sooner because this problem has bugging me whenever I want to playConnection Failed 0:66003S:4688822970:0B + Unable to Submit Support Ticket
Hello, I’m getting a connection error when trying to launch the game. The message says: "Connection Failed – Unable to connect to the EA servers. Please check your Internet connection, make sure the Platform Client is online and try again." Error code: 0:66003S:4688822970:0B My internet connection is working properly. Other online services and games connect without any issues. I have already tried: Restarting the game Restarting the PC/console Restarting the router Checking that the EA App is online The issue still persists. Additionally, I’m unable to create a support ticket on the EA Help website. After I fill out the form and press Submit, the ticket does not appear in my case history. It looks like the submission is not being registered. Could you please advise: What this specific error code means How to resolve the connection issue Why support tickets are not being created in my account Thank you.Can’t connect to EA servers Error code 1:86001S:66003S:4688822970:0B
Hello, I purchased Battlefield 6 on Steam, but when I launch it, I get the following error message:Unable to connect to EA servers – Error code 1:86001S:66003S:4688822970:0B. I’ve already tried verifying the game files, clearing EA App cache, repairing and reinstalling the EA App, and restarting the EA Background Service (Javelin). None of these steps fixed the problem. Interestingly, if I install Battlefield 6 directly from the EA App, the game connects fine — but that version doesn’t detect my paid Steam license. This makes me think my Steam and EA accounts may not be linking correctly, or my EA Javelin authentication token is broken.Could you please help me by checking or resetting my Steam–EA account link, and/or refreshing my Javelin authentication data? Thank you very much for your help!
Two games linked to one account
I play battlefield on steam, with my EA account connected. I bought this game for my brother on Ps5, which is tied to a completely different email address. he has his own EA account and has never used mine ever. Somehow when he's launching battlefield 6 its tied to my EA account, and therefore we cant connect to each other. I don't know why it automatically linked to my account, but i need to figure out how to to get him on his own account.IP 15.197.149.64 accounts.grpc.ea.com rejects auths
EA Auth Server on AWS Global Accelerator rejects valid auth requests (IP 15.197.149.64 accounts.grpc.ea.com) Battlefield 6 Connection Failure from UK / Globally — accounts.grpc.ea.com DNS Resolution Bug Summary Battlefield 6 fails to connect ("Connection Failed") when DNS resolves accounts.grpc.ea.com to 15.197.149.64 (AWS Global Accelerator) as the primary IP. When the same hostname resolves to 99.83.166.42 (CloudFront) as the primary IP, authentication succeeds. The game always uses the first IP returned by DNS and does not fall back to the second on failure. Environment Game: Battlefield 6 (Steam, PC) OS: Windows 11 Pro (Build 26200) Network: All connections on the same LAN (192.168.1.0/24), same router, same DNS servers, same ISP Adapter: Realtek USB GbE (same physical adapter used in all tests) Reproduction The issue is reliably reproducible based on which IP address DNS returns first for accounts.grpc.ea.com: Network Path DNS Returns Server Used Auth Result Direct ethernet via switch 99.83.166.42, 15.197.149.64 99.83.166.42 (CloudFront) Success WiFi (direct to router) 99.83.166.42, 15.197.149.64 99.83.166.42 (CloudFront) Success Ethernet via powerline adapter 15.197.149.64, 99.83.166.42 15.197.149.64 (Global Accelerator) Failure Adding a hosts file entry to force accounts.grpc.ea.com to 99.83.166.42 resolves the issue on the failing network path. Technical Analysis Full packet captures (pcapng) were taken on all three network paths using dumpcap/tshark. The captures show: 1. The gRPC authentication exchange differs by server endpoint When connecting to 99.83.166.42 (CloudFront) — SUCCESS: Client sends 1273-1274 byte auth request Server responds with 527 bytes, then 380-381 byte auth response Client sends 366 byte follow-up Server returns 7081-7083 bytes of session/token data Game proceeds to Blaze redirector and game servers When connecting to 15.197.149.64 (AWS Global Accelerator) — FAILURE: Client sends 1225 byte auth request (48 bytes shorter) Server responds with 527 bytes, then 424 byte auth response (different from success) Client goes silent for 11 seconds Client retries with 1042 bytes Server responds with 113 bytes (rejection) Client sends RST, game displays "Connection Failed" 2. All other EA services work correctly on all paths eaanticheat.ac.ea.com — anticheat verification completes successfully cdn.eaanticheat.ac.ea.com — CDN downloads complete successfully gcs.ea.com — game config service connects successfully collector.errors.ea.com — error reporting works (contacted in both success and failure cases) All TCP connections establish correctly (SYN/SYN-ACK) All TLS handshakes complete successfully Zero packet loss on all network paths 3. The failure is isolated to the gRPC auth endpoint The only difference between working and failing sessions is which IP serves accounts.grpc.ea.com. The two IPs appear to behave differently: 99.83.166.42 (CloudFront): Returns valid authentication/session data 15.197.149.64 (AWS Global Accelerator): Returns a rejection response 4. No client-side network issues Network diagnostics confirmed identical configuration across all paths: Same IP address (192.168.1.241 on ethernet, 192.168.1.207 on WiFi) Same gateway (192.168.1.1) Same DNS servers Same routing table and interface metrics Same MTU (1500) Gateway latency: 1-2ms (ethernet), 3-25ms (powerline) — both well within acceptable range Impact Any player whose DNS resolver returns 15.197.149.64 as the first IP for accounts.grpc.ea.com will be unable to connect. DNS ordering can vary based on ISP, geographic location, DNS caching, and network path, making this issue intermittent and difficult for affected players to diagnose. Suggested Fix Investigate the 15.197.149.64 (AWS Global Accelerator) endpoint — it appears to return different/invalid auth responses compared to the CloudFront endpoint Implement fallback — if the first resolved IP for accounts.grpc.ea.com returns an auth failure, the game should retry with the next DNS result before giving up Verify both endpoints are serving the same gRPC service configuration Workaround Adding the following entry to C:\Windows\System32\drivers\etc\hosts forces the working endpoint: 99.83.166.42 accounts.grpc.ea.com Note: This IP may change over time as CloudFront rotates addresses. This is a temporary workaround only. Evidence Files The following packet captures are available to support this report: bf6_powerline_20260308_004544.pcapng — Failing connection (powerline path) bf6_ethernet_working_20260308_005300.pcapng — Working connection (direct ethernet) bf6_wifi_20260308_010049.pcapng — Working connection (WiFi) netdiag2_powerline_upstairs_2_20260308_001143.txt — Network diagnostics (powerline) netdiag2_ethernet_downstairs_20260308_001524.txt — Network diagnostics (ethernet)
