I am compiling all my tracert results since the NA server relocation and notifying Square-Enix of the troubles the new, and very poor connection, has caused me and a portion of the general playerbase.
OVERALL REPORT:
Issues:
1: Random disconnections 90002 error.
2: Severe packet loss. This results in 5 second screen freezes. "Weaponskill/global cooldown/combos" not registering at all. Slow "crafting procs" indicators. "Global cooldown clipping" while "single and double weaving" abilities between weaponskills. Being hit by attacks due to lag. etc etc
3: Other players disconnecting in savage/extreme fights. This results in a duty failure, lost chests rewards from savage as well as party prematurely disbanding.
This renders the game completely unplayable, or frustrating enough the game is un-enjoyable. This is my final request to have the issue addressed as this as been ongoing since 4.0 and no notice has been made to repair the nodes surrounding the XIV servers in the California area.
Thank you.
REPORT: 1
5/20/2017
http://forum.square-enix.com/ffxiv/t...ter-Relocation
Type of Issue/Feedback: 9002 error. Weaponskill clipping, constant "Disconnecting"/"Red circle next to name" all other players/monsters will stop moving as i continue to press weaponskill actions but do not proc steps in combos, or enemies not receiving debuffs that I apply, such as Disembowel, Wildfire, etc.
Name of your Internet Service Provider: Comcast
State/Country: TN/USA
Date/Time: Just about all day every day since about 2 days before the server relocation, and more consistently after the server relocation. I dont know why this issue only started just before the relocation, and then also now after the relocation. It makes no sense.
World Name: Malboro
Frequency: All day every day
Traceroute records:
"Tracing Route to 204.2.229.101 over a maximum of 30 hops
1.....1 ms.......1 ms.......<1 ms (Omitted)
2.....10 ms.....10 ms......10 ms (omitted)
3.....12 ms.....11 ms.......9 ms Te5-4-ur01.tn.malt.comcast.net [Omitted]
4.....18 ms......9 ms.......11 ms (Omitted)
5.....13 ms.....12 ms......11 ms te-3-1-ur01.tn.malt.comcast.net [Omitted]
6.....24 ms......26 ms.....21 ms be-22258-cr02.dallas.tx.ibone.comcast.net [68.86.93.93]
7.....21 ms......20 ms.....29 ms be-12495-pe03.1950stemmons.tx.ibone.comcast.net [68.86.85.194]
8.....22 ms......27 ms.....22 ms ae-19.a01.dllstx09.us.bb.gin.ntt.net [129.250.66.29]
9.....69 ms......68 ms.....68 ms ae-3.r10.dllstx09.us.bb.gin.ntt.net [129.250.3.245]
10....21 ms.....21 ms.....21 ms ae-0.r23.dllstx09.us.bb.gin.ntt.net [129.250.5.5]
11....60 ms.....59 ms.....59 ms ae-8.r23.snjsca04.us.bb.gin.ntt.net [129.250.4.154]
12....69 ms.....69 ms.....70 ms ae-45.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.175]
13....65 ms.....63 ms.....65 ms ae-1.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.31]
14....76 ms.....76 ms.....77 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
15....67 ms..... *.......... * ....204.2.229.234
16....72 ms.....62 ms.....65 ms 204.2.229.101
Trace complete.
REPORT: 2
10/28/2017
http://forum.square-enix.com/ffxiv/t...Game-uplayable
1.......<1ms.........<1ms............<1ms.........Router
2.......9ms..............9ms...............9ms.......Other
3........9ms..............9ms..............9ms........Local
4.......11ms.............11ms..........11ms.......Local
5........24ms.............35ms...........24ms....GA-comcast
6........23ms.............29ms..........22ms......marietta.ga...comcast.net [68.86.88.178}
7........33ms............34ms..........29ms........50.242.151.58
8......24ms..............23ms..........25ms........Atlnha05 [129.250.5.59]
9.......22ms..............22ms.........27ms........atlnga05 [129.250.5.202]
10.....45ms..............44ms.........45ms........dllstx09 [129.250.4.116]
11.....90ms..............82ms..........83ms.......snjsca04 [129.250.4.154]
12.....85ms..............86ms..........88ms.......snjsca04 [129.250.6.119]
13....86ms..............87ms..........86ms........scrmca02 [129.250.7.53]
14....88ms..............87ms..........87ms.......scrmca02 [129.250.195.46]
15....87ms.............86ms...........86ms........FFXIV 204.2.229.254
16....93ms.............85ms............88ms......Malboro 204.2.229.101
REPORT: 3
11/8/2017
1 2 ms <1 ms <1 ms
2 10 ms 8 ms 9 ms
3 8 ms 9 ms 10 ms
4 11 ms 12 ms 12 ms
5 24 ms 25 ms 24 ms
6 25 ms 23 ms 22 ms hu-0-11-0-5-pe03.56marietta.ga.ibone.comcast.net [68.86.88.178]
7 25 ms 32 ms 26 ms 50.242.151.58
8 25 ms 23 ms 24 ms ae-1.r04.atlnga05.us.bb.gin.ntt.net [129.250.5.59]
9 29 ms 26 ms 23 ms ae-4.r21.atlnga05.us.bb.gin.ntt.net [129.250.5.202]
10 45 ms 44 ms 44 ms ae-6.r23.dllstx09.us.bb.gin.ntt.net [129.250.4.116]
11 89 ms 84 ms 83 ms ae-8.r23.snjsca04.us.bb.gin.ntt.net [129.250.4.154]
12 85 ms 87 ms 86 ms ae-41.r02.snjsca04.us.bb.gin.ntt.net [129.250.6.119]
13 87 ms 85 ms 87 ms ae-2.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.33]
14 86 ms 87 ms 86 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
15 87 ms 86 ms 86 ms 204.2.229.234
16 87 ms 87 ms 86 ms 204.2.229.101
Trace complete.
These reports are of the "better" times of day. Ping can reach up to 220ms+ as well as packet loss can reach upwards to 30% packet loss or higher.
EDIT: REPORT: 4
11/8/2017 11am CST
1 <1 ms <1 ms <1 ms
2 11 ms 9 ms 11 ms
3 14 ms 10 ms 10 ms
4 13 ms 19 ms 13 ms
5 27 ms 25 ms 27 ms be-22258-cr02.56marietta.ga.ibone.comcast.net
6 23 ms 23 ms 27 ms hu-0-11-0-5-pe03.56marietta.ga.ibone.comcast.net [68.86.88.178]
7 23 ms 22 ms 24 ms 50.242.151.58
8 28 ms 30 ms 25 ms ae-1.r04.atlnga05.us.bb.gin.ntt.net [129.250.5.59]
9 33 ms 28 ms 25 ms ae-4.r21.atlnga05.us.bb.gin.ntt.net [129.250.5.202]
10 47 ms 48 ms 50 ms ae-6.r23.dllstx09.us.bb.gin.ntt.net [129.250.4.116]
11 ....* .... *.....95 ms ae-8.r23.snjsca04.us.bb.gin.ntt.net [129.250.4.154]
12 90 ms 91 ms 89 ms ae-41.r02.snjsca04.us.bb.gin.ntt.net [129.250.6.119]
13 94 ms 87 ms 89 ms ae-2.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.33]
14 91 ms 104 ms 93 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
15 86 ms 87 ms 86 ms 204.2.229.234
16 86 ms 88 ms 89 ms 204.2.229.101
Trace complete.
Note:
I have already contacted Comcast on numerous occasion, had 4 separate technician visits resulting in cable adjustment, and node replacement, and still the errors persist. Square-Enix or Comcast need to locate the issue, and address it, instead of ignore it if they do not wish to lose customers, as it is not in the hands of the customers to find and address issues themselves.
I will be submitting a ticket via the Square-Enix support center, as well as contacting Comcast, my Internet Service Provider one final time.
-
11-09-2017, 12:41 AMDaniolaut[Unplayable] Severely poor connection since 4.0 (server relocation)
-
11-09-2017, 01:08 AMZalaty
I should have waited a lot longer before renewing my sub. Play on ps4 can't really access much data from there only get the 90k or lobby error message like very 10-20 min. I spend more time between lags and reconnecting than actually playing. SE said it was the higher IP problem, Comcast said it was L3 problem and L3 said it was an error on configuration and was fixed on monday....
-
11-09-2017, 01:19 AMDaniolautYeah I entered savage yesterday (tuesday, after the DDoS attack) for weekly 2 chest clear for v1s and right when the party jail let us go to start the duty, 3 people instantly started to disconnect. I disbanded the party, because 1 player disconnecting while completing the duty, results in 1 or more lost chests. This same thing happened last tuesday where someone disconnected and we lost out on one chest because of it. So clearly there is an issue, and no one is willing to fix it. So figure time to cut ties, and maybe then someone will step up and address the issue. Cant exactly play XIV without a solid connection. I dont play to carry disconnected players, and i'm sure people dont play to carry me when i disconnect, and also play only for half the rewards.Quote:
Originally Posted by Zalaty
-
11-09-2017, 01:27 AMsilverlunarfox
Square cannot control the internet connections going into the servers the ISPs do. I know you like ignoring the ISP issues but yelling at Square isn't going to do anything. That being said you have a higher ping than I do, and I route through Chicago with no problems whatsoever. I go usually from chi to scrm.
-
11-09-2017, 01:38 AMDaniolautYou are not a part of the Square-Enix technical support, and this is not general discussion. If you are not experiencing issues with connections to the FFXIV servers, please delete your comment and resist posting on this thread. This is a thread for people to post issues regarding their connections to the XIV servers, again, this is not general discussion.Quote:
Originally Posted by silverlunarfox
People are trying to get their connection issue resolved, and informing all parties involved is the best way to do that. -
11-09-2017, 01:50 AMsilverlunarfoxYou're still posting it in a forum where people can comment on it. So, I will continue to point out maybe its a hop that you do and I don't. So my statement is just as important. Maybe your dallas and snj hops are the issue and whatever ISP controls those... Hrrmmmm.... >.>Quote:
Originally Posted by Daniolaut
Like the information below:
SE said it was a higher IP problem. I.E. there isn't anything they can do about it. And that's believable considering theres only so much they can do.Quote:
Originally Posted by Zalaty
-
11-09-2017, 01:56 AMClaviusnexThat higher ISP problem is the backbone provider who happens to be NTT in this case. I'm not sure who is doing the game server hosting but the backbone provider selection is up to them and likely SE so there is a lot they can do about it. One is to find better providers for server hosting and backbone access.Quote:
Originally Posted by silverlunarfox
-
11-09-2017, 01:58 AMsilverlunarfoxIf I don't recall Square had done prior work with NTT which is probably what led to their server selection. No, it's not good but....it is SquareQuote:
Originally Posted by Claviusnex
Also this is the main thread for "server issues" and /or other issues related to connection
http://forum.square-enix.com/ffxiv/t...ter-Relocation -
11-09-2017, 03:18 AMZarkovitch
Im getting tired of PR silent treatment from square they should notice by now how new server are pretty bad rn i mean cmon if you see good versus bad & bad outweight it by alot.That means those servers are bad.
Here good & bad imo
Good:west coast player have better response on game(ping),more space to add servers,more communications between SE & HIS PROVIDER.
Bad:east coast player average or bad respond to the game(ping),servers infrastructure is on worse place than montreal,new server is vulnerable to DDOS attack,New Provider is same level as lvl3 but abit worse & better (pending on what),SOME NTT NODES ARE GARBAGE.
solutions to fix the bad:Get new provider SE & put server more on centralize spot or GET US EAST COAST SERVERS.
IDC IF IT Q.Q MONEY COST DO YOU WANT FIASCO 1.0 AGAIN? CUZ RIGHT NOW YOU GUYS STARTING TO HAVE A BAD REPUTATION INSIDE THE GAME & OUTSIDE.NEXT EXPANSION WILL NOT SELL VERY WELL IF IT CONTINUE RECESSION WILL SAY HI.D'ONT FORGET WHO SAVE COMPANY BACK IN 2013-14 IT WAS 14 SO YOU SHOULD MAYBE START RESPECT CLIENT & THINK WHATS IS GOOD FOR THEM. -
11-09-2017, 06:11 AMRiko_Futatabi
Yep the servers/location, it's all terrible. I've actually become a regular on this part of the forums due to the awful connection I've had to game for the past 2 months, unfortunately. Sometimes I don't like to post on other peoples threads here because I'm just going to say the same thing, but whatever, I'm persistent.
You know there's a Problem with something SE is doing when your connection goes to **** after a patch. This problem started for me since the 4.06a patch and has not been resolved since. I even made a thread here and it got moved to "resolved" but it was never resolved... -
11-09-2017, 07:06 AMhynaku
Never had one problem tell they brought out 4.0. Then hear ones getting none stop 90002 errors after it came out. This tells me server company they went with can't handle 4.0. So think they need to move there servers to a better place that can handle the load and not cause ones to disconnect all the time. Never once got 90002 error in old location never got 90002 error in new location till 4.0 came out. Been using same internet for almost 2 years now.
-
11-09-2017, 07:16 AMKurandoI think we need to drop this ridiculous notion that having the servers West Coast is suddenly the big problem here. As an EU player that plays on the NA data centre, I have never had as such serious issues as all these East Coast people keep making out and i am thousands of miles away and have to go through more routes to connect to the servers. The only time things ever got so bad that I could barely play was during SB early access, and now during the past few days. However the recent issues are because of problems with the ISPs (more than one) that are required to connect to the NA centres, it wouldn't make any difference where they are located.Quote:
Originally Posted by Zarkovitch
Players really need to quit jumping at SE for every single issue as the respect works both ways. I've never know a company like SE apologize so much and so publicly for the problems that are endured, you'd never get this kind of relations with WoW. -
11-09-2017, 08:58 AMRiko_FutatabiMay I ask what ISP you are using currently? I'm EU also and play on NA server since 2.0. Issues only started happening a couple months back for me and have persisted.Quote:
Originally Posted by Kurando
-
11-09-2017, 09:06 AMRiko_Futatabi
Also I might as well post this again as some sort of update of my terrible route to server. Also proof that east coast has some very bad routers with awful packet loss. And yeah, SEs lobby server has issues too.
This was monitored at 00:05 GMT Nov 9th.
Code:|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| SkyRouter.Home - 0 | 125 | 125 | 0 | 0 | 2 | 0 |
| 97e7fe6a.skybroadband.com - 0 | 125 | 125 | 5 | 5 | 10 | 6 |
| be365.pr2.hobir.isp.sky.com - 0 | 125 | 125 | 16 | 17 | 20 | 18 |
| ae-3.r02.londen03.uk.bb.gin.ntt.net - 0 | 125 | 125 | 16 | 17 | 21 | 17 |
| ae-3.r24.londen12.uk.bb.gin.ntt.net - 0 | 125 | 125 | 16 | 16 | 25 | 17 |
| ae-5.r24.nycmny01.us.bb.gin.ntt.net - 34 | 54 | 36 | 82 | 82 | 87 | 83 |
| ae-2.r20.sttlwa01.us.bb.gin.ntt.net - 29 | 60 | 43 | 0 | 158 | 184 | 156 |
| ae-0.r21.sttlwa01.us.bb.gin.ntt.net - 44 | 46 | 26 | 0 | 154 | 161 | 154 |
| ae-3.r23.snjsca04.us.bb.gin.ntt.net - 0 | 125 | 125 | 170 | 171 | 180 | 171 |
| ae-45.r01.snjsca04.us.bb.gin.ntt.net - 0 | 125 | 125 | 171 | 171 | 174 | 171 |
| ae-1.r00.scrmca02.us.bb.gin.ntt.net - 0 | 125 | 125 | 169 | 169 | 172 | 170 |
|xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net - 0 | 125 | 125 | 169 | 169 | 172 | 169 |
| 204.2.229.234 - 18 | 76 | 63 | 174 | 175 | 179 | 179 |
| 204.2.229.10 - 0 | 125 | 125 | 172 | 173 | 175 | 173 |
|________________________________________________|______|______|______|______|______|______|
-
11-09-2017, 09:17 AMhynaku
204.2.229.234 only place see package loss when do a tracer route. Few months ago never got any package loss from there. But notice online when Google it there is a lot of complaints about package loss from that IP address. Mine Went 34ms * 34ms at that IP address.
-
11-09-2017, 09:33 AMShizomaru
Oh god I thought I was the only one experiencing this. Ever since the update after the Halloween event I started lagging and disconnecting so much. It happened to me a few times during dungeons or guildhests and I kept apologizing and feeling bad for screwing up the duty.
-
11-09-2017, 02:54 PMLaraul
I took this screenshot of my iPad monitoring the server latency when a lag spike hit...
https://i.imgur.com/d9QlGYh.png
All four of us in the dungeon experienced the same spike at the same time. -
11-11-2017, 03:23 AMK3KW4RCHILD
I’m just glad more players are actually posting about this problem. Many aren’t aware that it is a chronic problem and also not exclusive to ddos attacks. Unfortunately, a large number of players have been reporting these issues for months. Now they either gave up and lurk these threads, or quit playing altogether. I refuse to do anymore trace route tests, reset my network and re enter all the port forwarding settings, I want to kill the next person who tells me to try google dns, my ISP knows me by first name basis and they recognize the very sound of my voice, they no longer address my problem, instead they say my issue is well documented and no longer warrants house visits by technicians, such is the extent of the connection issues I experience ONLY when playing this game.
-
11-11-2017, 03:18 PMRynn21
Since 4.0, it's felt like server stability has taken a dive. I'm on the West coast and it's been decent, but not better.
Now during this week's ddosing, I was kicked several times every day since it started about four days ago. I wish there was something to stop those annoying ddosers, but I guess for now just have to play something else. -
11-12-2017, 02:13 AMPhalk
I'm having constant disconnects too since the server relocation. Sometimes I can't log back in for 1 or 2 hours (disconnection after the loading screen, error 90002).
Playing from Brazil. -
11-12-2017, 02:40 AMxavird
I have the same problem since the last 4 or 5 days, rubberbanding and dc constantly, I'm playing from Argentina, is really unplayable from dying in final heads in potd, to waiting for hours because in the middle of the waiting to enter to play a dungeons roulette disconnected and I have to start again the wait.
-
11-12-2017, 08:02 AMHiruki
Hey, I'm playing from Argentina too. And... yes, same problem as you. :(