Problems with connection (R0) lag

[Trick01]

This is how pinging Phoenix looks:
Reply from 199.91.189.42: bytes=32 time=138ms TTL=240
Request timed out.
Reply from 199.91.189.42: bytes=32 time=136ms TTL=240
Reply from 199.91.189.42: bytes=32 time=148ms TTL=240
Reply from 199.91.189.42: bytes=32 time=143ms TTL=240
Reply from 199.91.189.42: bytes=32 time=136ms TTL=240
Reply from 199.91.189.42: bytes=32 time=147ms TTL=240
Reply from 199.91.189.42: bytes=32 time=152ms TTL=240
Reply from 199.91.189.42: bytes=32 time=135ms TTL=240
Reply from 199.91.189.42: bytes=32 time=135ms TTL=240
Reply from 199.91.189.42: bytes=32 time=141ms TTL=240
Reply from 199.91.189.42: bytes=32 time=136ms TTL=240
Reply from 199.91.189.42: bytes=32 time=137ms TTL=240
Reply from 199.91.189.42: bytes=32 time=138ms TTL=240
Reply from 199.91.189.42: bytes=32 time=135ms TTL=240
Reply from 199.91.189.42: bytes=32 time=129ms TTL=240
Reply from 199.91.189.42: bytes=32 time=137ms TTL=240
Reply from 199.91.189.42: bytes=32 time=131ms TTL=240
Reply from 199.91.189.42: bytes=32 time=130ms TTL=240
Reply from 199.91.189.42: bytes=32 time=134ms TTL=240
Reply from 199.91.189.42: bytes=32 time=129ms TTL=240
Reply from 199.91.189.42: bytes=32 time=138ms TTL=240
Reply from 199.91.189.42: bytes=32 time=137ms TTL=240
Reply from 199.91.189.42: bytes=32 time=131ms TTL=240
Reply from 199.91.189.42: bytes=32 time=148ms TTL=240
Reply from 199.91.189.42: bytes=32 time=139ms TTL=240
Reply from 199.91.189.42: bytes=32 time=137ms TTL=240
Reply from 199.91.189.42: bytes=32 time=139ms TTL=240
Reply from 199.91.189.42: bytes=32 time=144ms TTL=240
Reply from 199.91.189.42: bytes=32 time=130ms TTL=240
Reply from 199.91.189.42: bytes=32 time=131ms TTL=240
Reply from 199.91.189.42: bytes=32 time=133ms TTL=240
Request timed out.
Reply from 199.91.189.42: bytes=32 time=148ms TTL=240
Reply from 199.91.189.42: bytes=32 time=129ms TTL=240
Reply from 199.91.189.42: bytes=32 time=133ms TTL=240
Reply from 199.91.189.42: bytes=32 time=136ms TTL=240
Reply from 199.91.189.42: bytes=32 time=130ms TTL=240
Reply from 199.91.189.42: bytes=32 time=141ms TTL=240
Reply from 199.91.189.42: bytes=32 time=143ms TTL=240
Reply from 199.91.189.42: bytes=32 time=146ms TTL=240
Reply from 199.91.189.42: bytes=32 time=130ms TTL=240
Reply from 199.91.189.42: bytes=32 time=140ms TTL=240
Reply from 199.91.189.42: bytes=32 time=131ms TTL=240
Reply from 199.91.189.42: bytes=32 time=137ms TTL=240
Reply from 199.91.189.42: bytes=32 time=138ms TTL=240
Reply from 199.91.189.42: bytes=32 time=138ms TTL=240
Reply from 199.91.189.42: bytes=32 time=131ms TTL=240
Reply from 199.91.189.42: bytes=32 time=146ms TTL=240
Reply from 199.91.189.42: bytes=32 time=129ms TTL=240
Reply from 199.91.189.42: bytes=32 time=131ms TTL=240
Reply from 199.91.189.42: bytes=32 time=137ms TTL=240
Reply from 199.91.189.42: bytes=32 time=140ms TTL=240
Request timed out.
Request timed out.
Request timed out.
Reply from 199.91.189.42: bytes=32 time=139ms TTL=240

