Persistent host migration error and cross-play disconnections in F1 25
Hello,
I am experiencing a persistent multiplayer connectivity issue in F1 25 when playing on Xbox Series S with a friend on PS5 via cross-play. The main issue occurs in Two-Player Career mode. I am repeatedly disconnected and returned to the main menu with the following error message:
“Unable to transition after host migration.”
My friend remains in the race, and this happens almost every time, regardless of who creates the career. We have created four separate Two Player Careers, but the issue persists in all of them.
We have already tried the following troubleshooting steps:
-Opened the NAT on my Xbox.
-Restarted the Xbox and router multiple times.
-Changed DNS settings from Google DNS to Cloudflare DNS on both consoles’ respective networks.
-Tested the game using my phone’s mobile hotspot instead of my home Ethernet connection.
-Reinstalled F1 25.
- Tested the career with both me and my friend acting as host.
None of these steps has permanently resolved the issue.
We also tested a normal online multiplayer lobby, created by me with only the two of us and no AI. The 10-minute qualifying session completed without problems. However, during the 20-lap race, around lap 9, my friend was disconnected from my session and received a message saying that I had left. Both of us remained in the race locally, but we were no longer in the same session.
After that test, we tried Two-Player Career mode again, and I was disconnected once more.
Six months ago, we played the same game together and completed 16 races in Two-Player Career without any connectivity issues. Our internet connections have not changed since then.
Given that the issue persists across multiple careers, different DNS settings, Ethernet and mobile hotspot connections, and even after reinstalling the game, I suspect a possible multiplayer session, host migration, or cross-play synchronization bug.
Could you please investigate whether this is a known issue and advise whether there is a confirmed workaround or a planned fix?
Thank you.