Bad lag again with NTT's NA server network

[Aexnidaral]

Issues with the Sacramento Node, yet again. Getting over 150 ping when I usually get 80/90.

[Janyd]

Yep, looks like the Sacramento node is starting to go back into its bad habits again.

The spikes are around 100ms. Brief but noticeable.

EDIT: Pasting my most recent traceroute, starting at the first NTT node.

8 29 ms 28 ms 29 ms ae-13.a01.dllstx14.us.bb.gin.ntt.net [129.250.8.213]
9 * * * Request timed out.
10 56 ms 55 ms 55 ms ae-2.r24.lsanca07.us.bb.gin.ntt.net [129.250.7.69]
11 98 ms 98 ms 114 ms ae-5.a01.scrmca03.us.bb.gin.ntt.net [129.250.2.7]
12 101 ms 103 ms 105 ms ae-1.a00.scrmca03.us.bb.gin.ntt.net [129.250.4.76]
13 99 ms 101 ms 99 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
14 * * * Request timed out.
15 102 ms 102 ms 106 ms 204.2.29.122

[Janyd]

Hmm, strange. After today's hotfixes (and the May 6 DDoS), the NTT routing now goes from Dallas to Miami then to Sacramento, at least for me.

Traceroute enclosed as proof, starting at the first NTT node.

8 28 ms 27 ms 28 ms ae-13.a01.dllstx14.us.bb.gin.ntt.net [129.250.8.213]
9 28 ms 27 ms 27 ms ae-6.r22.dllstx14.us.bb.gin.ntt.net [129.250.3.118]
10 * * * Request timed out.
11 54 ms 52 ms 56 ms ae-0.a02.miamfl02.us.bb.gin.ntt.net [129.250.2.4]
12 * * * Request timed out.
13 54 ms 53 ms 53 ms ae-0.r22.miamfl02.us.bb.gin.ntt.net [129.250.2.5]
14 * * * Request timed out.
15 * * * Request timed out.
16 95 ms 100 ms 94 ms ae-5.a01.scrmca03.us.bb.gin.ntt.net [129.250.2.7]
17 95 ms 93 ms 94 ms ae-1.a00.scrmca03.us.bb.gin.ntt.net [129.250.4.76]
18 95 ms 94 ms 93 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
19 94 ms 94 ms 94 ms 204.2.29.241
20 93 ms 92 ms 94 ms 204.2.29.122

[Allison_Grimvault]

I just started getting horrid lag today after work even with the VPN that I've been using since the start of this thread last year. Unplayable LAG that was causing wipes as everything I saw was several seconds behind the party I was healing. I switched from the Dallas server to the Atlanta server on Nord and the lag is gone thank Christ as it was ruining my night with my mistress. Something definitely happened after today's hotfixes.

[wizisi2k]

Since the update on Tuesday, I've been getting consistant 2002 errors when connecting via my ISP to the game which do not exist if I utilize hotpost data. Today, I did a tracert while trying to login and found something interestering. Before I was trying to login, I could reach the Crystal DC lobby server in 21 hops. When I did a tracert while trying to login, it took 27 hops. I'm attaching below the tracert before I tried logging in first followed by the one I started while trying to login (removing timeouts from the logs and only including everything after NTT). "
11 7 ms 8 ms 7 ms ae-17.a02.nycmny17.us.bb.gin.ntt.net [129.250.8.229]
15 74 ms 71 ms * ae-0.r25.sttlwa01.us.bb.gin.ntt.net [129.250.3.83]
18 83 ms 82 ms 84 ms ae-4.a00.scrmca03.us.bb.gin.ntt.net [129.250.7.57]
19 83 ms 85 ms 83 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
20 83 ms 84 ms 84 ms 204.2.29.241
21 82 ms 82 ms 84 ms 204.2.29.8"
Second tracert "
11 27 ms 21 ms 9 ms ae-17.a02.nycmny17.us.bb.gin.ntt.net [129.250.8.229]
27 * * 84 ms 204.2.29.8"
I am connecting from the East Coast in NJ and my routing is going thru Seattle which makes no sense.

[XSSIV]

1 2 ms 1 ms 1 ms 192.168.68.1
2 4 ms 3 ms 2 ms 01.dc.d12c.cidr.airmail.net [209.44.220.1]
3 11 ms 12 ms 10 ms mt-rtr-e2.wynhll.setx.airmail.net [209.44.135.142]
4 11 ms 9 ms 10 ms 10.209.9.0
5 24 ms 16 ms 17 ms 69.170.120.52
6 16 ms 16 ms 16 ms 10.209.8.4
7 21 ms 18 ms 16 ms 50.be.425e.riseb.net [66.94.190.80]
8 17 ms 16 ms 18 ms 0.ae53.er3.dfw2.us.zip.zayo.com [72.10.75.60]
9 * * * Request timed out.
10 * * * Request timed out.
11 56 ms 21 ms 17 ms zayo.ntt.ter1.dfw2.us.zip.zayo.com [64.125.15.71]
12 17 ms 17 ms 17 ms ae-5.r22.dllstx14.us.bb.gin.ntt.net [129.250.3.116]
13 * * * Request timed out.
14 128 ms 126 ms 125 ms ae-7.r21.londen12.uk.bb.gin.ntt.net [129.250.2.110]
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

[AluneTempest]

The game is just unplayable without VPN for me in peak hours, and is the same thing every day, packet loss and high ping during those hours.
Now i have to pay for a VPN just to play this specific game.

[XSSIV]

I have been running the Cloudflare WARP client. Cloudflare's WARP Client: https://1.1.1.1 It seems to have helped. I still get bumped off, just not as much.

[ShizuForever]

literally have a private internet access premium account and no matter which server i tried connecting to (trust me i tried a lot of the US ones and many south east asia ones) it always starts dying once it reaches NTT
same problem when i dont use the PIA VPN
i thought paying a subscription fee and the expansion prices and the mogstation was enough arleady but no now i gotta pay a vpn to play this damn game

[Leeroy]

Exact same issue on EU datacenter with their ISP (twelve99). Every day during peak time (from around 6PM until around 11PM CEST) for the past year+ there is a huge congestion within twelve99 network, causing high latency and up to 40% packet loss. SE chose the cheapest ISPs that are known to provide low quality service (congested networks).

I, like many, refuse to pay extra subscription for VPN to avoid these congested routes. It's SE's problem and we (players) pay them to play the game, they should provide proper quality of service for all regions, not just Japan.