Known Lag Problems
These problems are reported by real players. If your region or ISP is listed, a network optimizer is likely to help.
Eastern Europe
60-180ms to EU West AWS- Relic officially acknowledged and investigated Eastern Europe-specific connection issues post-launch
- ISP routing to AWS EU West from Eastern Europe passes through multiple transit handoffs, adding latency and jitter
- Lockstep simulation amplifies jitter — brief routing instability causes visible simulation pauses for all players
Southeast Asia
50-200ms to SEA AWS (higher if cross-region matched)- SEA server confirmed available but smaller player pool than EU/NA means cross-region matchmaking is common
- Cross-region lockstep with EU or NA results in 200-350ms effective input delay
- ISPs in Philippines and Indonesia route suboptimally to AWS Singapore
South America (outside Brazil)
150-280ms to US East or EU West AWS- No dedicated CoH3 server in South America — players route to US East or EU West with 150-250ms
- Small player pool leads to cross-region matchmaking adding additional latency on top
- Lockstep simulation stalls caused by jitter on transoceanic ISP links
How to Fix It
Try these first — they're free and solve the problem for most people.
01 Check your current ping to Relic servers before each session
1. Open Command Prompt 2. Run: ping -n 10 aws.amazon.com 3. Note the average and the variation between individual pings (jitter) 4. If average is above 150ms or variation is above 30ms, your routing path to AWS may be suboptimal 5. Try running the same ping while on WiFi vs. while tethered to your phone — compare results 6. The connection with lower and more consistent ping is your better CoH3 interface
Identifies if your current network path to Relic's AWS servers is causing lockstep delays. Reveals jitter issues that won't show up in simple ping tests.
02 Switch to Ethernet and eliminate WiFi jitter
1. Connect your PC to your router with an Ethernet cable 2. In Windows Settings > Network & Internet, disable your WiFi adapter 3. Launch CoH3 and start a multiplayer match 4. Observe if the periodic freezes or simulation pauses disappear 5. WiFi interference — even brief 2.4GHz congestion — causes packet delay that stalls lockstep for all players
Eliminates the primary cause of lockstep simulation stalls for WiFi users. A single WiFi packet delay can freeze the game for everyone in your lobby.
03 Close background applications before ranked matches
1. Pause downloads, close streaming services, disable cloud sync (OneDrive) 2. Close Discord if you're not using voice — use Discord on your phone instead 3. Launch CoH3 last 4. Even brief bandwidth spikes cause packet delay in the lockstep model, stalling the match for all players
Prevents bandwidth competition that causes the lockstep simulation to pause for all players in your match
General network tips (not Company of Heroes 3-specific)
04 Open Steam ports in Windows Firewall
1. Open Windows Defender Firewall with Advanced Security (search in Start) 2. Create Inbound Rules for: - TCP ports: 27015-27030, 27036 - UDP ports: 27015, 27031-27036 3. Restart Company of Heroes 3 4. This ensures no firewall interference with the Steam networking stack CoH3 uses
Resolves connection failures and NAT issues that can cause the match to stall while waiting for packets that are being blocked.
05 Flush DNS and reset network stack
1. Open Command Prompt as Administrator 2. Run: ipconfig /flushdns 3. Run: netsh winsock reset 4. Run: netsh int ip reset 5. Restart your PC 6. Reconnect and test CoH3 multiplayer
Fixes sudden connectivity degradation from stale DNS entries or corrupted network state. Quick 2-minute fix that sometimes resolves persistent Relic server connection failures.
06 Verify Relic server status before troubleshooting
1. Check https://downdetector.com/status/company-of-heroes-3/ for reported outages 2. Check the official CoH3 community forums for maintenance announcements 3. During server-side issues, no client-side fix will help 4. Eastern European players: Relic has acknowledged historical connection issues in that region — follow official forum announcements
Confirms whether connectivity issues are on your end or Relic's. Saves time by ruling out server-side causes before adjusting your network.
Still lagging? The problem is likely your ISP's routing to the game servers.
PingAim detects Company of Heroes 3 automatically
No manual config. PingAim identifies Company of Heroes 3 by process name and routes it through your fastest connection using a kernel-level WFP driver.