Lag spikes of 1 second every 1-3 minutes.
While helping a mate I noticed we both get these at the exact same time. We run different GPUs, he runs Nvidia, I run AMD. We are 30 miles apart. He is on the newer BT lines in the UK, and I am on the virginmedia dedicated lines. So nothing links the two systems as a possible cause.
WinMTR shows issues at your end.
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|-----------------------------------------------------------|------|------|------|------|------|------|
| 192.168.0.1 - 0 | 3107 | 3107 | 0 | 0 | 6 | 1 |
| 10.53.33.129 - 0 | 3107 | 3107 | 4 | 9 | 720 | 10 |
| 80.255.199.120 - 0 | 3107 | 3107 | 4 | 11 | 654 | 10 |
| No response from host - 100 | 626 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 626 | 0 | 0 | 0 | 0 | 0 |
|86.85-254-62.static.virginmediabusiness.co.uk - 0 | 3107 | 3107 | 17 | 24 | 813 | 24 |
| No response from host - 100 | 626 | 0 | 0 | 0 | 0 | 0 |
| uk-lon01b-ri1-ae-25-0.aorta.net - 0 | 3107 | 3107 | 17 | 24 | 734 | 24 |
| ldn-b3-link.ip.twelve99.net - 28 | 1490 | 1080 | 0 | 23 | 62 | 23 |
| ldn-bb1-link.ip.twelve99.net - 1 | 3103 | 3102 | 20 | 24 | 93 | 25 |
| prs-bb1-link.ip.twelve99.net - 62 | 911 | 355 | 27 | 31 | 40 | 30 |
| ffm-bb1-link.ip.twelve99.net - 0 | 3107 | 3107 | 33 | 38 | 749 | 39 |
| ffm-b11-link.ip.twelve99.net - 85 | 716 | 112 | 36 | 41 | 108 | 38 |
|squareenix-ic-369631.ip.twelve99-cust.net - 0 | 3107 | 3107 | 33 | 39 | 703 | 38 |
| 80.239.145.241 - 11 | 2227 | 2001 | 34 | 38 | 50 | 39 |
| 80.239.145.96 - 0 | 3107 | 3107 | 33 | 39 | 797 | 39 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Mostly from twelve99.net onwards.
Aww shit, here we go again
Looks like I'm back with another network issue. This time, rather than difficulties logging in, it's been a consistent problem with rubberbanding, high ping, and dropped packets.
These results are for the NA server. I'm playing from the East Coast on Optimum.
Ping statistics for 204.2.29.78:
Packets: Sent = 969, Received = 891, Lost = 78 (8% loss),
Approximate round trip times in milli-seconds:
Minimum = 121ms, Maximum = 150ms, Average = 125ms
While 8% doesn't seem like a lot, they happen in blocks and the effect is most noticeable in-game while running content like dungeons or FATEs. The enemies stutter in their movement or sometimes abilities won't trigger immediately like they're supposed to.
Below is a result of tracert, with the first four hops omitted for privacy concerns:
5 5 ms 5 ms 6 ms 451be068.cst.lightpath.net [65.19.99.104]
6 6 ms 5 ms 4 ms 64.15.1.151
7 6 ms 5 ms 7 ms nyk-b7-link.ip.twelve99.net [62.115.153.104]
8 6 ms 5 ms 5 ms ewr-bb2-link.ip.twelve99.net [62.115.143.12]
9 * * * Request timed out.
10 11 ms 5 ms 8 ms ae-17.a02.nycmny17.us.bb.gin.ntt.net [129.250.8.229]
11 6 ms 6 ms 7 ms ae-16.r23.nwrknj03.us.bb.gin.ntt.net [129.250.3.16]
12 25 ms 24 ms 25 ms ae-10.r24.chcgil09.us.bb.gin.ntt.net [129.250.2.166]
13 24 ms 23 ms 23 ms ae-1.r25.chcgil09.us.bb.gin.ntt.net [129.250.5.135]
14 120 ms 120 ms 120 ms ae-7.r26.snjsca04.us.bb.gin.ntt.net [129.250.4.137]
15 124 ms 124 ms 125 ms ae-4.a00.scrmca03.us.bb.gin.ntt.net [129.250.7.57]
16 124 ms 125 ms 124 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
17 124 ms 123 ms 125 ms 204.2.29.241
18 124 ms 124 ms 124 ms 204.2.29.78
As you can see, the high ping starts when it gets to hop 14, node titled ae-7.r26.snjsca04.us.bb.gin.ntt.net [129.250.4.137]. This could indicate a problem on that node specifically or the one before it. These results are consistent and do not change.
Playing on Windows 64-bit DX11 client. Wired connection with speed tests confirming over 300Mbps download speed. No other pings to any other IP addresses show dropped packets or high ping results.
I have tried network hardware resets, PC reset, and various network troubleshooting on my PC including DNS flush, ipconfig release/renew, netsh winsock reset, updating network drivers and uninstalling/reinstalling the network card.
This is not a local issue, this appears to be on the route to the server or an issue in the datacenter itself