"Connection Failed" With Error Code 1:86001S:51002S:57019S

me too :)

I know this doesn't exactly help, but:

The EA servers they’ve asked us to trace are hosted on AWS in Europe, while the CDN is on Akamai. For me, the Akamai trace resolves fine, but the EU-AWS one doesn’t. That tells us we’re now at the level of behemoth-to-behemoth communication.

I work in IT at a large enterprise, where we have a document known as an SLA (Service Level Agreement). It’s a standard concept — essentially, the rules that dictate how quickly one company must fix something for another. What’s likely happening right now is that EA has engaged AWS to investigate. Since this isn’t a total outage, it’s unclear how AWS is prioritizing it.

Change management becomes complicated when dealing with networks of this size, and the ones I handle are relatively small by comparison. Depending on the priority level, it could take AWS weeks or even months to resolve this — not because EA doesn’t care, but because their contract might not make this issue a top priority.

On top of that, AWS has to reproduce the problem in a non-production (testing) environment before it can safely make changes. So, in short: EA needs to prove there’s a problem (that’s why we’re sending traceroutes), AWS has to reproduce it, then get approvals to update the affected network paths surgically. We might be here a while.

I don't know EXACTLY if this is what's happening, and the fact is, the CMs probably can't tell us, but based on my experience, this is the shape of these types of things.

**bleep** so we will be here for awhile 

I can agree with that asnwer since i do IT myself and EA has moved much of its server infrastructure to AWS for hosting game servers and backend services. Akamai is a CDN provider which is used for making game updates, patches and yes staff often can’t share detailed backend information, either because they don’t have it or due to company policy so i see why they been telling us soon all the time 😆

I have the same error, the only consistent part I can find is there is another computer in on my network who also has the game and if we try to log on at the same time one cannot play. so only one person at a time on the same network seems to also be a ting. Not saying thats what everyones got but seems to be happening my side,

Me and my brother have this exact same issue, only one of use can connect at any one time. Apparently it's some nonsense to do with how EA recognises players by their ip so only one person can connect from a single network which is ridiculous issue for such a big company to have. It's 2025 and we can't even play the singleplayer campaign at the same time even though we've both purchased the game separately it's a joke. Tried all sorts of port forwarding and router settings but nothing works.

Can’t even get to the menu screen on Battlefield 6 on the playstation 5. i have tried everything, everything and it won’t let me in. did all the steps plus a bunch more

Hi,

I’m also experiencing the same issue — “Connection Failed” with error code:
1:8600:15:5100:2S:57019S
after the game queues for a few seconds.

My system is fully compatible and meets all security requirements:
– Windows 11 Pro (Build 26100.689)
– Secure Boot: ON
– TPM 2.0: Enabled (PTT mode)
– UEFI boot
– Intel Core i7-13700K
– Gigabyte B660M DS3H AX DDR4 motherboard
– EA App (latest version)

EA AntiCheat is installed correctly and runs fine with --run-as-service (exit code 0).
However, the Windows service EAAntiCheatService fails to start through Service Control Manager with error 193.

I’ve already tried:
– reinstalling Battlefield 2042 and EA App,
– clearing cache,
– resetting network stack,
– running both as administrator,
– testing with Cloudflare WARP and Proton VPN.

None of these helped — the issue persists exactly as described by others.

It seems that the Javelin AntiCheat authentication service is failing on EA’s backend, as all local checks pass successfully.

I’ve never been able to play the game after getting this message for 5 hours straight. On ps5

same problem, every 5-7 mins, disappointed EA