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.