I purchased this to play online with my boyfriend it won't allow us to connect or play. Amazon won't refund a digital game purchase. Ea support is horrible they won't do anything. So basically I lost $40 on a game I can't play. My boyfriend lives away from me so we can't play it. I wasted my money on a game that EA should help fix problem since it's their issue. Nobody will help or refund. Error 10580190000 won't allow us to connect to EA servers. Nothing helps. Tried everything. Buyer please be aware do not buy. You can not play. I don't wish people to buy it and be out $40 like me on a game that can't be played.
Same issue here. Bought the game exclusively to play online and can't. Multiple threads on these forums show this has been a common issue for years with none of EA's proposed "fixes" working. So disappointing that this great game is tied to a company that's okay with ignoring its customers.
Community Managerdiglettusedfly LilacKoya Bassup
I hear what you’re saying, and I want to address this clearly.
There isn’t evidence of a widespread outage or a long-standing issue affecting all players trying to connect to EA servers for It Takes Two. If that were the case, it wouldn’t be working consistently for others across the same platform.
What is showing up in this thread -- and in similar cases -- is a pattern where the connection succeeds after switching networks (like using a hotspot) and then continues to work temporarily. That points much more strongly to a network routing or session initialisation issue, not a permanently broken online service.
The hotspot workaround isn’t random -- it forces a new connection path and refreshes how the session is established. When switching back to Wi-Fi, it then works, suggesting the initial connection handshake is what’s failing, not the game itself.
So rather than this being ignored, the challenge is that the issue isn’t consistently reproducible across all setups, which makes it harder to isolate without specific details.
If you’re still running into this, it would really help to narrow it down with a bit more detail:
Also, if the hotspot method consistently allows you to connect at least once, that’s a strong indicator your setup can connect -- it’s just failing during the initial network handshake on your default connection.
On refunds: I understand the concern, but purchases made through third-party retailers (like Amazon) are handled by them directly, not EA.
Let’s focus on isolating what’s actually causing the connection to fail so we can get you playing reliably.
Thank you for additional insight. I feel a lot of the frustration is stemming from this being an issue for several years with many threads here about it going unanswered, which led us to assume that EA was ignoring the problem.
I tried the hotspot/WiFi switch and here are my results:
To date, this is the only online game I've had a connection issue with. I've previously played through It Takes Two online on PS5 with no issues.
I’ve been having the same issue. I’ve emailed them multiple times but it seems like they have no idea what’s going on. They need to refund those that bought this solely to play online yet can’t. I’ve tried everything to get it working and still having the same issue weeks later. What a waste of money.
Community ManagerI understand how frustrating this is -- especially if you bought It Takes Two specifically to play together online.
To clarify, though, error code 105-80190000 isn’t a general server outage or a known issue affecting all players. It’s typically related to account setup or connection/authentication between your Nintendo and EA accounts. That’s why some players can connect without issues while others can’t.
Before assuming the game is unplayable, it’s worth double-checking a few things that commonly cause this:
I wouldn’t recommend unlinking accounts as a general fix here, as it can cause loss of access or progress and isn’t required for this error in most cases.
On refunds: purchases made through Amazon are handled by the retailer, so EA isn’t able to process refunds for those transactions directly.
If you’re still running into this after trying the steps above, share exactly what you’ve already tried and your setup (region, who is hosting, etc.). That makes it much easier to narrow down what’s actually causing the connection failure.
There is definitely a bigger issue here. The only solution that worked for me and a few other is the last option you listed above "Try connecting from a different network (for example, a mobile hotspot) to rule out a network-related block" but once it connects to the alternate network you can switch back to the wi-fi with no issues until the game is turned off and on again. However, don't expect to just start up and connect to alternate network/hotspot as that can also fail, but if you switch back to wi-fi after it fails it appears to connect on wi-fi then. There is definitely a bigger issue here. I played Split Fiction from start to finish with no issues with multiple start/stop sessions and enjoyed it very much!
Actually, I think there is a misunderstanding regarding how the networks are behaving (at least from my experience and maybe diglettusedfly can confirm it the same for him or not). The issue is not specific to my home Wi-Fi; rather, it happens on the initial connection attempt, regardless of which network I use.
Here is exactly how it behaves:
The failure often happens on the first attempt after the system is turned on, no matter which network I am using. It is the act of swapping networks that allows the connection to succeed, not the specific network itself.
Community ManagerThanks for laying this out clearly -- that behavior is important.
If the connection fails on the first attempt regardless of whether you start on WiFi or a hotspot, and then succeeds after switching networks, that points to something different than a specific ISP or router issue.
In this case, the consistent factor isn’t the network itself, but the initial connection attempt. The network switch is effectively forcing a fresh connection attempt, which is why it succeeds on the second try.
That explains why:
So this isn’t about one network “blocking” the connection -- it’s about how the connection is being established on the first attempt.
For now, the most reliable workaround remains:
If others are seeing the same “first attempt fails, second works after switching” pattern, feel free to confirm -- that helps separate this from standard network-specific issues.
Did some additional testing to see what worked and didn't, detailed below. These were all done one after the other.
This seems to support that we have one shot at connecting, regardless of the connection method (see 3 and 7) but have to restart for a connection change to "count" (see 4-6). The most reliable hack seems to be to restart, then change the connection method, then host a game (see 1 and 2). EA_Leeuw, is this helpful in getting closer to an actual fix?
For some bonus testing, I checked my Switch's WiFi NAT and got a B (Nintendo grades this from A to F, A being the best). I also tried a couple other non-EA Switch online games on WiFi and had no issues starting a lobby. If anyone has a different Switch EA game to test starting an online lobby, maybe that could also help narrow down the cause?
Hey, can you elaborate on your fix?
Are you completely exiting the game in between switching networks?
Or are you waiting for the initial 10580190000 error code to pop up, returning to the home screen without quitting the game, changing your network, and then returning to the game to try online again?
I'm facing this issue similarly to everyone else, however, the rare chances I've been able to actually establish a connection, I haven't been able to notice a pattern.
I’ve spent guts trying to get this to work and I’m having the same issue as everyone here. First try on each internet network allows me to login, but then I get the error.
The below are the same for me as listed by diglettusedfly
I have rebooted routers and switch and cleared cache and tried all the things listed but at this point nothing is working to get to the online game.
usa, switch 2, it takes two full game (not friend pass), trying to play online with my 9 year old nephew in another state also on a switch. We enjoyed it when we were able to get in the first time we tried but now we’re unable to play.
I keep getting this error code. I've looked through other forums to find fixes tried everything I could find (restarting the system, cleared the cache, restarted my router, used a wired connection, using a Hotspot for a different network connection) it all leads back to the same 105-80190000 error code. I dont know what else to do. I'm halfway through the game at this point so I don't know why this is happening now.
I have also been consistently having this issue. It's total BS. EA tries to shift the blame onto Nintendo but its obvious, seeing as connectivity issues are present across platforms, that the primary fault lies with EA and their lousy networks.
This game SHOULD NOT have been advertised with online functionality as it clearly DOES NOT WORK MAJORITY OF THE TIME.
To anyone troubleshooting this issue: ‼️GET YOUR MONEY BACK‼️ DO NOT SUPPORT THIS COMPANY and their false advertising!
Update: the Hotspot fix worked, but only if I fully removed my wifi network. I still do not know what caused the issue in the first place
I’m also having this issue. Based in the US (before i get asked about a region).
I have tried
Ive played this game on the PS4 and completed the game with zero issues. I got the full game to play with someone else on the nintendo switch and halfway through the game it’s stopped working and i’m getting that error code. I’m so confused, if I try to refund it or whatever I’ll lose all my progress. What can I do to fix this???
In the exact same boat as you. Have spent hours trying to figure out how to fix this with no solution. We have been able to connect previously. So clearly an issue with EA.
EA_Leeuw, I also began running into this issue as a full block on April 11th 2026 and I decided to do a more detailed analysis of the traffic over my network to have a better understanding of the root cause of the issue because it occurs on both Home Networks and Hotspots intermittently while happening much more often on non-hotspots (as observed/noted previously).
BACKGROUND
I ran into the 105-80190000 error from the first day I bought the game in mid-late February 2026, but it would typically let me create a session after rebooting my console 1-3 times while still using my WiFi, so I didn't think too much of it, but after I reached Chapter 6 I was unable to get past the error even after many restarts.
This is what I've concluded from my analysis:
This is not particularly a client-side network issue, or an ISP/firewall blocking the handshake; rather there is an issue with the response time of EA backend infrastructure and it should probably be escalated to your infrastructure or backend engineering team for review.
MY SYSTEM INFORMATION
Platform: Nintendo Switch
NETWORK DETAILS
To play the game I use an AT&T Router linking to Fiber Internet
NAT Type: B
All testing was done using Raspberry Pi as an access point with an ethernet uplink/WiFi uplink to the same AT&T Router or mobile hotspot uplink also AT&T based. No changes were made to the network/firewall, all alterations to speed were run through the Raspberry Pi as it intercepted traffic and then forwarded it to the Mobile Hotspot/AT&T Router.
Networks tested:
SUMMARY OF FINDINGS
Online session creation fails due to a race condition in EA's backend session preparation pipeline. The Switch reaches the Blaze session server and completes authentication faster than EA's backend finishes preparing the session. When the Switch presents its auth result to the Blaze Server, EA's backend is not yet ready to validate it, returns an unexpected response, and the Switch aborts the connection with a TLS Encrypted Alert.
Artificially slowing the network connection (adding 30ms and 50ms and 75ms latency via Linux traffic control) improved the success rate from ~2% on base ethernet to ~40% with a 30ms delay added and then 100% with 75ms added. So higher natural/artificially added latency confirms that connection speed — not network configuration — determines the outcome. I ran 100 tests across the three network settings mostly with my natural ethernet based connection.
Here's the breakdown:
Notice that slower connections using a cellular/hotspot connection or WiFi work because they give EA servers time to respond when the Switch expects and create the session correctly. Ethernet connections were 100% successful with artificial latency of 75ms added, but it improved as more latency was added when it almost never worked with its natural low latency.
RACE CONDITION EXPLANATION
The bug is a timing dependency between two EA backend systems:
1. The Blaze session server accepts the connection and begins session setup
2. EA's auth backend (accounts.ea.com coordination) prepares the session credentials in parallel
On low-latency connections the Switch completes its auth steps and returns to the Blaze Server before the auth backend finishes. The Blaze Server receives the Switch's auth presentation but cannot validate it because the backend preparation is not complete. It returns an error response, the Switch sends an Encrypted Alert, and the session fails.
On high-latency connections the additional network delay gives EA's auth backend enough time to finish. The Switch's auth presentation arrives after the backend is ready, validation succeeds, and the session completes. This is consistent with all observed data across 100 captures.
EVIDENCE AVAILABLE
I have the following available to share upon request:
I am happy to provide any of these to your engineering team, but they may also be able to reproduce the behavior detailed above on their own just from this information.
Thank you for your time and attention to this. I hope this report helps your team identify and resolve the issue for all affected players.
Edit-
Adding some detail about the flow of network traffic during the failures/successes:
DETAILED FAILURE SEQUENCE
Every failed session follows this exact sequence:
1. Switch queries spring18.gosredirector.ea.com and is assigned a Blaze Server
2. Switch initiates TLS connection to assigned Blaze server — handshake completes successfully
3. Initial Application Data exchange occurs between Switch and Blaze Server
4. Switch simultaneously contacts accounts.ea.com, qoscoordinator.gameservices.ea.com, Nintendo auth servers, and other EA services during a multi-second gap
5. Switch returns to Blaze Server with auth result
6. Blaze Server responds with Application Data
7. Switch immediately sends a TLS Encrypted Alert — indicating it received an unexpected or invalid response
8. Switch sends TCP RST to Blaze Server
9. Blaze Server sends FIN ACK (terminating the connection to the Switch)
10. Session creation fails and players get the "Account settings has changed..." error message.
In successful sessions, Step 7 does not occur, instead, the Switch receives a valid response and the Application Data exchange continues for ~2-3 additional seconds until the session is fully established.
Also, "Blaze Server" refers to any of the following 4 servers as the Switch may be assigned to any one of the four after being redirected by spring18:
These servers are present across failures and successes pointing towards this being a backend timing issue, and not a server health issue as they wouldn't work at all if there was a health issue. They just need more time than our connections give them to handle the authentication/session creation correctly.
In my experience with this error, the manipulation of the speed of the network proved to be the only fully reliable way to avoid the issue. Outside of my recorded testing I had more success creating a session with my phone's hotspot, but like others, it still doesn't work some portion of the time because the speed of the network is variable, so without forcing it to be slower you're just gambling with better odds when using a hotspot...it seems like a fix but it is actually just masking the issue.
Please help get this information into the right hands, so we can get past this error once and for all.
Patient_Poetry you deserve a big pay check from EA for doing their QC/QA/test job. 😄
You go girl
Incredible work and I was able to prove your findings by using Clumsy (network throttling software) on Windows. Thanks again for all your effort and happy than I can finally play this game :)
TEMP FIX for It Takes Two Switch - Account Changed Error - 105-80190000 | EA Forums - 13435627
Thanks, I'm glad that my testing helped. Hopefully others will be able to use your workaround until EA addresses the root issue.
Wanted to note and flag I'm hitting this same issue. I'll try looking into throttling my Network, but I'm hopeful a real fix can be rolled out sometime...
I'll note that I reached out to Hazelight on X to see if we can get their attention (https://x.com/_niallis/status/2076171160505696470?s=20). I imagine as the developer they care more about folks being disappointed they can't play the game than EA is themselves.
