Regarding ingame server lag serious issues

[BuffaloMagi]

I have been experiencing lag as well. Mine began around Monday. I live in Japan and play on an NA server, but had zero latency issues before Monday. Now I sometimes have to wait 6-10 seconds for actions to process. I guess the game is still playable, but it isn't very fun anymore. I have been playing conjurer and tried doing Halatali the other day. Managed to get through it, but it really hard to heal with that kind of lag. -_- I get error 90000 a fair amount too.

[Othin]

I am getting disconected every 10 - 20 min or so with alot of lag spikes too.

People here have already said what the issue was so i'll just post my findings.

I had no issues on JP server "Anima"


C:\>ping 124.150.157.50 -n 20

Pinging 124.150.157.50 with 32 bytes of data:
Reply from 124.150.157.50: bytes=32 time=185ms TTL=239
Reply from 124.150.157.50: bytes=32 time=190ms TTL=239
Reply from 124.150.157.50: bytes=32 time=186ms TTL=239
Reply from 124.150.157.50: bytes=32 time=188ms TTL=239
Reply from 124.150.157.50: bytes=32 time=185ms TTL=239
Reply from 124.150.157.50: bytes=32 time=207ms TTL=239
Reply from 124.150.157.50: bytes=32 time=191ms TTL=239
Reply from 124.150.157.50: bytes=32 time=195ms TTL=239
Reply from 124.150.157.50: bytes=32 time=195ms TTL=239
Reply from 124.150.157.50: bytes=32 time=197ms TTL=239
Reply from 124.150.157.50: bytes=32 time=202ms TTL=239
Reply from 124.150.157.50: bytes=32 time=192ms TTL=239
Reply from 124.150.157.50: bytes=32 time=183ms TTL=239
Reply from 124.150.157.50: bytes=32 time=202ms TTL=239
Reply from 124.150.157.50: bytes=32 time=186ms TTL=239
Reply from 124.150.157.50: bytes=32 time=183ms TTL=239
Reply from 124.150.157.50: bytes=32 time=189ms TTL=239
Reply from 124.150.157.50: bytes=32 time=209ms TTL=239
Reply from 124.150.157.50: bytes=32 time=183ms TTL=239
Reply from 124.150.157.50: bytes=32 time=184ms TTL=239

Ping statistics for 124.150.157.50:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 183ms, Maximum = 209ms, Average = 191ms

But on my "home" server Diabolos:

C:\>ping 199.91.189.45 -n 20

Pinging 199.91.189.45 with 32 bytes of data:
Reply from 199.91.189.45: bytes=32 time=32ms TTL=241
Reply from 199.91.189.45: bytes=32 time=27ms TTL=241
Reply from 199.91.189.45: bytes=32 time=26ms TTL=241
Reply from 199.91.189.45: bytes=32 time=28ms TTL=241
Reply from 199.91.189.45: bytes=32 time=27ms TTL=241
Reply from 199.91.189.45: bytes=32 time=26ms TTL=241
Reply from 199.91.189.45: bytes=32 time=29ms TTL=241
Request timed out.
Request timed out.
Reply from 199.91.189.45: bytes=32 time=27ms TTL=241
Reply from 199.91.189.45: bytes=32 time=30ms TTL=241
Reply from 199.91.189.45: bytes=32 time=29ms TTL=241
Reply from 199.91.189.45: bytes=32 time=27ms TTL=241
Reply from 199.91.189.45: bytes=32 time=28ms TTL=241
Reply from 199.91.189.45: bytes=32 time=29ms TTL=241
Reply from 199.91.189.45: bytes=32 time=28ms TTL=241
Reply from 199.91.189.45: bytes=32 time=26ms TTL=241
Reply from 199.91.189.45: bytes=32 time=26ms TTL=241
Reply from 199.91.189.45: bytes=32 time=29ms TTL=241
Reply from 199.91.189.45: bytes=32 time=29ms TTL=241

Ping statistics for 199.91.189.45:
Packets: Sent = 20, Received = 18, Lost = 2 (10% loss),
Approximate round trip times in milli-seconds:
Minimum = 26ms, Maximum = 32ms, Average = 27ms

[Cyrus-Wallace]

I've been playing yesterday and I experienced lag, random freezes, 90k errors and it was totally unplayable. I am playing with my GF, she sits next to me and she experienced lag as well. The curious thing is that she didn't experience freezes when I did and vice versa. So, it wasn't my ISP. Also, during the early access, I played without lag issues.

[BlossomRose]

It has nothing to do with ISPs yeah. Some of SE's servers are broken. You'd be confused because they're refusing to say anything about it.

[Aesthphron]

Hello all! First of all, thanks you for all your information on this issue, you've all been very thorough. As this is an issue that cannot be readily solved via the forums, I'm going to lock this thread so we can investigate the issue further. Thank you for all your patience, and I apologize for any inconvenience you may have been caused.