Seems like no one cares about the lag

[Liralara]

Come on guys....

Reply from 204.2.229.10: bytes=32 time=206ms TTL=48
Reply from 204.2.229.10: bytes=32 time=203ms TTL=48
Reply from 204.2.229.10: bytes=32 time=204ms TTL=48
Request timed out.
Reply from 204.2.229.10: bytes=32 time=208ms TTL=48
Reply from 204.2.229.10: bytes=32 time=205ms TTL=48
Reply from 204.2.229.10: bytes=32 time=202ms TTL=48
Reply from 204.2.229.10: bytes=32 time=204ms TTL=48
Reply from 204.2.229.10: bytes=32 time=211ms TTL=48
Request timed out.
Reply from 204.2.229.10: bytes=32 time=196ms TTL=48
Reply from 204.2.229.10: bytes=32 time=190ms TTL=48
Reply from 204.2.229.10: bytes=32 time=174ms TTL=48
Reply from 204.2.229.10: bytes=32 time=204ms TTL=48
Reply from 204.2.229.10: bytes=32 time=198ms TTL=48
Request timed out.
Reply from 204.2.229.10: bytes=32 time=199ms TTL=48
Reply from 204.2.229.10: bytes=32 time=203ms TTL=48
Reply from 204.2.229.10: bytes=32 time=209ms TTL=48
Reply from 204.2.229.10: bytes=32 time=206ms TTL=48
Reply from 204.2.229.10: bytes=32 time=203ms TTL=48
Reply from 204.2.229.10: bytes=32 time=201ms TTL=48
Reply from 204.2.229.10: bytes=32 time=198ms TTL=48
Reply from 204.2.229.10: bytes=32 time=204ms TTL=48
Request timed out.
Reply from 204.2.229.10: bytes=32 time=168ms TTL=48
Reply from 204.2.229.10: bytes=32 time=206ms TTL=48
Reply from 204.2.229.10: bytes=32 time=206ms TTL=48
Reply from 204.2.229.10: bytes=32 time=215ms TTL=48
Reply from 204.2.229.10: bytes=32 time=214ms TTL=48
Reply from 204.2.229.10: bytes=32 time=210ms TTL=48
Reply from 204.2.229.10: bytes=32 time=208ms TTL=48
Reply from 204.2.229.10: bytes=32 time=214ms TTL=48
Reply from 204.2.229.10: bytes=32 time=208ms TTL=48
Reply from 204.2.229.10: bytes=32 time=203ms TTL=48
Reply from 204.2.229.10: bytes=32 time=206ms TTL=48
Reply from 204.2.229.10: bytes=32 time=207ms TTL=48
Request timed out.
Reply from 204.2.229.10: bytes=32 time=203ms TTL=48
Reply from 204.2.229.10: bytes=32 time=195ms TTL=48
Reply from 204.2.229.10: bytes=32 time=205ms TTL=48
Reply from 204.2.229.10: bytes=32 time=207ms TTL=48
Reply from 204.2.229.10: bytes=32 time=181ms TTL=48
Reply from 204.2.229.10: bytes=32 time=196ms TTL=48
Reply from 204.2.229.10: bytes=32 time=174ms TTL=48
Reply from 204.2.229.10: bytes=32 time=202ms TTL=48
Reply from 204.2.229.10: bytes=32 time=198ms TTL=48
Reply from 204.2.229.10: bytes=32 time=199ms TTL=48
Reply from 204.2.229.10: bytes=32 time=203ms TTL=48
Reply from 204.2.229.10: bytes=32 time=208ms TTL=48
Reply from 204.2.229.10: bytes=32 time=208ms TTL=48
Reply from 204.2.229.10: bytes=32 time=194ms TTL=48
Reply from 204.2.229.10: bytes=32 time=186ms TTL=48
Request timed out.
Reply from 204.2.229.10: bytes=32 time=201ms TTL=48
Reply from 204.2.229.10: bytes=32 time=213ms TTL=48
Reply from 204.2.229.10: bytes=32 time=206ms TTL=48
Reply from 204.2.229.10: bytes=32 time=208ms TTL=48
Reply from 204.2.229.10: bytes=32 time=207ms TTL=48
Reply from 204.2.229.10: bytes=32 time=181ms TTL=48
Request timed out.
Reply from 204.2.229.10: bytes=32 time=199ms TTL=48
Reply from 204.2.229.10: bytes=32 time=190ms TTL=48
Reply from 204.2.229.10: bytes=32 time=200ms TTL=48
Reply from 204.2.229.10: bytes=32 time=199ms TTL=48
Reply from 204.2.229.10: bytes=32 time=205ms TTL=48
Reply from 204.2.229.10: bytes=32 time=203ms TTL=48
Reply from 204.2.229.10: bytes=32 time=206ms TTL=48
Reply from 204.2.229.10: bytes=32 time=207ms TTL=48
Reply from 204.2.229.10: bytes=32 time=181ms TTL=48
Request timed out.
Reply from 204.2.229.10: bytes=32 time=206ms TTL=48
Reply from 204.2.229.10: bytes=32 time=165ms TTL=48
Reply from 204.2.229.10: bytes=32 time=190ms TTL=48

