Forum Discussion

New Rookie

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

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.

3 Replies

MetHeePong
New Rookie
3 months ago
Update:
After further testing and feedback from other players, it seems that changing DNS (to Cloudflare or Google) doesn’t fully solve the issue for everyone.
Some players can connect with Cloudflare, while others still face the same “Connection Failed” error regardless of DNS changes.
This confirms the issue is likely on EA’s side — possibly related to how Battlefield 6’s global authentication servers route traffic through certain regions or ISPs.
For now, we’re waiting for EA’s technical/network team to investigate and deploy an official fix in an upcoming update.
If anyone receives updates or patch notes addressing this, please share here.
zo0-Y0rk
Rising Rookie
3 months ago
What router model do you have?
dndhmmm
Rising Newcomer
3 months ago
I’m suddenly experiencing this issue today, after being able to play the game without issues daily since launch. I even played a couple of matches before work this morning, but have been unable to connect since lunchtime. Nothing has changed on my network, so can only assume it is my ISP’s DNS. If run Cloudflare Warp (VPN), I am able to connect, but this is not a sustainable solution to the issue.