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

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.

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,

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 😆

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

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.

me too :)

That's so interesting that more and more ppl are getting it. Like I said before to others its spreading. Ur like the 6th new person today iv seen on here with it

never had connection problems since the launche, before 30 min ago... [removed] EA !

(cm edit removed language and caps)

Hi, have a troubleshoot file composed but for some reason can't DM

Sooo, should I free up my weekend like I did last time or I'm going to be disappointed yet again? This is ridiculous...