[Liralara]

Traceroute to the datacenter:

6 11 ms 10 ms 10 ms gar25.dlstx.ip.att.net [12.122.85.233]
7 35 ms 40 ms 39 ms ae-5.a00.dllstx14.us.bb.gin.ntt.net [129.250.8.237]
8 38 ms 41 ms 42 ms ae-2.r21.dllstx14.us.bb.gin.ntt.net [129.250.4.19]
9 45 ms 46 ms 46 ms ae-2.r25.snjsca04.us.bb.gin.ntt.net [129.250.4.154]
10 192 ms 206 ms * ae-5.r24.snjsca04.us.bb.gin.ntt.net [129.250.3.146]
11 177 ms 189 ms 182 ms ae-4.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.57]
12 209 ms 198 ms 162 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [192.80.16.2]
13 * * 192 ms 204.2.229.230
14 177 ms 186 ms 175 ms 204.2.229.10

[Zerea]

Same. It started very late for me but has been very on/off.

Obviously I want the problem gone altogether but if it's been pushed back to ~11:30 PM every night that's a significant improvement for me. I was mostly concerned with my ping during raid times but I can handle 200 ms if I'm just doing hunts or roulettes at the end of the night.

Disregard past self.... again.

200+ ms starting at 10 PM EST. Back to the original problem.

The good/bad periods are too sporadic and varied across different nights to suggest any sort of pattern. At this point I don't think I need to keep commenting updates as plenty of other people are already doing my job for me. It's abundantly clear what the problem nodes are and it's out of our hands. Maybe if/when they finally fix something and I can go an entire week with normal ping I'll check back in.

[absolutecrow]

Using VPN to reroute from my location (Florida) to Texas.

Below is the routing without VPN.

Tracing route to 204.2.229.9 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 172.16.0.1
2 1 ms 1 ms 1 ms 104.14.148.1
3 2 ms 2 ms 2 ms 99.167.39.50
4 9 ms 6 ms 7 ms 12.242.116.11
5 23 ms 11 ms 11 ms 192.205.35.118
6 35 ms 27 ms 11 ms ae-6.r22.miamfl02.us.bb.gin.ntt.net [129.250.2.202]
7 42 ms 38 ms 39 ms ae-8.r20.dllstx14.us.bb.gin.ntt.net [129.250.2.219]
8 39 ms 39 ms 40 ms ae-1.r21.dllstx14.us.bb.gin.ntt.net [129.250.3.55]
9 90 ms 76 ms 76 ms ae-2.r25.snjsca04.us.bb.gin.ntt.net [129.250.4.154]
10 238 ms * 235 ms ae-5.r24.snjsca04.us.bb.gin.ntt.net [129.250.3.146]
11 * 234 ms 229 ms ae-4.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.57]
12 226 ms 241 ms 234 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [192.80.16.2]
13 * 238 ms 234 ms 204.2.229.230
14 238 ms 236 ms 228 ms 204.2.229.9

[Jin-]

Some strong spikes today again, even with the mudfish.
After multiple spikes i got an error 90006

[Kolsykol]

Some strong spikes today again, even with the mudfish.
After multiple spikes i got an error 90006

If it's like last week on the Light data center then it's going to be trash tomorrow too...
It seems like the weekend from friday to sunday + monday is just bad.

So basically we have three days a week to play and then it starts again...

Edit: On Arrstatus.com the EU servers have been up to 300ms and I ran Tracert.


