For Honor FAQ — Ping, Servers, Network

Yes. PingAim uses a kernel-level WFP driver to route For Honor's traffic through your chosen network interface. This is fully compatible with EasyAntiCheat — WFP operates at the Windows network stack level and EAC does not flag or interfere with it. PingAim detects forhonor.exe automatically and applies routing the moment the game launches.

For Honor migrated from peer-to-peer to dedicated servers on February 19, 2018. All PvP modes now run on Ubisoft's own dedicated server infrastructure across 8 global regions: Oregon (US), Virginia (US), São Paulo, London, Frankfurt, Singapore, Tokyo, and Sydney. Host migration no longer exists.

For Honor uses lag compensation on its server-authoritative netcode. When a player with 150 ms ping executes a parry, the server rewinds time to account for their latency before resolving the interaction. This means their input can register against your attack even though, on your screen, the parry window had already closed. Lowering your own ping does not eliminate this issue, but it levels the playing field and ensures your own reactions are processed as accurately as possible.

Under 60 ms is considered good for For Honor. Sub-40 ms is ideal and allows consistent reaction-based gameplay. Above 100 ms, parry windows become unreliable and you will begin to lose exchanges that should be reactable. Unlike many online games, even a 20–30 ms improvement is meaningful in For Honor because combat resolves at frame-level granularity.

For Honor does not show exact ping numbers in-game, but during a match you can press TAB to open the scoreboard and see color-coded connection quality bars for every player: green (good, roughly under 50 ms), yellow (moderate), and red (poor, 150 ms+). For an exact millisecond reading, use pingtestlive.com/for-honor — it pings each Ubisoft datacenter from your browser. You can also open Resource Monitor (Win+R → resmon → Network tab → filter by forhonor.exe) during a match to see real-time latency.

For Honor uses UDP ports 3074–3075 for game traffic, which may be blocked or restricted by your router's default NAT configuration. A Strict or Moderate NAT can cause matchmaking delays and force your connection through relay paths, adding latency. Fix: set up port forwarding in your router for UDP 3074 and 3075 pointing to your PC's local IP address. This opens a direct path to Ubisoft's dedicated servers.