Strict NAT

Why does my game or console show "Strict NAT" after using WTFast?

WTFast uses a Strict NAT by default, whether you’re using the PC Client or our Router integration. This isn't a bug; it’s a security measure to protect your network and ensure that only authorized traffic passes through our servers.

How this affects "Hosted" Games (P2P)

Because of these protocols, you might run into issues in Peer-to-Peer (P2P) games—specifically when one person is hosting for others.

In P2P modes, the game tries to create a direct connection between players. A Strict NAT can block those connections from forming. You’ll notice this most often in:

• EA Sports FC & eFootball: Mainly during casual or friendly matches.
• Call of Duty: Warzone & Battlefield 4: These games are sensitive to NAT types; a Strict NAT here can make it harder to join specific lobbies, find friends, or stay connected with your party.

The Situation If both you and a friend are using WTFast, one of you might not be able to join the other's hosted match. This is because both systems are filtering direct connection requests to keep the network secure.

The Fix In "Hosted" or P2P matches, the easiest way to stay connected is to have the host turn off WTFast. This lets your client (or router) focus on optimizing your route to the game's data centers without fighting the hurdles of a P2P handshake.