1 5 ms 5 ms 5 ms 192.168.1.1
2 19 ms 15 ms 16 ms static-212-247-169-6.cust.tele2.se [212.247.169.6]
3 16 ms 17 ms * static-212-247-169-5.cust.tele2.se [212.247.169.5]
4 15 ms 16 ms 26 ms lim-core-1.bundle-ether1.tele2.net [130.244.82.48]
5 10 ms 7 ms 10 ms kbn-b3-link.ip.twelve99.net [62.115.171.212]
6 851 ms 850 ms * kbn-bb2-link.ip.twelve99.net [62.115.138.112]
7 31 ms 35 ms 35 ms ffm-bb2-link.ip.twelve99.net [62.115.114.95]
8 21 ms 21 ms 23 ms ffm-b1-link.ip.twelve99.net [62.115.121.7]
9 23 ms 25 ms 23 ms kddi-ic319844-ffm-b1.ip.twelve99-cust.net [62.115.32.106]
10 19 ms 20 ms 19 ms 195.82.61.14
11 * 1347 ms * 195.82.50.230
12 23 ms 23 ms 23 ms 195.82.50.10

I've been disconnected multiple times too.

When I search around about this it's clear that it's very particular nodes people are having consistent problems with...

[joolzy]

the lag started early today, around 3:30pm pacific time.

5 7 ms 8 ms 5 ms 32.130.16.195
6 8 ms 8 ms 5 ms 192.205.36.158
7 6 ms 5 ms 5 ms ae-16.r22.atlnga05.us.bb.gin.ntt.net [129.250.5.57]
8 25 ms 25 ms 25 ms ae-6.r21.dllstx14.us.bb.gin.ntt.net [129.250.4.116]
9 * 63 ms 63 ms ae-2.r25.snjsca04.us.bb.gin.ntt.net [129.250.4.154]
10 137 ms 145 ms * ae-5.r24.snjsca04.us.bb.gin.ntt.net [129.250.3.146]
11 161 ms 157 ms 146 ms ae-4.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.57]
12 129 ms 134 ms 131 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [192.80.16.2]
13 107 ms * * 204.2.229.230
14 206 ms 173 ms 169 ms 204.2.229.96

[Jconix]

the lag started early today, around 3:30pm pacific time.

5 7 ms 8 ms 5 ms 32.130.16.195
6 8 ms 8 ms 5 ms 192.205.36.158
7 6 ms 5 ms 5 ms ae-16.r22.atlnga05.us.bb.gin.ntt.net [129.250.5.57]
8 25 ms 25 ms 25 ms ae-6.r21.dllstx14.us.bb.gin.ntt.net [129.250.4.116]
9 * 63 ms 63 ms ae-2.r25.snjsca04.us.bb.gin.ntt.net [129.250.4.154]
10 137 ms 145 ms * ae-5.r24.snjsca04.us.bb.gin.ntt.net [129.250.3.146]
11 161 ms 157 ms 146 ms ae-4.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.57]
12 129 ms 134 ms 131 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [192.80.16.2]
13 107 ms * * 204.2.229.230
14 206 ms 173 ms 169 ms 204.2.229.96

Just noticed this too.. x_x what the heck this is now so spontaneous it's getting more ridiculous now


Edit: Jeez. Today is by far the most worst day of ping spiking I've seen with one session happening mid day and having the usual ramp up as of right now.

[NevaehQuest]

So bad... the lag... even my friends thats playing single weaving job are complaining it today. every job with double weave is unplayable.
This is not animal crossing, we are trying to kill the boss before it kills us.
The biggest enemy here is not the boss but the freaking SE support.
I beat they are laughing at us right now saying' look at all this nerds caring about damage and weaving', because they don't give a damn.
What else am I supposed to react, its been a whole month. How can I tell when this is going to end?
Just remove all the job that require no server lag, nin, mnk, mch, rdm, gnb..... just remove ogcd altogether

[Naoki34]

"Poor" connection at the character selection screen.
Latency in-game.
Random disconnects.

It's hard to worry about that when I don't have connection or lag issues.

I have 20ms constant and when I'm connected, I stay connected all day.


And about : "Poor" connection at the character selection screen.
This is because of the congestion during the hours when most people are playing.

If the login server is overloaded, well, it is also overloaded to respond to the request sent to the login server to display your character.