This is how pinging google looks:
Reply from 173.194.44.50: bytes=32 time=26ms TTL=56
Reply from 173.194.44.50: bytes=32 time=30ms TTL=56
Reply from 173.194.44.50: bytes=32 time=31ms TTL=56
Reply from 173.194.44.50: bytes=32 time=27ms TTL=56
Reply from 173.194.44.50: bytes=32 time=26ms TTL=56
Reply from 173.194.44.50: bytes=32 time=27ms TTL=56
Reply from 173.194.44.50: bytes=32 time=26ms TTL=56
Reply from 173.194.44.50: bytes=32 time=35ms TTL=56
Reply from 173.194.44.50: bytes=32 time=25ms TTL=56
Reply from 173.194.44.50: bytes=32 time=27ms TTL=56
Reply from 173.194.44.50: bytes=32 time=31ms TTL=56
Reply from 173.194.44.50: bytes=32 time=28ms TTL=56
Reply from 173.194.44.50: bytes=32 time=26ms TTL=56
Reply from 173.194.44.50: bytes=32 time=25ms TTL=56
Reply from 173.194.44.50: bytes=32 time=26ms TTL=56
Reply from 173.194.44.50: bytes=32 time=28ms TTL=56
Reply from 173.194.44.50: bytes=32 time=27ms TTL=56
Reply from 173.194.44.50: bytes=32 time=58ms TTL=56
Reply from 173.194.44.50: bytes=32 time=30ms TTL=56
Reply from 173.194.44.50: bytes=32 time=58ms TTL=56
Reply from 173.194.44.50: bytes=32 time=25ms TTL=56
Reply from 173.194.44.50: bytes=32 time=29ms TTL=56
Reply from 173.194.44.50: bytes=32 time=26ms TTL=56
Reply from 173.194.44.50: bytes=32 time=28ms TTL=56
Reply from 173.194.44.50: bytes=32 time=26ms TTL=56
Reply from 173.194.44.50: bytes=32 time=29ms TTL=56
Reply from 173.194.44.50: bytes=32 time=28ms TTL=56
Reply from 173.194.44.50: bytes=32 time=28ms TTL=56
Reply from 173.194.44.50: bytes=32 time=28ms TTL=56
Reply from 173.194.44.50: bytes=32 time=28ms TTL=56
Reply from 173.194.44.50: bytes=32 time=40ms TTL=56
Reply from 173.194.44.50: bytes=32 time=25ms TTL=56
Reply from 173.194.44.50: bytes=32 time=29ms TTL=56
Reply from 173.194.44.50: bytes=32 time=27ms TTL=56
Reply from 173.194.44.50: bytes=32 time=25ms TTL=56
Reply from 173.194.44.50: bytes=32 time=29ms TTL=56
Reply from 173.194.44.50: bytes=32 time=27ms TTL=56
Reply from 173.194.44.50: bytes=32 time=32ms TTL=56
Reply from 173.194.44.50: bytes=32 time=25ms TTL=56
Reply from 173.194.44.50: bytes=32 time=38ms TTL=56
Reply from 173.194.44.50: bytes=32 time=30ms TTL=56
Reply from 173.194.44.50: bytes=32 time=25ms TTL=56
Request timed out.
Reply from 173.194.44.50: bytes=32 time=25ms TTL=56
Reply from 173.194.44.50: bytes=32 time=28ms TTL=56
Reply from 173.194.44.50: bytes=32 time=28ms TTL=56
Reply from 173.194.44.50: bytes=32 time=25ms TTL=56
Reply from 173.194.44.50: bytes=32 time=27ms TTL=56
Reply from 173.194.44.50: bytes=32 time=28ms TTL=56
Reply from 173.194.44.50: bytes=32 time=25ms TTL=56
Reply from 173.194.44.50: bytes=32 time=27ms TTL=56
Reply from 173.194.44.50: bytes=32 time=29ms TTL=56
Reply from 173.194.44.50: bytes=32 time=25ms TTL=56
Reply from 173.194.44.50: bytes=32 time=25ms TTL=56
Reply from 173.194.44.50: bytes=32 time=27ms TTL=56
Reply from 173.194.44.50: bytes=32 time=25ms TTL=56
Reply from 173.194.44.50: bytes=32 time=27ms TTL=56
Reply from 173.194.44.50: bytes=32 time=29ms TTL=56
Reply from 173.194.44.50: bytes=32 time=25ms TTL=56
Reply from 173.194.44.50: bytes=32 time=27ms TTL=56
Reply from 173.194.44.50: bytes=32 time=28ms TTL=56
Reply from 173.194.44.50: bytes=32 time=29ms TTL=56
Reply from 173.194.44.50: bytes=32 time=29ms TTL=56
Reply from 173.194.44.50: bytes=32 time=30ms TTL=56
Reply from 173.194.44.50: bytes=32 time=25ms TTL=56
Reply from 173.194.44.50: bytes=32 time=27ms TTL=56
Reply from 173.194.44.50: bytes=32 time=25ms TTL=56
Reply from 173.194.44.50: bytes=32 time=25ms TTL=56
Reply from 173.194.44.50: bytes=32 time=25ms TTL=56
Reply from 173.194.44.50: bytes=32 time=27ms TTL=56
Reply from 173.194.44.50: bytes=32 time=26ms TTL=56
Reply from 173.194.44.50: bytes=32 time=25ms TTL=56
Reply from 173.194.44.50: bytes=32 time=29ms TTL=56
Reply from 173.194.44.50: bytes=32 time=29ms TTL=56
Reply from 173.194.44.50: bytes=32 time=26ms TTL=56
Reply from 173.194.44.50: bytes=32 time=28ms TTL=56
Reply from 173.194.44.50: bytes=32 time=25ms TTL=56
Reply from 173.194.44.50: bytes=32 time=30ms TTL=56
Reply from 173.194.44.50: bytes=32 time=26ms TTL=56
Reply from 173.194.44.50: bytes=32 time=26ms TTL=56
Reply from 173.194.44.50: bytes=32 time=29ms TTL=56
Reply from 173.194.44.50: bytes=32 time=25ms TTL=56
Reply from 173.194.44.50: bytes=32 time=27ms TTL=56
Reply from 173.194.44.50: bytes=32 time=25ms TTL=56
Reply from 173.194.44.50: bytes=32 time=27ms TTL=56

