Tracert (First 5 hops omitted, local network or ISP gateway):
Spoiler
1 1 ms 1 ms 1 ms omitted
2 <1 ms <1 ms <1 ms omitted
3 6 ms 5 ms 8 ms omitted
4 6 ms 5 ms 5 ms omitted
5 6 ms 6 ms 6 ms omitted
6 8 ms 7 ms 7 ms tcore4-toronto12_2-4-0-0_.net.bell.ca [64.230.10
4.164]
7 7 ms 6 ms 7 ms tcore4-torontoxn_hundredgige0-5-0-0.net.bell.ca
[64.230.50.13]
8 6 ms 5 ms 6 ms bx1-torontoxn_et4-0-0.net.bell.ca [64.230.97.159
]
9 6 ms 6 ms 6 ms level3_bx1-torontoxn.net.bell.ca [67.69.246.158]
10 * * * Request timed out.
11 116 ms 115 ms 116 ms br2.amsterdam1.surf.net [213.244.164.2]
12 147 ms 147 ms 147 ms ae6-6.rt.sl.spb.ru.retn.net [87.245.232.141]
13 130 ms 130 ms 130 ms gw-selectel.retn.net [87.245.228.222]
14 132 ms 132 ms 132 ms 05.spb.net.selectel.ru [188.93.17.9]
15 131 ms 130 ms 131 ms node05st-ru.star-conflict.com [5.178.86.28]
The only router that ever dropped a packet was hop #11: br2.amsterdam1.surf.net [213.244.164.2]
I cannot get any metrics from hop #10, since it does not return any ICMP packets.
Here is hop #11 br2.amsterdam1.surf.net [213.244.164.2], while pinging the game server (5.178.86.28) with TTL=11:
Spoiler
Date/Time: 4/22/2017 10:21:51 AM Eastern Standard Time
Pinging 5.178.86.28 with 512 bytes and TTL 11:
Reply from 213.244.164.2: bytes=512 time=129ms TTL=11
Reply from 213.244.164.2: bytes=512 time=116ms TTL=11
Reply from 213.244.164.2: bytes=512 time=115ms TTL=11
Reply from 213.244.164.2: bytes=512 time=116ms TTL=11
Reply from 213.244.164.2: bytes=512 time=116ms TTL=11
Reply from 213.244.164.2: bytes=512 time=116ms TTL=11
Reply from 213.244.164.2: bytes=512 time=116ms TTL=11
Reply from 213.244.164.2: bytes=512 time=116ms TTL=11
Reply from 213.244.164.2: bytes=512 time=116ms TTL=11
Reply from 213.244.164.2: bytes=512 time=116ms TTL=11
Reply from 213.244.164.2: bytes=512 time=116ms TTL=11
Reply from 213.244.164.2: bytes=512 time=116ms TTL=11
Reply from 213.244.164.2: bytes=512 time=116ms TTL=11
Reply from 213.244.164.2: bytes=512 time=118ms TTL=11
Reply from 213.244.164.2: bytes=512 time=116ms TTL=11
Reply from 213.244.164.2: bytes=512 time=117ms TTL=11
Reply from 213.244.164.2: bytes=512 time=130ms TTL=11
Reply from 213.244.164.2: bytes=512 time=116ms TTL=11
Reply from 213.244.164.2: bytes=512 time=116ms TTL=11
Reply from 213.244.164.2: bytes=512 time=115ms TTL=11
Reply from 213.244.164.2: bytes=512 time=116ms TTL=11
Reply from 213.244.164.2: bytes=512 time=116ms TTL=11
Reply from 213.244.164.2: bytes=512 time=116ms TTL=11
Reply from 213.244.164.2: bytes=512 time=116ms TTL=11
Reply from 213.244.164.2: bytes=512 time=116ms TTL=11
Reply from 213.244.164.2: bytes=512 time=116ms TTL=11
Reply from 213.244.164.2: bytes=512 time=116ms TTL=11
Reply from 213.244.164.2: bytes=512 time=116ms TTL=11
Reply from 213.244.164.2: bytes=512 time=118ms TTL=11
Reply from 213.244.164.2: bytes=512 time=116ms TTL=11
Reply from 213.244.164.2: bytes=512 time=115ms TTL=11
Reply from 213.244.164.2: bytes=512 time=116ms TTL=11
Reply from 213.244.164.2: bytes=512 time=116ms TTL=11
Reply from 213.244.164.2: bytes=512 time=116ms TTL=11
Reply from 213.244.164.2: bytes=512 time=118ms TTL=11
Reply from 213.244.164.2: bytes=512 time=116ms TTL=11
Reply from 213.244.164.2: bytes=512 time=115ms TTL=11
Reply from 213.244.164.2: bytes=512 time=116ms TTL=11
Reply from 213.244.164.2: bytes=512 time=130ms TTL=11
Reply from 213.244.164.2: bytes=512 time=116ms TTL=11
Reply from 213.244.164.2: bytes=512 time=116ms TTL=11
Reply from 213.244.164.2: bytes=512 time=116ms TTL=11
Reply from 213.244.164.2: bytes=512 time=116ms TTL=11
Reply from 213.244.164.2: bytes=512 time=116ms TTL=11
Reply from 213.244.164.2: bytes=512 time=124ms TTL=11
Reply from 213.244.164.2: bytes=512 time=116ms TTL=11
Reply from 213.244.164.2: bytes=512 time=116ms TTL=11
Reply from 213.244.164.2: bytes=512 time=116ms TTL=11
Reply from 213.244.164.2: bytes=512 time=120ms TTL=11
Reply from 213.244.164.2: bytes=512 time=115ms TTL=11
TTLP statistics for 213.244.164.2:
Packets: Sent = 50, Received = 50, >1000ms = 0 (0%), Lost = 0 (0%),
Approximate round trip times in milli-seconds:
Minimum = 115ms, Maximum = 130ms, Difference = 15ms, Average = 117ms
Variance of 15ms, no dropped packets (there was only 1 earlier). I also ICMPd the RU servers, and there was no packet loss there, difference of about 15ms as well. Did a few more on hop #11, dropped 1 more packet, and a difference of 41ms, but that was only 1 out of a series of them.
Actually, that is just the Amsterdam server dropping its own ICMP responses.
Here is the summary for the game server (5.178.86.28) - 0% packet loss, 0.1% congestion >161ms:
Spoiler
TTLP statistics for 5.178.86.28:
Packets: Sent = 1000, Received = 1000, >161ms = 1 (0%), Lost = 0 (0%),
Approximate round trip times in milli-seconds:
Minimum = 130ms, Maximum = 166ms, Difference = 36ms, Average = 131ms
This doesn’t appear to be any different from any other time of day, so why is there massive lag and packet loss? Server load?
You know, I just realized where the server capacity went! If not for PvE, OS and Co-op modes, there would be more capacity to dedicate to PvP. ;o
edit: Also, module de-activation does not apply to Recon. You must strafe or roll apparently to exit the warp. Pushing the module button again does not cancel it. So, I have no way of testing that unless I decide to play Tackler/LRF in T5.