Host Migration message.


Connection lost message after a failed host migration.

Multiplayer sessions in WARFRAME are hosted peer-to-peer (P2P), meaning a single person is selected by the game to be the host of a particular session. Any additional players who join that session will be connected to the host player's machine. Host migration is the consequence of a drop in connection from the host, forcing the game to choose another player in the same session to be the host instead. If a host migration is successful, the remaining players will continue the session, retaining rewards and progress made (to a certain extent). However, if a host migration fails, all players will be taken back the Orbiter, potentially losing rewards gained in that session.

Players in Solo matchmaking won't experience host migration as they host the sessions themselves.

Situations That Lead to Host MigrationEdit

  • When host player extracts in Defense missions after the end of a rotation.
  • When host player doesn't continue through the portal during Sanctuary Onslaught and Elite Sanctuary Onslaught.
  • When host player performs an individual extraction during Survival, Excavation, and Defection missions.
  • When host player aborts the mission through the menu.
  • When host player Alt + F4  to exit out of WARFRAME, the game crashed, or system shutdown.
  • When host player gets captured by Zanuka Hunter.

If Host Disconnects During Endless MissionsEdit

Rotation rewards during endless missions (Defense, Survival, Interception, Excavation, Disruption, etc.), including opening Void Relics during Void Fissures, can be recovered by the game if a host migration fails. Ordis may send a message to disconnected players, containing 'lost' rewards up the rotation before they disconnected:

Items Recovered


Items were dropped during your extraction and have been retrieved for you.

Diagnostic repairs are now underway, Ordis is certain this probably won't happen again.

These items have been delivered to your inventory.

—Orbiter Systems

(Attachments: Lost rewards)

Any picked-up Resources, Mods, and Ayatan Treasures and Affinity earned by equipment will be lost upon a failed host migration since these rewards are determined client-side, not server-side, which means that the game's servers cannot verify their existence, leading to the loss of these.


  • The host player will always be denoted by a "1" next to their name in the player list sidebar (default key to toggle Z ).


  • Rarely, host migrations would result in joining a completely different session from the one the player was currently in, across different missions types even.

Patch HistoryEdit

Hotfix 28.0.5
  • General stability changes towards Railjack missions when a Host migration occurs. This touches on issues related to Crewships not spawning after a Host migration, and crashing when a Crewship spawning triggers a Host migration.

Update 27.2

  • Fixed progression stopping bug if a Host migration occurred after the first radiator has been exposed on a Pulse Turbine POI, and players then proceed to destroy the exposed radiators.
    • After the Host migration, both radiators would be visible and vulnerable, at which destroying both of them would leave the mission broken due to having nothing to destroy after hacking the second console for the second radiator.
  • Fixed script error with host migration after exiting Railjack.
  • Fixed Kuva Larvling not spawning Kuva Lich if downed before Host migration and captured after Host migration.
  • Fixed Clients in The Index losing all functionality asides from the pause menu if they die and Host migration occurs before they are able to respawn. As reported here:
  • Fixed script error that would occur in the Transmission scripts during a Host migration.

Hotfix 27.1.2

  • Fixed numerous issues if a Host migration occurred during a Kuva Lich mission:
    • Fixed getting stuck on the Vanquish/Convert screen if a Host migration occurred while a Client is Vanquishing their Kuva Lich.
    • Fixed Clients able to kill a recently migrated Host’s Kuva Lich, resulting in 1,200 Kuva being rewarded, as well as being able to see the Lich's head mesh idling/walking in place after defeat. As reported here:
    • Fixed broken reward UI after a Host migration occurs.
    • Fixed Parazon being stuck equipped after a Host migration occurred during a Kuva Lich Kill attempt.

Update 22.4

  • Fixed the remaining Client post-Host migration joining the Client who left the squad instead of the new Host in the Plains.

Hotfix 22.2.5

  • Fixed experiencing a massive hitch as the Client when a Host migration occurs in the Plains.

Update 15.9

  • Fixed general issues that would occur during Archwing Missions during host migration.
Community content is available under CC-BY-SA unless otherwise noted.