BARO  Next: Fri, Sep 18 at Larunda Relay (Mercury)
NEXT  Citrine Prime + Iceblade of Narin, Sept 23
STATE  Guides verified against Update 43
Home Guides Warframe High Ping, Lag and Host Migration Fix (2026): Ping Limit, Region, UPnP and Ports
warframe.today

Warframe High Ping, Lag and Host Migration Fix (2026): Ping Limit, Region, UPnP and Ports

Enemies teleporting and host migrations: the ping limit, region, UPnP and the exact ports

Last Updated on September 14, 2026

The short answer

Warframe missions are hosted by a player, not a server, so lag is the host’s connection plus yours. Set the Matchmaking Ping Limit to 150 or lower so you only join nearby hosts, pick your Region, turn on UPnP in game and on the router, and fix a Strict NAT with the port list below. Host migrations happen when the host leaves; hosting yourself (solo or invite only) ends them.

Reviewed September 14, 2026, against the current Settings menu (Update 43.5) and the official support articles; this page is re-checked after every major patch.

Setting or checkWhereWhat to set
Matchmaking Ping LimitOptions, Gameplay100 or 150; No Limit is why you get 400 ms hosts
RegionOptions, GameplayYour continent; it also picks your chat region
UPnP and NAT-PMPOptions, SystemOn, and on the router too; Strict NAT means one of them is off or blocked
Show FPSOptions, DisplayOn: it prints your ping to the host
ConnectionPhysicalWired beats Wi-Fi; Wi-Fi on a Steam Deck wants 5 GHz
FirewallWindows and any third-partyExceptions for Launcher.exe and Warframe.x64.exe

If UPnP fails: forward these ports

  1. PC (standalone launcher): TCP 6695 to 6709; UDP 4950 and 4955.
  2. PC via Steam: add TCP 27015 and 27036; UDP 27015 and 27031 to 27036.
  3. PlayStation: TCP 3478 to 3480 and 6695 to 6709; UDP 3074, 3478 to 3479, 4950, 4955.
  4. Xbox: TCP 3074 and 6695 to 6709; UDP 88, 500, 3074, 3544, 4500, 4950, 4955.
  5. Nintendo Switch: TCP 6667, 6695 to 6709, 12400, 28910, 29900 to 29901, 29920; UDP 1024 to 65535.
  6. After forwarding manually, turn UPnP off in the game and on the router so the two do not fight; DE's own guide says so.
  7. Give the PC a fixed local IP first, or the forward points at the wrong machine after a reboot.

Host migration, explained

  • The host is the player whose PC runs the mission. When they leave, the game picks a new host and everyone reloads: that is the migration.
  • To never migrate: play solo, or host with Invite Only and friends joining you.
  • A bad host shows as high ping in Show FPS while your own speed test is fine. Leave and re-queue; the ping limit stops it recurring.
  • Cross-platform squads add the other platform's hop; turn off Cross Platform Play in Gameplay if your region is thin on hosts.
Still dropping frames? Our own tool

CPUCores — Maximize Your FPS

If you’ve worked through the settings above and still get stutter, the bottleneck is often background processes stealing CPU time from the game. CPUCores isolates Windows and background tasks onto separate cores so your game gets the rest — it launches straight from Steam and detects your library automatically.

CPUCores video thumbnail
View CPUCores on Steam Heads up: CPUCores is made by the same people who run warframe.today, so we’re not a neutral party here. Results vary by CPU and by game — check the Steam reviews and refund policy before you buy.

Tips that save runs

  • DE's Basic Network Troubleshooting guide covers the rest: restart the router, drop VPNs and proxies, disable IPv6 tunneling adapters, try bypassing the router briefly to isolate it.
  • Double NAT (an ISP modem plus your own router) defeats UPnP; put the ISP box in bridge mode or forward on both.

Mistakes that waste runs

  • Setting the ping limit to No Limit for faster queues, then playing at 350 ms.
  • Forwarding ports and leaving UPnP on.

Related