Will performing the traceroute at any time be helpful, or should I wait until the next time the issue occurs?
Printable View
I have temporarily worked around my 90002 error disconnects by trialling the Mudfish.Net service that was mentioned here and in other forums. It seems to route the traffic differently to avoid the problem area on NTT/Square's network. I also seem to get a slightly better ping with Mudfish. It is not ideal though and I am not entirely comfortable about having to use a 3rd party service to play the game.
I'm having the same issues, spectum is my ISP, and I've done an traceRT from my IP to the IP of the server that I am on (merilith/dynamis) and noticed that the high ping is coming from servers labeled "Us.bb.gin.ntt.net"
https://i.imgur.com/wBxXiXL.png
This keeps happening last week, and the week before... It even happen to me during my raiding times before 11 pm EST, and had the call the raid early due to my poor internet performance.
This needs to end, I can't sacrifice more precious time when me and my team are progging though savage this tier, and these us.bb.gin.ntt.net servers keep acting up.
I'm even helping my fellow friends though content and this keep happening at the time they finally about to hit the dungeon, and suddenly my ping goes from 82 ms to 333 ms, and keep hovering between 282 ms to 333 ms.
I just had this issue start to affect me as well. Going to be submitting the tracert to SE.
Every thing was fine for me for like a week or so, but as of last night, the lag is back, and last I looked, the internet in my area seemed to be just fine, so it's clearly not my fault. I need to check the ping again to see where the packet drops keep happening, but I've no doubt that with everyone else having this problem, that it's NTT's servers.
I was able to subvert the NTT problem by using a VPN to canada, dropped the 286-333 ms ping to a 150-190 ms ping. Still double my average ping which is 70-90 ms, but doable.