Known Lag Problems
These problems are reported by real players. If your region or ISP is listed, a network optimizer is likely to help.
Australia / Oceania
80-120ms to Singapore; 180-220ms to Oregon- No dedicated Oceania server — Australian players must connect to AP Southeast (Singapore) or US West (Oregon) after 2025 merges
- Baseline ping from Sydney to Singapore ~80-100ms; to US West Oregon ~180-200ms
- After July 2025 merges folded most AP Southeast servers into US West, many Australian players now face 180-200ms as their best option
- Some Australian ISPs (Telstra, Optus) have suboptimal routing to both AWS ap-southeast-1 and us-west-2, adding 20-40ms above geographic minimum
Southeast Asia
30-80ms from Singapore/Malaysia; 80-150ms from Philippines with ISP routing issues- AP Southeast server retains only 1 world after July 2025 merges — queue populations very low
- Most SEA players may find better matchmaking by connecting to US West despite higher ping
- Philippine ISPs (PLDT, Converge) often have poor routing to AWS ap-southeast-1 Singapore, adding 30-60ms above geographic minimum
- Indonesian ISPs also report elevated ping to Singapore AWS endpoints versus expected geographic baseline
South America (excluding Brazil)
80-150ms to US East from most SA countries- SA East retains only 1 world after July 2025 merges — queue times very long
- Most non-Brazilian SA players now connecting to US East (Virginia) after merges
- Geographic distance from Colombia, Chile, Argentina to Virginia adds 80-120ms baseline
- South American ISPs often have poor peering with US East AWS endpoints
- Players in western SA (Colombia, Peru, Chile) sometimes find US West (Oregon) gives lower ping than US East
Eastern Europe / Balkans
40-100ms to Frankfurt depending on country and ISP- EU Central server is in Frankfurt — Eastern European countries have longer geographic paths to Frankfurt
- Some Eastern European ISPs route through Western Europe before reaching Frankfurt AWS, adding extra hops
- Players in Ukraine and Belarus face 60-100ms to Frankfurt depending on ISP international routing
How to Fix It
Try these first — they're free and solve the problem for most people.
01 Check your Input Latency with the in-game overlay
1. Launch New World: Aeternum 2. Press F11 during gameplay to open the performance overlay 3. Look for 'Input Latency' (ms) — this is your real-time ping to the server 4. Alternatively: Esc → Settings → Video → enable 'Show FPS' for a persistent top-left display 5. Note whether your latency is stable or spiking — spikes indicate congestion, steady high ping indicates routing issues
Diagnostic only — doesn't fix anything, but tells you exactly how bad your connection is and whether it's consistent or intermittent.
02 Switch to Ethernet and disable WiFi
1. Connect your PC to your router with an Ethernet cable 2. Open Windows Settings → Network & Internet → WiFi 3. Toggle WiFi off to prevent Windows from splitting traffic 4. Restart New World and check Input Latency via F11 5. Compare before/after — WiFi users typically see 5-20ms improvement plus less jitter
Eliminates wireless jitter and packet loss. The single most effective free fix for WiFi users — critical for consistent dodging in Wars.
03 Set Bandwidth Mode to High
1. Press Esc in-game 2. Go to Settings → Game tab 3. Find 'Bandwidth Mode' and set it to High 4. If visible, disable 'Telemetry Data' 5. Restart the game session to apply
Ensures the game requests full game-state updates rather than a reduced bandwidth mode. Most impactful for connections with available bandwidth that the game wasn't fully utilizing.
04 Flush DNS and reset Windows network stack
1. Right-click Start Menu → Windows Terminal (Admin) or Command Prompt (Admin) 2. Run each command in sequence: ipconfig /flushdns netsh winsock reset netsh int ip reset 3. Restart your PC 4. Launch New World and check ping via F11
Fixes routing issues from stale DNS entries or a corrupted Windows network state. Quick 5-minute fix that resolves sudden ping increases after Windows updates.
General network tips (not New World: Aeternum-specific)
05 Traceroute to diagnose ISP routing to AWS
1. Open Command Prompt (Windows key + R, type cmd, Enter) 2. Type: tracert 52.0.0.1 (AWS US East - Virginia region) 3. Or for EU: tracert 52.28.0.1 (AWS Frankfurt) 4. Count the hops and note where latency jumps. A jump at hop 3-5 inside your ISP's network = ISP routing issue. A jump at hop 6-10 near AWS edge = peering issue. 5. If you see your traffic leaving North America before coming back, your ISP has a major routing problem
Identifies whether your ISP's path to AWS is the problem. This diagnosis directly tells you whether PingAim will help — if you see inefficient hops to AWS, routing through a different interface can shave 20-80ms off the round-trip in many cases.
06 Verify your route to AWS us-east-1 or eu-central-1
Open Command Prompt and run: tracert 52.0.0.1 (AWS Virginia range) or tracert 52.28.0.1 (AWS Frankfurt). Count hops and identify where latency spikes. If your ISP routes through unexpected countries, your peering to AWS is suboptimal.
Diagnoses whether your ISP has routing issues to AWS — the exact problem PingAim solves.
Still lagging? The problem is likely your ISP's routing to the game servers.
PingAim detects New World: Aeternum automatically
No manual config. PingAim identifies New World: Aeternum by process name and routes it through your fastest connection using a kernel-level WFP driver.