I do get about 1% packet loss in general it seems, but it's not nearly as much as I get with phoenix.

[Paintballrulz]

They just did a network maintenance , didn;t change a damn thing i still lag everytime i get in the game and disconnect with error 90000 again. I am starting to think none of them know how servers work.

[Lytir]

I am also randomly freezing for a period of time which varies, in dungeons it's usually a longer time than when I am questing on my own. I'm sure it has something to do with the fact I'm playing on a JP world and not an NA/EU world. I am hoping that server transfers which are due to come in mid-September will allow me to change to a NA/EU server, and hopefully sort out my issue.

[Vespar]

I am also randomly freezing for a period of time which varies, in dungeons it's usually a longer time than when I am questing on my own. I'm sure it has something to do with the fact I'm playing on a JP world and not an NA/EU world. I am hoping that server transfers which are due to come in mid-September will allow me to change to a NA/EU server, and hopefully sort out my issue.

It is not the world you are on, myself and many others have attempted to create characters on other worlds to test this, and we still get the same lag, be it JP server or a NA/EU one.

[Lytir]

It is not the world you are on, myself and many others have attempted to create characters on other worlds to test this, and we still get the same lag, be it JP server or a NA/EU one.

That's depressing, I hope it gets sorted out soon, after all the errors and inability to log on, this is a real kick in the pants as it's not very fun playing by myself, which for me is really the only option as joining dungeons with this sort of lag/freezing is rendering me useless.

If anyone has ever seen "Bernard's Watch" on UK Television, this is similar to what I am experience, I being in Bernards shoes, and I guess this "Receiving" thing to be the watch. At the end of this period of seemingly stopped time, everything goes very fast, playing out all the things that would have happened to/from me and to/from others, during that time.

[Paintballrulz]

That's depressing, I hope it gets sorted out soon, after all the errors and inability to log on, this is a real kick in the pants as it's not very fun playing by myself, which for me is really the only option as joining dungeons with this sort of lag/freezing is rendering me useless.

Yeah pretty nice how 1-2 day before fixing the log in servers we get another bug even worst than the error 1017 , i miss that error now , i do not mind spamming my 0 key for 15min to get in and then play the game with no problem , now yes i can log in with no error 1017 but when i get in i lag and get disconnect error 90000 maximum 5-10min after getting in the game. I just hope this can be fixed soon i am so tire of this right now -.-

[mishins]

I am having the same issue, sent in a help ticket with customer support, still no reply. I am getting very frustrated. I can't complete a single dungeon all the way through without lagging/R=0 every 30-90 seconds, and then error 90000 disconnecting me, which then prohibits me from joining back up into the instance I was just in, having to start ALL OVER again and again and again and again and again. Can SE please update us on the current situation with this issue? Has it even been addressed? ISP running great, modem and router the same. What is going on?

[Gebeleizis]

They dont care, they just want the free month to go away and people to leave so they can spent as little as possible on servers. Its an outrage to add 1 new server when you know all the other servers where full but again most will leave after free month so from management point of view its a bad investment to get more servers for 1 month.

[Horatium]

They dont care, they just want the free month to go away and people to leave so they can spent as little as possible on servers. Its an outrage to add 1 new server when you know all the other servers where full but again most will leave after free month so from management point of view its a bad investment to get more servers for 1 month.

is not that easy to find solutions...
I'm not network expert, but i know some things, there are tons of rules on routers/firewalls and you need time to find out which cause problem, because in my opinion, they added some rules on 2nd Sept which cause the problem we have. Or maybe they added a new device which is not properly configured.
We just have to hope they have an inspired guy in their NOC, who know where to look to fix the problem... if they dont have that guy, it might take days/weeks till the they find the problem

[Gebeleizis]

is not that easy to find solutions...
I'm not network expert, but i know some things, there are tons of rules on routers/firewalls and you need time to find out which cause problem, because in my opinion, they added some rules on 2nd Sept which cause the problem we have. Or maybe they added a new device which is not properly configured.
We just have to hope they have an inspired guy in their NOC, who know where to look to fix the problem... if they dont have that guy, it might take days/weeks till the they find the problem

Its not the rules or software problem its a hardware problem, they dont have proper equipment to handle this and I dont think they will add more.