When trying to tracert to what I believe to be the NA servers for War Thunder I get:
Tracing route to 185.106.204.4 over a maximum of 30 hops
1 2 ms 1 ms 1 ms 192.168.1.1
2 8 ms 7 ms 9 ms 10.144.5.1
3 8 ms 9 ms 9 ms 172.30.18.33
4 9 ms 10 ms 15 ms 10.16.112.2
5 13 ms 13 ms 12 ms 10.16.112.61
6 11 ms 10 ms 11 ms 68-66-73-252.client.mchsi [dot] com [68.66.73.252]
7 11 ms 22 ms 12 ms po10.mplmn001er1.mchsi [dot] com [68.66.72.70]
8 9 ms 12 ms 9 ms ae1-1492.cr6-min1.ip4.gtt [dot] net [198.47.97.250]
9 102 ms 102 ms 102 ms ae1.cr6-lon1.ip4.gtt [dot] net [213.200.113.38]
then it times out.
I can tracert:
Tracing route to dns.google [8.8.8.8] over a maximum of 30 hops:
1 3 ms 1 ms 2 ms 192.168.1.1
2 7 ms 7 ms 8 ms 10.144.5.1
3 6 ms 5 ms 5 ms 172.30.18.33
4 10 ms 9 ms 11 ms 10.16.112.2
5 12 ms 9 ms 11 ms 10.16.112.61
6 30 ms 29 ms 31 ms 10.16.112.103
7 30 ms 29 ms 29 ms po10.demia001ag1.mchsi [dot] com [68.66.73.254]
8 29 ms 30 ms 31 ms 68-66-73-8.client.mchsi [dot] com [68.66.73.8]
9 30 ms 30 ms 30 ms po13.chgil001cr1.mchsi [dot] com [68.66.72.41]
10 31 ms 29 ms 29 ms po10.chgil001er1.mchsi [dot] com [68.66.73.122]
11 31 ms 30 ms 31 ms 72.14.198.150
12 31 ms 32 ms 30 ms 142.251.64.197
13 31 ms 29 ms 29 ms 142.251.231.249
14 29 ms 30 ms 28 ms dns.google [dot] com [8.8.8.8]
I get 1-12% packet loss in some matches lasting most of the match up until the last small amount of the match. I can play other online games with no similar issues, and their tracerts are fine as well. In ground battles, I do not ever get this issue. However, I only get this issue in air battles.
I can also do warthunder [dot] com just fine:
Tracing route to warthunder [dot] com [172.66.151.104] over a maximum of 30 hops:
1 3 ms 1 ms 1 ms 192.168.1.1
2 9 ms 8 ms 9 ms 10.144.5.1
3 8 ms 7 ms 7 ms 172.30.18.33
4 9 ms 9 ms 9 ms 10.16.112.2
5 12 ms 11 ms 11 ms 10.16.112.61
6 10 ms 11 ms 12 ms 68-66-73-252.client.mchsi [dot] com [68.66.73.252]
7 12 ms 12 ms 11 ms po10.mplmn001er1.mchsi [dot] com [68.66.72.70]
8 10 ms 11 ms 17 ms 162.158.212.2
9 12 ms 16 ms 10 ms 172.66.151.104
Trace complete.
What is ae1.cr6-lon1.ip4.gtt [dot] net [213.200.113.38]? I have tried to look it up but it comes back just as a telecom conglomerate that has nothing to do with my ISP.
Tracing route to host18gc-us-ash.warthunder [dot] com [89.43.104.166]
over a maximum of 30 hops:
1 2 ms 2 ms 2 ms 192.168.1.1
2 8 ms 9 ms 7 ms 10.144.5.1
3 11 ms 9 ms 6 ms 172.30.18.33
4 9 ms 9 ms 9 ms 10.16.112.2
5 10 ms 9 ms 9 ms 10.16.112.61
6 11 ms 11 ms 9 ms 68-66-73-252.client.mchsi [dot] com [68.66.73.252]
7 11 ms 13 ms 11 ms po10.mplmn001er1.mchsi [dot] com [68.66.72.70]
8 10 ms 11 ms 12 ms ae1-1492.cr6-min1.ip4.gtt [dot] net [198.47.97.250]
9 37 ms 35 ms 35 ms ae0.cr6-was1.ip4.gtt [dot] net [89.149.130.50]
10 * * * Request timed out.
Tracing route to 172.240.109.44 over a maximum of 30 hops:
1 <1 ms 1 ms 1 ms 192.168.1.1
2 8 ms 8 ms 7 ms 10.144.5.1
3 8 ms 8 ms 7 ms 172.30.18.33
4 11 ms 9 ms 9 ms 10.16.112.2
5 11 ms 10 ms 9 ms 10.16.112.61
6 11 ms 11 ms 11 ms 68-66-73-252.client.mchsi [dot] com [68.66.73.252]
7 11 ms 11 ms 12 ms po10.mplmn001er1.mchsi [dot] com [68.66.72.70]
8 9 ms 10 ms 9 ms ae1-1492.cr6-min1.ip4.gtt [dot] net [198.47.97.250]
9 18 ms 17 ms 17 ms ae0.cr12-chi1.ip4.gtt [dot] net [89.149.131.242]
10 * * * Request timed out.
11 21 ms 20 ms 19 ms be2765.ccr41.ord01.atlas.cogentco [dot] com [154.54.45.17]
12 31 ms 31 ms 31 ms port-channel2717.ccr91.cle04.atlas.cogentco [dot] com [154.54.6.222]
13 37 ms 37 ms 43 ms port-channel9258.ccr91.dca04.atlas.cogentco [dot] com [154.54.173.94]
14 37 ms 37 ms 38 ms be8413.ccr41.iad02.atlas.cogentco [dot] com [154.54.5.218]
15 37 ms 37 ms 37 ms xcore-was1-se-r1.servers [dot] com [209.192.153.216]
Tracing route to 172.240.109.52 over a maximum of 30 hops:
1 3 ms 1 ms 1 ms 192.168.1.1
2 8 ms 7 ms 9 ms 10.144.5.1
3 8 ms 9 ms 9 ms 172.30.18.33
4 9 ms 9 ms 9 ms 10.16.112.2
5 40 ms 11 ms 9 ms 10.16.112.61
6 11 ms 11 ms 11 ms 68-66-73-252.client.mchsi [dot] com [68.66.73.252]
7 13 ms 11 ms 11 ms po10.mplmn001er1.mchsi [dot] com [68.66.72.70]
8 11 ms 12 ms 14 ms ae1-1492.cr6-min1.ip4.gtt [dot] net [198.47.97.250]
9 18 ms 17 ms 18 ms ae0.cr12-chi1.ip4.gtt [dot] net [89.149.131.242]
10 18 ms 17 ms 19 ms be3257.ccr41.ord03.atlas.cogentco [dot] com [154.54.11.241]
11 18 ms 18 ms 13 ms be2765.ccr41.ord01.atlas.cogentco [dot] com [154.54.45.17]
12 29 ms 30 ms 31 ms port-channel2717.ccr91.cle04.atlas.cogentco [dot] com [154.54.6.222]
13 37 ms 41 ms 37 ms port-channel9258.ccr91.dca04.atlas.cogentco [dot] com [154.54.173.94]
14 37 ms 38 ms 37 ms be8413.ccr41.iad02.atlas.cogentco [dot] com [154.54.5.218]
15 38 ms 38 ms 37 ms 209.192.153.247
16 * * *
Subject: Intermittent packet loss/timeout to War Thunder NA game server — possible GTT transit routing issue
Hello — please investigate an intermittent packet-loss/timeout problem I get when playing War Thunder (only in air battles). I’ve included traceroutes and diagnostic notes below.
Summary
Problem: 1–12% packet loss seen in matches (mostly during the match, sometimes until the match end). Only occurs in air battles (ground battles are fine). Other online games are unaffected.
Affected game server IPs I tested: 185.106.204.4 (War Thunder US game server reported by community), and the resolved hostnames used in-game. I also tested DNS 8.8.8.8 and warthunder [dot] com — those tracerts behave differently.
ISP: (paste your ISP name here — from my traces it appears to be Mediacom / mchsi hostnames).
My public IP: (paste your public IP here).
Time(s) observed: (give ISO timestamps for a few matches, e.g. 2025-11-16 19:20 CST).
Router/modem model & firmware: (paste).
Connection type: wired Ethernet from PC to router (or say wireless if applicable).
Key traceroute outputs
To 185.106.204.4 (War Thunder US):
1 192.168.1.1
2 10.144.5.1
3 172.30.18.33
4 10.16.112.2
5 10.16.112.61
6 68-66-73-252.client.mchsi
7 po10.mplmn001er1.mchsi
8 ae1-1492.cr6-min1.ip4.gtt
9 ae1.cr6-lon1.ip4.gtt <-- big jump to 102 ms then timeouts
<then it times out>
To 8.8.8.8 (Google DNS) — completes locally without the transatlantic spike:
... reaches 8.8.8.8 in ~30 ms; path stays on regional backbone and does not show the same 102 ms spike or timeout.
To warthunder [dot] com (web) — completes normally (resolved to Cloudflare IP), no timeouts.
Observations & likely interpretation
The hop ae1.cr6-lon1.ip4.gtt (213.200.113.38) is part of GTT Communications’ global backbone (a GTT core/router in the “cr6 LON1” PoP). This hostname indicates traffic is being carried over a GTT transit node (likely London).
A single traceroute shows a latency jump to ~102 ms at that hop and then request timeouts. That suggests either: (a) traffic is being routed to Europe (hairpin) instead of the correct North American path, (b) an intermediate link is congested or flapping, or (c) those GTT devices are deprioritizing ICMP (common) while UDP game traffic might still have issues further along. ICMP timeouts in traceroute are common and don’t always mean application-level packet loss — but you are seeing actual in-game packet loss (1–12%), so this is not purely diagnostic noise.
Your ISP’s internal/private hops (10.x / 172.30.x) and hostnames like client.mchsi indicate your connection is being carried by your ISP to a GTT uplink/peer — so the problem is likely on the ISP → upstream (GTT) path or on the upstream peering between GTT and the game host (Gaijin). Gaijin/War Thunder IP ranges (e.g. 185.106.204.4 / 185.106.206.x) are known in community traces to belong to the game servers.
What I suggest you (devs / ISP / War Thunder networking team) check
Inspect BGP/peering and traffic engineering for 185.106.204.4 and nearby Gaijin IP ranges; verify whether traffic from the user’s ISP is being sent to GTT’s London PoP and then back to the US (a hairpin) instead of using a local peering point. Run a BGP path check / Looking Glass from GTT and from the ISP towards 185.106.204.4.
Check interface utilization and drops on the GTT CR6-LON1 device (213.200.113.38) and adjacent peers during the time windows I provided. Look for packet counters, errors, or BGP flaps.
Confirm whether ICMP is being rate-limited (explains traceroute timeouts). If the ICMP is deprioritized, check UDP paths used for the game (and whether UDP packets are being dropped/queued on any hop).
Verify whether War Thunder matchmaking sometimes lands players on a different regional server (air battles possibly using a different datacenter) — explain why air battles only. War Thunder sometimes routes different modes or matches to different server clusters; please confirm which server cluster these match IDs used.
Diagnostics / attachments I can provide
Full text copies of the traceroutes I ran.
WinMTR (or MTR) logs to the target server IP while a match is running (captures per-hop packet loss over time).
Short Wireshark / packet capture during an affected match (captures UDP traffic, retransmits, jitter; small timeframe if privacy concern).
Exact match IDs and timestamps for matches where packet loss was seen.
Speedtest and ping/jitter results run at the same time as a match.
Router/modem logs (WAN interface errors, reauths) and public IP.
Quick test: connecting via VPN or phone hotspot — if the problem disappears, likely a routing/transit problem on ISP → GTT → Gaijin path.
Quick user troubleshooting (things I can/do already)
I can reach 8.8.8.8 and warthunder [dot] com without issues, so general Internet connectivity is fine.
I am connecting via (wired / wireless) from (OS).
What I’d like you (devs/ISP) to do next
Run BGP/looking-glass from your edge and from GTT for prefixes containing 185.106.204.4 and the GTT IP 213.200.113.38. Provide the AS path and confirm the preferred egress/ingress points.
Check for interface drops or queuing on the GTT and peering interfaces during the match timestamps I provided.
If possible, route a test flow (or pinhole) for my public IP to the War Thunder server to observe whether packet loss appears in netflow/sflow/IP counters.
If this is a peering/route selection issue, consider announcing preferred shorter path or rearranging peering to avoid the London hairpin for traffic between my ISP region and the War Thunder NA servers.
Tracing route to ae1-1492.cr6-min1.ip4.gtt [dot] net [198.47.97.250]
over a maximum of 30 hops:
1 3 ms 1 ms 1 ms 192.168.1.1
2 18 ms 7 ms 11 ms 10.144.5.1
3 11 ms 9 ms 9 ms 172.30.18.33
4 12 ms 11 ms 15 ms 10.16.112.2
5 33 ms 10 ms 11 ms 10.16.112.61
6 11 ms 11 ms 11 ms 68-66-73-252.client.mchsi [dot] com [68.66.73.252]
7 10 ms 11 ms 11 ms po10.mplmn001er1.mchsi [dot] com [68.66.72.70]
8 19 ms 9 ms 9 ms ae1-1492.cr6-min1.ip4.gtt [dot] net [198.47.97.250]
Trace complete.
C:\Users\user>tracert 213.200.113.38
Tracing route to ae1.cr6-lon1.ip4.gtt [dot] net [213.200.113.38]
over a maximum of 30 hops:
1 3 ms 1 ms 1 ms 192.168.1.1
2 7 ms 7 ms 10 ms 10.144.5.1
3 11 ms 11 ms 9 ms 172.30.18.33
4 10 ms 10 ms 10 ms 10.16.112.2
5 10 ms 9 ms 10 ms 10.16.112.61
6 10 ms 11 ms 9 ms 68-66-73-252.client.mchsi [dot] com [68.66.73.252]
7 9 ms 17 ms 17 ms po10.mplmn001er1.mchsi [dot] com [68.66.72.70]
8 10 ms 10 ms 9 ms ae1-1492.cr6-min1.ip4.gtt [dot] net [198.47.97.250]
9 11 ms 11 ms 10 ms ae0.cr5-min1.ip4.gtt [dot] net [213.200.113.117]
10 35 ms 35 ms 35 ms ae5.lr1-chi1.ip4.gtt [dot] net [213.200.112.114]
11 35 ms 35 ms 35 ms ae18.lr5-chi1.ip4.gtt [dot] net [89.149.136.81]
12 34 ms 36 ms 35 ms ae7.lr2-nyc12.ip4.gtt [dot] net [89.149.134.145]
13 35 ms 35 ms 35 ms ae4.lr4-nyc6.ip4.gtt [dot] net [89.149.133.65]
14 108 ms 106 ms 107 ms ae4.lr4-lon1.ip4.gtt [dot] net [89.149.142.169]
15 103 ms 109 ms 103 ms ae1.cr6-lon1.ip4.gtt [dot] net [213.200.113.38]
Tracing route to warthunder.com [172.66.151.104]
over a maximum of 30 hops:
1 1 ms 1 ms 2 ms 192.168.1.1
2 9 ms 7 ms 9 ms 10.144.5.1
3 10 ms 9 ms 9 ms 172.30.18.33
4 10 ms 9 ms 9 ms 10.16.112.2
5 10 ms 9 ms 9 ms 10.16.112.61
6 11 ms 10 ms 11 ms 68-66-73-252.client.mchsi [dot] com [68.66.73.252]
7 11 ms 11 ms 11 ms po10.mplmn001er1.mchsi [dot] com [68.66.72.70]
8 10 ms 11 ms 11 ms 162.158.212.2
9 10 ms 11 ms 21 ms 172.66.151.104