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

guys I can't believe all these attempts and solutions were useless, I looked at all my usb ports and noticed that there is a usb This usb was for the screen that came with the aio liquid cooler that i can show pics or videos or anything but i forgot i had to take the usb that came with it and plug it on the motherbord .I have temporarily disabled it from the driver manager. and the game workkkssss its woorkkk I turned it on again and had the same error , open my pc crach the screen and try again its working without any errors . pls try to look at the driver manager and see if you have and usb or External hard drive just disabled it and try maybe its will fix yours guys

I’m in the same boat, I have enabled secure boot and TPM 2.0 and I cannot have it play I now get the “unknown error” after playing 4mins into my first match after launching the game and I get kicked and keep getting kicked the game is unplayable for me. I too had this problem in the beta reached out but the staff or support couldn’t solve my issue I’m at a lost n probably gonna have to refund this game or something

Don't retry too many times guys, your account will be flag as bot and be locked permanently...

Hi everyone,

I’ve been investigating this issue and found that it’s not a server outage — it’s a DNS routing problem.

During the Open Beta, Battlefield 6 used public regional servers that didn’t depend heavily on DNS lookups.
But after the full release, EA switched to a global authentication and matchmaking system hosted on AWS / Akamai.

Many ISPs or routers assign internal/private DNS (for example 10.x.x.x or local resolvers) that cannot reach EA’s global domains like ea.com or origin.com.
That’s why the game fails to connect even though your Internet is fine.

1.The issue isn’t EA’s servers — it’s DNS and routing.

When Battlefield 6 tries to connect, it first contacts EA’s global authentication system.
If your DNS (the system that translates web addresses into real IPs) can’t find those EA servers,
the game instantly fails to connect — even if your Internet is perfectly fine.

2.Different network setup between Beta and Full Release

During the Open Beta, EA used public regional servers (like in Singapore or Japan).
Those were easy to reach even with local ISP DNS.
But after the full release, EA switched to a global authentication and matchmaking system hosted on AWS and Akamai.
That system requires a proper public DNS to reach those global addresses.

3.Private/internal DNS servers can’t reach EA’s global endpoints

Some ISPs and routers assign private DNS servers (for example addresses starting with 10.x.x.x).
These internal DNS servers only work within the provider’s own network and cannot resolve global domains like ea.com or origin.com.
So when the game asks “where is EA’s login server?”, those private DNS simply don’t know the answer.

In summary
The Beta worked because it used public regional servers.
• The full release fails because it now uses a global authentication system that depends on proper DNS resolution.
• Some local/private DNS can’t reach EA’s domains.
• Changing DNS to Cloudflare or Google fixes the issue instantly.

Idk none of those options in changing the DNS worked for me and this issue has been happening since the beta for me

Not sure about the google one, because I manualy set it from 8.8.8.8 to 8.8.4.4 in the DNS settings for me, but it doesn't work

Only cloudfare working for now

This is effectively what I am experiencing. EA account on their side has no flags on my account, but under security and privacy, I downloaded my account info and it says "account_abuse". This makes no sense at all. I have done nothing abuse and have done nothing against the UA or TOS. 

EA/BF need to get on this ASAP, I am seeing more and more reports here, Steam, and Reddit of people experiencing actual false bans. This is very disappointing.

Hi everyone,

I’ve been investigating this issue and found that it’s not a server outage — it’s a DNS routing problem.

During the Open Beta, Battlefield 6 used public regional servers that didn’t depend heavily on DNS lookups.
But after the full release, EA switched to a global authentication and matchmaking system hosted on AWS and Akamai.

Many ISPs or routers assign internal/private DNS (for example 10.x.x.x or local resolvers) that cannot reach EA’s global domains like ea.com or origin.com.
That’s why the game fails to connect even though your Internet is fine.

1. The issue isn’t EA’s servers — it’s DNS and routing.
When Battlefield 6 tries to connect, it first contacts EA’s global authentication system.
If your DNS (the system that translates web addresses into real IPs) can’t find those EA servers, the game instantly fails to connect — even if your Internet is perfectly fine.

2. Different network setup between Beta and Full Release
During the Open Beta, EA used public regional servers (like in Singapore or Japan). Those were easy to reach even with local ISP DNS.
But after the full release, EA switched to a global authentication and matchmaking system hosted on AWS and Akamai.
That system requires a proper public DNS to reach those global addresses.

3. Private/internal DNS servers can’t reach EA’s global endpoints
Some ISPs and routers assign private DNS servers (for example addresses starting with 10.x.x.x).
These internal DNS servers only work within the provider’s own network and cannot resolve global domains like ea.com or origin.com.
So when the game asks “where is EA’s login server?”, those private DNS simply don’t know the answer.

In summary:
- The Beta worked because it used public regional servers.
- The full release fails because it now uses a global authentication system that depends on proper DNS resolution.
- Some local/private DNS can’t reach EA’s domains.
- Changing DNS to Cloudflare or Google fixes the issue instantly.

For reference, many users across different ISPs have confirmed that switching to Cloudflare (1.1.1.1) or Google DNS (8.8.8.8) resolves this error.
Please investigate the DNS routing for Battlefield 6 authentication servers.

Thank you.

EA PLEASE FIX IT TODAY THE WEEKEND IS ALMOST OVER.. 

I love to see this is being looked at.  I’ve re installed the game, steam, hard reboot my PC and router, and still the same. Looking forward to playing. Hopefully.