Get WTFast. Or mudfish, I use WTFast, and it will solve the problems. Its not a perfect solution, but it does fix the issue everyone is experiencing with the NA servers.
Get WTFast. Or mudfish, I use WTFast, and it will solve the problems. Its not a perfect solution, but it does fix the issue everyone is experiencing with the NA servers.
WTFast will not fix the problem.
fixed it for me, since it cut out the ntt network entirely. So
If anyone use mudfish can someone tel me what setting you guys use? Did you guys set it to auto?
I'm sure it does work for many. However, if more and more started using these VPN services SE would know less about how bad their service is and take a longer time to resolve any problems. I know for a fact that if a VPN worked for me, I would not be posting here as much. And of course, you could say, "That's great, you can have a good time in game now!". But unfortunately for me, I'm stubborn and also don't like the idea of stacking subscription services. It makes me feel dirty. (lol)
Oh I agree they need to do something. I know I never had lag like this before the server move. I just wanted to give the option to people who it may work for. Its not a perfect solution, and won't work for everyone, but it might for some. Since SE doesn't seem to have any idea how to fix it, and our isp's basically say its the ntt network so they can't do anything either, we're stuck.
Connection Issues: Lag/Pausing (Other players and mobs stand still for up to 1 minute before a time compression of thos events occour), Disconnection (sometimes instead of time compression, I loose connection to the server)
My ISP: Xfinity (Comcast)
Frequency: Almost daily, usually after 8pm EST
Traceroute:
# traceroute -n 209.2.229.9
traceroute to 209.2.229.9 (209.2.229.9), 30 hops max, 60 byte packets
1 96.120.4.57 15.621 ms 21.475 ms 22.394 ms
2 68.85.173.193 22.546 ms 22.596 ms 22.476 ms
3 162.151.88.62 24.930 ms 24.951 ms 24.990 ms
4 68.86.93.125 25.655 ms 25.127 ms 24.997 ms
5 68.86.85.246 23.279 ms 23.372 ms 23.430 ms
6 50.242.148.190 23.465 ms 12.678 ms 14.938 ms
7 154.54.6.117 13.935 ms 13.601 ms 12.551 ms
8 154.54.24.221 44.556 ms 44.059 ms 43.935 ms
9 154.54.40.109 43.554 ms 43.644 ms 42.413 ms
10 154.54.84.214 42.540 ms 42.429 ms 42.467 ms
11 38.122.8.210 41.019 ms 41.751 ms 41.956 ms
12 128.59.255.10 52.225 ms 52.044 ms 52.102 ms
13 128.59.255.13 38.934 ms 38.107 ms 42.754 ms
14 128.59.255.226 43.375 ms 43.214 ms 43.356 ms
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 *^C
This has been going on for two months now.
WTFast for me doesn't fix the issue. I don't see the lag, rubberband effect but I get hit by AOEs while moving away with a decent time.
I have some ping test from NA Servers from early in the morning and around peak times (7 - 10PM EST):
MORNING:
http://i217.photobucket.com/albums/c...pswnvaz608.png
EVENING:
http://i217.photobucket.com/albums/c...psxftgapnn.png
Location: Puerto Rico
ISP: AT&T
It looks like the traffic going from NTT xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net (129.250.195.46) to FFXIV Servers is getting LOOOT of packet drops there. As many people have said before for me this will be my last post, I think only a blind person would not see whats going on here. NTT is the problem and if SE is not doing something regarding the situation and contacting them this will not change. Will not going to continue wasting time running test when everything Points to a very specific problem and thats NTT
Runsell, what kind of lag are you experiencing and how often? If you are getting hit by AoE all the time even if you clearly moved out of it, then you are definitely experiencing lag. Just curious how often you notice it. Also, those packet losses that you are seeing is pretty normal. Mine sits at around 20% but the game runs fine for me.
Einmimiria,
I am going to be very direct here as the information provided by you on this is inaccurate as I work for an ISP and I am having this same problem that everyone else is having and it is NTT specifically and I have looked at other's routing tables. When you look at a trace route the first 4 hops are your customer's ISP, once it is past that portion this is the routing table configured specifically for your company (Square Enix) to reach the customer who is paying to have access to the game. From every hop I'm seeing including my own these customers are well past the ISP so instead of giving false information, let's be clear that the issue are not on multiple ISP's but in nature the routing table which the breakdown is where the route is set up for the Square Enix servers that run through NTT. It's time to own up and fix and issue instead of passing the blame. Let's work to get the issue resolved and stop pointing the finger whereas Square needs to contact whom sets up the routing for the servers and have NTT removed from that route, end of story. As an fyi mine is happening at night as well and it is really bad. When is this going to be addressed and fixed? This has gone on long enough and I'm paying for something I can't use!
The koreans only make your connection less consistent, make you lag more.
The only solution is a location that isn't shit, ex: Chicago.
The game is almost totally unplayable for me now with all this lag. There's no reason to continue my sub if I can't play with my friends during the evening hours.
Time of trace: ~9:30pm CSTCode:Tracing route to 204.2.229.97 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms RT-AC68U-5570 [192.168.1.1]
2 10 ms 14 ms 8 ms 96.120.28.53
3 10 ms 9 ms 8 ms te-0-7-0-8-sur03.chicago301.il.chicago.comcast.net [68.85.180.45]
4 9 ms 9 ms 8 ms 68.85.183.142
5 14 ms 11 ms 11 ms be-144-ar01.area4.il.chicago.comcast.net [162.151.45.69]
6 11 ms 12 ms 10 ms be-33491-cr02.350ecermak.il.ibone.comcast.net [68.86.91.165]
7 10 ms 10 ms 9 ms be-10577-pe03.350ecermak.il.ibone.comcast.net [68.86.86.2]
8 15 ms 13 ms 11 ms ae-26.a02.chcgil09.us.bb.gin.ntt.net [129.250.66.65]
9 177 ms 186 ms * ae-3.r07.chcgil09.us.bb.gin.ntt.net [129.250.5.111]
10 11 ms 10 ms 9 ms ae-5.r21.chcgil09.us.bb.gin.ntt.net [129.250.4.213]
11 178 ms 187 ms 79 ms ae-5.r22.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
12 96 ms 101 ms 96 ms ae-40.r02.snjsca04.us.bb.gin.ntt.net [129.250.3.121]
13 * 186 ms 185 ms ae-3.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.11]
14 190 ms 192 ms * xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
15 84 ms * * 204.2.229.234
16 189 ms 188 ms 185 ms 204.2.229.97
Trace complete.
You really expect me to play in that?
Still continuing to investigate? Stormblood launched on June 20, 2017. Today is March 6, 2018. Nearly 9 months later. How much more "investigating" do you expect your players to put up with?
^this thing has happen ever since heavensward era some just got “lucky” like me who start seeing this error after stormblood start.
They have no excuse, they will keep going in “investigating” status as long as player who has no problem with this game still in higher ratio than the one who has problem like us. In other words, we are not priority
My concern is that I am thinking SE is not going to do anything. On Another post here in the forum:
http://forum.square-enix.com/ffxiv/t...=1#post4508492
One of the moderator said and I quote:
It looks they are not going to find a solution to our problems. I do have less hops and packet drops to EU Servers!. I made a character there and I didn't notice any lag at all, obviously a higher pings around 190ms from my end, but when NTT gets congested I get between 250 - 300ms with packet drops. I wouldn't like to move my character because of lot of friends I have made in the past and my current house.Quote:
Hello All!
We do apologize for the inconvenience you have experienced. We are trying to find the best way to assist everyone with their connection issues, but because of the dynamic nature of the network and the multiple parties involved, we have little control over the matter. Please note that there are many parties/companies between you and the servers, this means that if there is a hiccup along the way (sometimes caused by local conditions), we may have trouble assisting. The nodes through Los Angeles (operated by NTT) has no connection or affiliation with Square Enix. Because of this, we recommend that you report your connection issues and packet loss to your ISP and specify exactly where the problem is occurring. We are escalating this on our side as well so it can be investigated and reported. Unfortunately, we cannot get a fix at this time, but we hope we can assist in any way we can.
Thank you for playing Final Fantasy XIV!
Interesting find Runsell...
It seems that when they purged the tech forum a month ago or so the mod team moved a bunch of posts regarding lag to the locked forums and swept it under the rug. I know my original post was moved to "closed concern" regarding the poor lag with NTT. The mod team also condensed and combined a ton of threads regarding the issue into this sticky post. That may be why there were so many back to back mod posts in that thread.
I would hope now with the amount of people who are posting in this sticky accelerates the process in seeking a resolve. I almost think moving the servers back to Montreal would give us less problems.
I've been working on this issue with a friend of mine, while I don't currently have his tracert's it stems from the connection to NTT nodes. Until these are fixed, the problems will NOT go away.
I myself havent had any issues with lag or dc's. So why is it fine for some but so bad for most?
I'm just loving the packet loss. Makes gathering and crafting just that much more annoying. Maybe it'll be fixed by 5.0, or maybe 6.0. I do love corporate speak promises after all.
Code:Target Name: 204.2.229.9
IP: 204.2.229.9
Date/Time: 3/8/2018 4:18:46 PM - 3/8/2018 4:28:46 PM
Hop Sent PL% Min Avg Host Name / [IP]
1 598 0 2.12 5.15 192.168.43.1 [192.168.43.1]
2 598 0 86.56 114.52 172.26.96.169 [172.26.96.169]
3 598 0 84.88 114.75 107.72.233.4 [107.72.233.4]
4 598 0 85.71 112.63 12.83.188.161 [12.83.188.161]
5 598 0 83.87 112.83 12.83.179.49 [12.83.179.49]
6 598 0 88.41 115.06 ggr2.la2ca.ip.att.net [12.122.128.101]
7 598 5 190.94 225.19 ae-5.a00.lsanca20.us.bb.gin.ntt.net [129.250.9.61]
8 597 6 205.12 236.73 ae-3.r01.lsanca20.us.bb.gin.ntt.net [129.250.2.233]
9 598 5 196.00 230.99 ae-8.r23.lsanca07.us.bb.gin.ntt.net [129.250.6.48]
10 598 8 202.46 237.66 ae-12.r22.snjsca04.us.bb.gin.ntt.net [129.250.4.150]
11 598 7 207.44 243.16 ae-19.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.27]
12 598 7 206.82 240.38 ae-4.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.57]
13 598 7 205.06 241.06 xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
14 596 42 210.15 245.20 204.2.229.234 [204.2.229.234]
15 596 8 205.27 241.30 204.2.229.9 [204.2.229.9]
Square, it's been five months since this thread was created, and the problem had existed for weeks or months before that. This is beyond ridiculous. I finally, FINALLY got my husband to agree to play ffxiv with me, and he does enjoy it, but he has very little patience for this kind of constant disruption and won't pay a sub if it continues. I can't play a healing class when I'm constantly being dropped off the server during duties, leaving the rest of the party to wipe. My Twitch stream focuses on FFXIV and answering questions for people interested in trying the game out. I'm sure you can imagine what kind of impression the constant lag, rubberbanding, and disconnecting is making on potential players.
This is the only game my husband and I have this issue with. He works in cable and internet installation, so I'm confident when I say that we've verified that the problem is not on our end. Saying "well golly gee" and washing your hands of it is not acceptable, nor is it the kind of answer I'd expect from a company that wants to continue growing their customer base.
I don't have anything in specific to say in this post - all of the concerns that I want to raise or issues that I want to vent about have already been done so by numerous other posters aside from me. All I really want to do is add one more voice to the countless that are telling you, Square Enix:
Get better servers.
I unsubbed from this game several months ago when half of my raid disconnected at 5% on Neo ExDeath when we were on record for a new personal best in terms of kill time. Half of the raid. Not one person. Four people. All from different locations, all on different ISPs. That can't be all four of them each having individual issues all that the same time. That is a *categorical failure* on Square Enix's part to provide proper server infrastructure for their game. You can try to pass the blame off onto your customers or onto the people who run your servers all you want, but this is *your game* that people are unable to play.
I resubbed at the behest of my raid group for 4.2, but if this disgusting latency where-in I can barely play the game because of how often and to what degree it occurs continues to do so, I will unsub again, and this time, I won't be coming back.
I pay you a monthly subscription to provide me with game servers which I can actually reliably play on. I do not pay you a monthly subscription to provide me with substandard game servers where latency is the rule rather than the exception.
I know that the moderators in these threads aren't the ones who make these sort of decisions. But I do know they can escalate it to those who do. So, my dear moderators, I'm telling you:
Escalate this situation, or tell your bosses that they will continue bleeding subscribers due to latency issues.
This has to be some of the worst networking I have ever seen. NTT advertises to be reliable. Far From it.
I'm still livid. It's every day. Every DAY!
8:00 PM, USA Central, Illinois. Comcast. Time for the mod to feed us the "looking into it" bit again soon.
Code:Tracing route to 204.2.229.97 over a maximum of 30 hops
1 1 ms 1 ms 1 ms 10.0.0.1
2 10 ms 11 ms 16 ms 96.120.24.33
3 9 ms 8 ms 9 ms GE-1-46-ur01.mortongrove.il.chicago.comcast.net [68.86.117.209]
4 9 ms 9 ms 12 ms 162.151.37.113
5 11 ms 9 ms 12 ms be-124-ar01.elmhurst.il.chicago.comcast.net [69.139.235.53]
6 11 ms 14 ms 12 ms be-33491-cr01.chicago.il.ibone.comcast.net [68.86.92.33]
7 13 ms 13 ms 14 ms be-10506-cr02.350ecermak.il.ibone.comcast.net [68.86.86.229]
8 12 ms 12 ms 19 ms be-10577-pe03.350ecermak.il.ibone.comcast.net [68.86.86.2]
9 88 ms 93 ms 104 ms ae-26.a02.chcgil09.us.bb.gin.ntt.net [129.250.66.65]
10 178 ms 184 ms 182 ms ae-3.r07.chcgil09.us.bb.gin.ntt.net [129.250.5.111]
11 * 117 ms 136 ms ae-5.r21.chcgil09.us.bb.gin.ntt.net [129.250.4.213]
12 193 ms 168 ms 184 ms ae-5.r22.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
13 180 ms 190 ms 189 ms ae-19.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.27]
14 191 ms * 201 ms ae-4.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.57]
15 192 ms * 184 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
16 143 ms 138 ms * 204.2.229.234
17 194 ms 200 ms 188 ms 204.2.229.97
Trace complete.
On one hand, I understand Square's position (below). Obviously, they cannot control that which is out of their control. On the other hand, it is by their own admission here that they understand how the Internet can be volatile. To this end, other games and services deal with the same Internet network challenges...and do not break!
Our user-voice focus should not be on trying to compel Square to work with various network providers, with whom they have no affiliation. Instead, let's focus on what Square does: they write software, and the FFXIV game client should be more fault tolerant.
As a user, I would like my game client to not disconnect from the server due to nominal network provider packet loss.
How do we +1 this feature request?
Quote:
Hello All!
We do apologize for the inconvenience you have experienced. We are trying to find the best way to assist everyone with their connection issues, but because of the dynamic nature of the network and the multiple parties involved, we have little control over the matter. Please note that there are many parties/companies between you and the servers, this means that if there is a hiccup along the way (sometimes caused by local conditions), we may have trouble assisting. The nodes through Los Angeles (operated by NTT) has no connection or affiliation with Square Enix. Because of this, we recommend that you report your connection issues and packet loss to your ISP and specify exactly where the problem is occurring. We are escalating this on our side as well so it can be investigated and reported. Unfortunately, we cannot get a fix at this time, but we hope we can assist in any way we can.
Thank you for playing Final Fantasy XIV!
Unfortunately, a feature like this isn't exactly viable. The client can only be so resilient to connection issues and packet loss before it disconnects. We can't improve the connectivity through the client in this way. Nor would this solve the latency issues as the information is not getting to the client fast enough. I like the idea, but I'm not sure it would work the way you are describing.
It's definitely not simple, but please understand when we say that literally every other online game handles real-world latency and packetloss better than FFXIV does. Since they're all operating over the same internet, that leaves the game client and the server, and by and large it's the client doing the disconnecting (90002).
For me, I get better and more stable connections when playing FFXI... in f'ing Japan.... than I do playing FFXIV in the evenings.
I'm also getting disconnects, rubber-banding, and losing combos because skills would go on cooldown but not firing. It's happening a lot more recently to the point where doing raids is impossible.
Tracert at around ~12am 3/14:
Tracing route to 204.2.229.9 over a maximum of 30 hops
.
.
.
4 10 ms 10 ms 8 ms ool-4353f912.dyn.optonline.net [67.83.249.18]
5 9 ms 8 ms 9 ms 67.59.239.235
6 14 ms 12 ms 12 ms 451be049.cst.lightpath.net [65.19.114.73]
7 * 12 ms 14 ms lag-150.ear1.NewYork1.Level3.net [4.35.80.5]
8 * * * Request timed out.
9 13 ms 14 ms 13 ms NTT-level3-90G.NewYork1.Level3.net [4.68.110.74]
10 96 ms 98 ms 96 ms ae-54.r08.nycmny01.us.bb.gin.ntt.net [129.250.5.90]
11 13 ms 12 ms * ae-3.r24.nycmny01.us.bb.gin.ntt.net [129.250.5.61]
12 78 ms 76 ms 82 ms ae-2.r20.sttlwa01.us.bb.gin.ntt.net [129.250.4.13]
13 89 ms 77 ms 76 ms ae-0.r21.sttlwa01.us.bb.gin.ntt.net [129.250.2.54]
14 97 ms * 97 ms ae-3.r23.snjsca04.us.bb.gin.ntt.net [129.250.3.124]
15 97 ms 96 ms 96 ms ae-45.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.175]
16 96 ms 96 ms 98 ms ae-4.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.57]
17 99 ms 96 ms 96 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
18 * 97 ms 96 ms 204.2.229.234
19 97 ms 96 ms 100 ms 204.2.229.9
Trace complete.
I don't know if the world I'm on matters, because it's happening in cross-server instances, but I am on Balmung.
Started yesterday getting disconnects from the server and lags.
Forgive me for bad English
Time: 21:00 GMT
Quote:
Tracing route to 195.82.50.48 over a maximum of 30 hops
5 1 ms 2 ms 2 ms vla06.vla21.transtelecom.net [217.150.40.86]
6 19 ms 19 ms 19 ms 212.73.250.154
7 21 ms 21 ms 21 ms lag-120.ear2.Stockholm2.Level3.net [212.73.250.153]
8 40 ms 40 ms 41 ms ae-2-3207.edge5.Frankfurt1.Level3.net [4.69.163.22]
9 41 ms 42 ms 46 ms 212.162.4.98
10 47 ms 47 ms 54 ms 195.82.60.29
11 40 ms 40 ms 40 ms 195.82.61.14
12 * 41 ms 41 ms 195.82.50.234
13 42 ms 41 ms 41 ms 195.82.50.48
Every evening the game becomes unplayable without use of a third party VPN. It has been months with no real indication that SE is taking any action with NTT to pressure them to fix this issue with Comcast and other ISP's. Tonight was so bad that I missed the entire trial from beginning to end before the client caught up with the traffic. What if players report me for being AFK or griefing when I had absolutely no control over the situation?
During that time this is what my trace looked like:
https://i.imgur.com/vf1Htrh.png
This was around 9:10pm EDT 3/15/2018.
I do not experience these problems on my PS4. Why would that be? Don't you think that this suggests the one client on the PS4 is more resilient than on the PC, Einmimiria?
Several others report the same pattern:
- PC = disconnects
- PS4 = stable
I am now exclusively playing on a PS4 Pro for this reason. I'd be curious to know whether or not the devs know that users on the same ISP using a different client/platform are not having the problem..
Thank you for patience and assistance while we worked with the upstream ISP in question to investigate the connection issues that have been reported throughout the thread. These reports, details, and traceroutes aided our infrastructure teams in conducting detailed investigations into the difficulties connecting to FINAL FANTASY XIV through certain upstream ISP servers. As a result of this investigation, it was found that the issues were not related to the FINAL FANTASY XIV servers. As such, we have also been sharing the collected data with the upstream ISP in question for further reviews and investigations.
We apologize that these difficulties have been ongoing, and that we don’t have an immediate resolution to share. Although we have no direct control of the situation, we’ll continue to work with the upstream ISP to investigate whether there are any specific troubles that they can isolate and work towards a solution. We’ll also share any additional updates should they become available.
If you wish to make detailed reports about your connection difficulties, we recommend contacting your local ISP directly to try to improve your connection with the upstream ISP.
Thank you again for your patience and assistance throughout this process.
Are they disconnecting or lagging, or both?
Let me better characterize my experience:
Latency and Lag
I really almost never have any lag or latency related issues on either PC or PS4. Maybe those having latency/lag issues are having a slightly different, but perhaps related issue?
PL and disconnects
- PS4: I never get disconnected on my PS4.
- PC: I constantly (1x per hour, at least) get DCd on my PC.
In this latter case (on the topic of disconnects), it seems quite a strange coincidence ... given the consistency of the problem.
Numerous people in this thread have already reported that NTT (the ISP in question) isn't interested in hearing from people that aren't their customers. YOU are their customer. WE are not. They could not possibly give less of a crap what WE think about their service because they don't server us, they server YOU.
This thread & Reddit confirm we cant do anything.It only you SE who can do something because you are customer & it you're ISP.If you want us to do you're job hire us I wouldn't mind to get paid.Just admit already this ISP doesn't make the cut you promise for the game "better experience" it been since after relocation of server.Get Other One.I mean yeah it sucks to find a other one but this time try to put in mind NA Player Base not the wallet & ISP who have stable connection with other ISP & centralize server it will make you re job less pain in butt I can guaranteed you that.
On good note thanks to redirect my connection to server faster less node the better.Still, somewhat package lost but less worse so ill take it for right now.:D
Same problem in France, here a tracert from my computer. Hope that can help.
It stuck always on the jump 6 for all providers.
Détermination de l’itinéraire vers 195.82.50.9 avec un maximum de 30 sauts.
1 <1 ms <1 ms <1 ms FREEBOX [192.168.0.254]
2 23 ms 24 ms 24 ms gbw68-2-88-120-120-254.fbx.proxad.net [88.120.120.254]
3 24 ms 24 ms 26 ms 213.228.17.190
4 37 ms 39 ms 39 ms ppp2-marseille.isdnet.net [194.149.165.129]
5 35 ms 34 ms 34 ms bzn-9k-7-be1001.intf.routers.proxad.net [194.149.163.170]
6 * * * Délai d’attente de la demande dépassé.
7 44 ms 43 ms 44 ms ae-1-3107.edge5.Frankfurt1.Level3.net [4.69.163.18]
8 45 ms 44 ms 43 ms 212.162.4.98
9 43 ms 48 ms 49 ms 195.82.60.29
10 44 ms 43 ms 44 ms 195.82.61.14
11 44 ms 43 ms 45 ms 195.82.50.234
12 44 ms 44 ms 43 ms 195.82.50.9
Itinéraire déterminé.
Tracing route to 204.2.229.9 over a maximum of 30 hops
1 2 ms 4 ms 4 ms 10.0.0.1
2 12 ms 13 ms 15 ms 96.120.74.229
3 9 ms 19 ms 14 ms xe-8-2-0-32767-sur01.mtlaurel.nj.panjde.comcast.
net [68.86.221.109]
4 18 ms 14 ms 15 ms be-11-ar03.eastwindsor.nj.panjde.comcast.net [68
.85.62.117]
5 25 ms 23 ms 24 ms be-101-ar03.plainfield.nj.panjde.comcast.net [96
.108.49.105]
6 23 ms 26 ms 22 ms be-33659-cr02.newyork.ny.ibone.comcast.net [68.8
6.90.21]
7 24 ms 19 ms 19 ms be-10381-pe02.111eighthave.ny.ibone.comcast.net
[68.86.86.250]
8 98 ms 93 ms 94 ms 50.242.151.70
9 104 ms 103 ms 109 ms ae-6.r08.nycmny01.us.bb.gin.ntt.net [129.250.6.5
4]
10 103 ms 48 ms 44 ms ae-3.r24.nycmny01.us.bb.gin.ntt.net [129.250.5.6
1]
11 93 ms 103 ms 95 ms ae-2.r20.sttlwa01.us.bb.gin.ntt.net [129.250.4.1
3]
12 94 ms 104 ms * ae-0.r21.sttlwa01.us.bb.gin.ntt.net [129.250.2.5
4]
13 108 ms 103 ms 105 ms ae-3.r23.snjsca04.us.bb.gin.ntt.net [129.250.3.1
24]
14 129 ms 118 ms 109 ms ae-45.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.
175]
15 108 ms 108 ms 109 ms ae-4.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.5
7]
16 107 ms 114 ms 109 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129
.250.195.46]
17 * 108 ms 123 ms 204.2.229.234
18 106 ms 119 ms 119 ms 204.2.229.9
Trace complete.
Platform: Windows PC
Connection: Wired
Internet Service Provider: Comcast
Server: Faerie
I've been having on and off lag issues since the server change last year, and using a VPN has been able to make the game at least playable whenever it gets bad, but ever since the patch last Tuesday it's been infinitely worse. CONSTANT disconnecting with 90002 errors and occasionally 90001 whenever I'm in ANY duty, which has never happened before except for the very occasional which I suspect everyone gets from time to time. Eureka, dungeon, trial and sometimes in town. I've tried everything suggested and more since I've been getting the issues and nothing has worked, as suspected. The issue is exclusive to this game, like most people. Today was especially bad, couldn't even check my retainer or teleport without having to wait 30 seconds before it registered. I absolutely love this game but since the server change, my patience has been wearing thinner and thinner, and now this is making me want to unsub. Not really sure what else I can do at least point. No reason in paying for a service I can't even properly use.