This only happens at night for me, around 8:30pm +8GMT for some reason. Been like this for the past 3 days now.
This only happens at night for me, around 8:30pm +8GMT for some reason. Been like this for the past 3 days now.
I can confirm alot of SEA player is lagging, Technical support we need help, is not fun to not be able to play with this massive delay, lag and kick out of the server during Christmas time..
Been having the same issue basically since 6.01 launch, and i think a bit before it. Haven't had any issues with the packet loss or severe lag before prime release of endwalker and especially now during 6.01. I really wish they would get onto this and give an actual response instead of dismissing or delaying it. It makes the game borderline unplayable at times and it's constant
Seems like only SEA players have this problem.
I really hope this is not the cause to make us, SEA players, reluctantly move to Oceania DC….
I'm in Northeast America with this problem, though I don't know how many of us up here have this issue aside of me. I have no desire to move to another DC, but it makes it tempting..
Kinda surprise SE have not acknowledge anything yet.
The game is totally unplayable due to the delay in combat/movement.
I'm still having issues a day after the problem started. For me, it's just the NA servers that seem to be affected. I'm playing from NZ.
I seem to be experiencing some issues as well this evening. I was fine earlier this afternoon but now I'm getting some pretty bad delays in game. Not sure if it's the bad weather sweeping across some of the US or something messing with the internet pipeline but something clearly isn't right. NA server here, east coast US.
This has been happening to me consistently as well over the last several days since the patch on Ultros.
Consistent packet loss along route.
Results of pathping to server (Primal)
Computing statistics for 450 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
1 0ms 0/ 100 = 0% 0/ 100 = 0% [redacted]
0/ 100 = 0% |
2 17ms 0/ 100 = 0% 0/ 100 = 0% [redacted]
0/ 100 = 0% |
3 25ms 0/ 100 = 0% 0/ 100 = 0% [redacted]
0/ 100 = 0% |
4 21ms 5/ 100 = 5% 5/ 100 = 5% [redacted]
0/ 100 = 0% |
5 25ms 4/ 100 = 4% 4/ 100 = 4% [redacted]
0/ 100 = 0% |
6 26ms 8/ 100 = 8% 8/ 100 = 8% [redacted]
0/ 100 = 0% |
7 26ms 8/ 100 = 8% 8/ 100 = 8% bu-ether14.dllstx976iw-bcr00.tbone.rr.com [66.109.6.88]
0/ 100 = 0% |
8 19ms 0/ 100 = 0% 0/ 100 = 0% 66.109.5.121
2/ 100 = 2% |
9 24ms 4/ 100 = 4% 2/ 100 = 2% ae3.cr7-dal3.ip4.gtt.net [208.116.212.9]
0/ 100 = 0% |
10 23ms 4/ 100 = 4% 2/ 100 = 2% ae0.cr11-dal3.ip4.gtt.net [89.149.139.201]
0/ 100 = 0% |
11 21ms 8/ 100 = 8% 6/ 100 = 6% as2914.cr11-dal3.ip4.gtt.net [69.174.23.138]
0/ 100 = 0% |
12 24ms 3/ 100 = 3% 1/ 100 = 1% ae-2.r21.dllstx14.us.bb.gin.ntt.net [129.250.4.19]
0/ 100 = 0% |
13 64ms 7/ 100 = 7% 5/ 100 = 5% ae-2.r25.snjsca04.us.bb.gin.ntt.net [129.250.4.154]
0/ 100 = 0% |
14 60ms 4/ 100 = 4% 2/ 100 = 2% ae-5.r24.snjsca04.us.bb.gin.ntt.net [129.250.3.146]
0/ 100 = 0% |
15 61ms 2/ 100 = 2% 0/ 100 = 0% ae-4.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.57]
1/ 100 = 1% |
16 --- 100/ 100 =100% 97/ 100 = 97% xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [192.80.16.2] <------ consistent packet loss (97%)
0/ 100 = 0% |
17 63ms 4/ 100 = 4% 1/ 100 = 1% 204.2.229.230
0/ 100 = 0% |
18 65ms 3/ 100 = 3% 0/ 100 = 0% 204.2.229.10
Trace complete.