Reporting Issues Resulting from the North American Data Center Relocation

**CielRei** · 06-12-2017 04:31 PM

Type of Issue/Feedback: Latency issue. ping went from 30 to 130 Average. Having lag spikes very often. I have to spam hitting oGCD for it to register. Retainer doesn't appear for good 5+ seconds many times. When I get off mount, on the screen, I am still on the mount for 3+ seconds.
Name of your Internet Service Provider (ISP): Spectrum (formally Time Warner Cable)
State/Country: NJ/USA
Date/Time: (When did the issue start happening, at what specific times does this issue arise, if any.): Day after datacenter migration.
World Name: Leviathan
Frequency: (How often does the issue occur?) ALL TIME.

1 14 ms 8 ms 8 ms 142.254.171.29
2 6 ms 9 ms 13 ms be62.plpknj4602h.nyc.rr.com [68.173.202.230]
3 15 ms 14 ms 11 ms agg132.nyquny9101r.nyc.rr.com [68.173.198.82]
4 22 ms 23 ms 14 ms bu-ether25.nycmny837aw-bcr00.tbone.rr.com [107.14.19.22]
5 9 ms 8 ms 14 ms 205.197.232.13
6 11 ms 13 ms 13 ms 207.88.14.150.ptr.us.xo.net [207.88.14.150]
7 11 ms 14 ms 13 ms 216.156.16.131.ptr.us.xo.net [216.156.16.131]
8 13 ms 17 ms 11 ms 206.111.13.193.ptr.us.xo.net [206.111.13.193]
9 11 ms 11 ms 11 ms ae-2.r24.nycmny01.us.bb.gin.ntt.net [129.250.3.180]
10 128 ms 110 ms 119 ms ae-2.r20.sttlwa01.us.bb.gin.ntt.net [129.250.4.13]
11 122 ms 120 ms 125 ms ae-0.r21.sttlwa01.us.bb.gin.ntt.net [129.250.2.54]
12 119 ms 110 ms 119 ms ae-3.r23.snjsca04.us.bb.gin.ntt.net [129.250.3.124]
13 120 ms 119 ms 118 ms ae-41.r02.snjsca04.us.bb.gin.ntt.net [129.250.6.119]
14 128 ms 124 ms 123 ms ae-2.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.33]
15 128 ms 122 ms 122 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
16 128 ms 125 ms 124 ms 204.2.229.234
17 129 ms 129 ms 129 ms 204.2.229.9

-SE mentioned 200-220ms is playable. But it feels like either my computer is broken, or my internet is massively slower. Everything registers extremely slower, everything in the game feels delayed.

I am not saying I should have 30ms ping back. I was actually happy about server move because LIKE SE mentioned, it will stablize latency issue for all NA players. (It is NA Datacenter)
But instead of fixing the issue, it just swapped from coast to coast.

I thought "Slight Increase" of ping meant, going from 30 to 60-70. which is double or more, and I was OK with that since friends from West Coast I raid with won't have ping issue. I thought that was the reason for server move. But how are you expecting us to accept enjoy your decision?

"200-220ms is playable."
Well, PS3 is playble too. But if you 'force' PS4 players and PC (with decent build) players to play on PS3 from now on, just because of SE's decision (just an example of how I feel. I know PS3 service is done in SB) will it be enjoyable?
This is dramatic as what I stated above.

**Pandamonious** · 06-13-2017 02:07 AM

Some communication of any kind would be great from se... Unless this thread is nothing more than a "yea we will take a look at it" deal.

**ShivaKannou** · 06-13-2017 03:36 AM

Type of Issue/Feedback: High latency (~300ms), used to be ~150ms.
Name of your Internet Service Provider (ISP): Vivo - Fiber connection 100MB
State/Country: São Paulo/Brazil
Date/Time: Since the NA Data Center Relocation
World Name: Behemoth
Frequency: Always
Ping records:

The ping on my resmon:

204.2.229.105 latency 305

The pings from ARRStatus:

Chaos 195.82.50.9 latency 234
Elemental 124.150.157.158 latency 310
Mana 124.150.157.156 latency 319
Gaia 124.150.157.157 latency 327
Primal 199.91.189.93 request timed out
Aether 199.91.189.74 request timed out

The ping from FFXIV Guild:

NA server 184.107.107.176 request timed out

**LlenCoram** · 06-14-2017 06:48 AM

Type of Issue/Feedback: Incredible lag, rubber banding of up to 10 second increments, Error 900006.
Name of your Internet Service Provider (ISP): Teksavvy
State/Country: Canada
Date/Time: June 13th, 2017, at log-in around 4:30pm.
World Name: Sargatanas
Frequency: It literally only just started today. My latency went up after the server move, but in general my connection was fine. Today I noticed such insane lag that the game is completely unplayable in a very literal sense. With a constant 25 to 50% packet loss rate and rubberbanding of upwards of 10 seconds, I can't actually do anything in game anymore.
Traceroute records

Code:

Tracing route to 204.2.229.87 over a maximum of 30 hops

  1     1 ms     4 ms     5 ms  192.168.0.1
  2    27 ms    25 ms    26 ms  67.231.220.82
  3    25 ms    27 ms    21 ms  104-195-128-122.cpe.teksavvy.com [104.195.128.122]
  4    24 ms    21 ms    28 ms  104-195-128-121.cpe.teksavvy.com [104.195.128.121]
  5    25 ms    28 ms    28 ms  ae0-2160-bdr01-tor.teksavvy.com [192.171.59.69]
  6    24 ms    29 ms    28 ms  ae8-0-bdr01-tor2.teksavvy.com [206.248.155.9]
  7    24 ms    28 ms    24 ms  ae54.bar2.Toronto1.Level3.net [4.28.138.21]
  8     *        *        *     Request timed out.
  9    52 ms    49 ms    58 ms  NTT-level3-90G.NewYork1.Level3.net [4.68.110.74]
 10    60 ms    54 ms    59 ms  ae-3.r24.nycmny01.us.bb.gin.ntt.net [129.250.5.61]
 11   103 ms    99 ms    97 ms  ae-2.r20.sttlwa01.us.bb.gin.ntt.net [129.250.4.13]
 12   113 ms     *      103 ms  ae-0.r21.sttlwa01.us.bb.gin.ntt.net [129.250.2.54]
 13   219 ms   116 ms   110 ms  ae-3.r23.snjsca04.us.bb.gin.ntt.net [129.250.3.124]
 14   117 ms   108 ms   128 ms  ae-45.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.175]
 15   113 ms   118 ms     *     ae-1.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.31]
 16   112 ms   119 ms   118 ms  xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
 17     *      113 ms   145 ms  204.2.229.234
 18   113 ms     *      114 ms  204.2.229.87

Trace complete.

I ran 5 tracerts and the drop happens at hop 8 every single time. Basically as soon as I leave Canada.

**Brazin_Alexander** · 06-14-2017 01:58 PM

This is ridiculous. I can't barely play and almost regret wasting money on the forgoing expansion and content you guys have to offer. I just got done playing a different game and was 100% fine and not lagging a tall. I come on FFXIV and can barely play for a minute without lagging.

1. Lag. Lag. Lag. Lag.
2. Comcast
3. Florida, US
3. Every freaking day all day.
4. Behemoth
5. All the time

**Zerahn** · 06-14-2017 07:18 PM

Type of Issue/Feedback: Ever since the server move, my Swiftcast timing has been garbage. Even after waiting for the animation delay, my raises often end up slowcast even though I can see the Swiftcast buff counting down on the bar. It's an issue with both White Mage and Astrologian, with raises, Holy, Stoneskin 2, and Flare on Black Mage. I had the same issues back in 2.0, they stopped while I was taking one of my 6 month breaks so I don't know why.
Name of your Internet Service Provider (ISP): Aliant (Fiber-Op)
State/Country: New Brunswick, Canada
Date/Time: June 14th, 2017, around 1am Atlantic time
World Name: Hyperion
Frequency: Sometimes I don't even notice because another healer will get in a raise while mine is slowcasting. I hear the raise ding go off and think it worked, and then I end up swiftcasting a Cure 2 or something. I also don't play as much lately, but it happens at least once a day, and it's not limited to particular times. I'm on whenever.

Code:

Tracing route to 184.107.107.176 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  192.168.2.1
  2     2 ms     2 ms     2 ms  loop0.45w.ba08.mctn.nb.aliant.net [142.166.182.13]
  3     3 ms     2 ms     2 ms  ae15-182.cr02.mctn.nb.aliant.net [142.176.208.13]
  4    15 ms    15 ms    15 ms  ae9.bx01.mtrl.pq.aliant.net [207.231.227.126]
  5    20 ms    21 ms    21 ms  ae8.bx01.toro.on.aliant.net [207.231.227.121]
  6    33 ms    30 ms    30 ms  bx2-torontoxn_ae3 [184.150.187.56]
  7    38 ms    31 ms    31 ms  tcore4-torontoxn_hundredgige0-6-0-0.net.bell.ca [64.230.97.146]
  8    30 ms    27 ms    27 ms  tcore4-toronto63_hundredgige1-1-0-0.net.bell.ca [64.230.50.14]
  9    34 ms    31 ms    31 ms  tcore4-montreal02_1-2-0-0.net.bell.ca [64.230.79.37]
 10    31 ms    30 ms    31 ms  bx7-montreal02_ae5.net.bell.ca [64.230.91.65]
 11    31 ms    29 ms    31 ms  ix-xe-8-0-0-0.tcore1.W6C-Montreal.as6453.net [66.198.96.37]
 12    31 ms    30 ms    30 ms  66.198.96.58
 13    46 ms    28 ms    27 ms  te7-3.dr9.mtl.iweb.com [67.205.127.214]
 14    31 ms    31 ms    30 ms  174.142.115.218
 15    31 ms    30 ms    30 ms  184.107.107.176

Trace complete.

**Takamorisan** · 06-17-2017 10:27 AM

So the expansion released and not a single word from the team.

**Roda** · 06-19-2017 10:10 AM

Originally Posted by Roda

Type of Issue/Feedback: Periodic lag stutters, jarring and immersion annihilating rubberbanding and iceskating of other players, server eating casts and inputs are behaving sluggish.
Name of your Internet Service Provider (ISP): Comcast Xfinity
State/Country:Virginia
Date/Time: Since server migration
World Name: Balmung
Frequency: Constantly
Traceroute records:

Tracing route to 204.2.229.84 over a maximum of 30 hops

1 1 ms 31 ms 1 ms 10.0.0.1
2 12 ms 10 ms 14 ms 96.120.18.125
3 33 ms 14 ms 13 ms te-1-4-sr01.powhatan.va.richmond.comcast.net [68
.86.127.57]
4 12 ms 11 ms 12 ms ge-3-24-ur01.salem.va.richmond.comcast.net [68.8
6.125.185]
5 19 ms 17 ms 21 ms ae-27-0-ar02.charlvilleco.va.richmond.comcast.ne
t [69.139.165.109]
6 22 ms 28 ms 21 ms be-21508-cr02.ashburn.va.ibone.comcast.net [68.8
6.91.53]
7 29 ms 31 ms 28 ms hu-0-10-0-3-pe07.ashburn.va.ibone.comcast.net [6
8.86.83.78]
8 107 ms 117 ms 122 ms ae-16.a02.asbnva02.us.bb.gin.ntt.net [129.250.66
.49]
9 118 ms 117 ms 114 ms ae-69.r06.asbnva02.us.bb.gin.ntt.net [129.250.5.
193]
10 130 ms 252 ms 126 ms ae-2.r23.asbnva02.us.bb.gin.ntt.net [129.250.2.1
32]
11 114 ms 116 ms 113 ms ae-10.r22.snjsca04.us.bb.gin.ntt.net [129.250.6.
237]
12 119 ms 113 ms 120 ms ae-40.r02.snjsca04.us.bb.gin.ntt.net [129.250.3.
121]
13 144 ms 148 ms 121 ms ae-2.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.3
3]
14 118 ms 118 ms 118 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129
.250.195.46]
15 * 121 ms 114 ms 204.2.229.234
16 127 ms 121 ms 119 ms 204.2.229.84

Trace complete.

Originally Posted by Roda

Gonna add that i'm getting frequent 90ks on zone transitions and very frequently in instances.

Still getting random 90ks not related to the server stress.

Seem to be dropping at 204.2.229.234

Tracing route to 204.2.229.9 over a maximum of 30 hops

1 1 ms 1 ms 1 ms 10.0.0.1
2 15 ms 9 ms 11 ms 96.120.18.125
3 11 ms 11 ms 14 ms te-1-4-sr01.powhatan.va.richmond.comcast.net [68
.86.127.57]
4 13 ms 13 ms 20 ms ge-3-24-ur01.salem.va.richmond.comcast.net [68.8
6.125.185]
5 20 ms 19 ms 19 ms ae-27-0-ar02.charlvilleco.va.richmond.comcast.ne
t [69.139.165.109]
6 24 ms 23 ms 35 ms be-21508-cr02.ashburn.va.ibone.comcast.net [68.8
6.91.53]
7 90 ms 24 ms 22 ms hu-0-10-0-7-pe07.ashburn.va.ibone.comcast.net [6
8.86.86.54]
8 56 ms 59 ms 59 ms ae-16.a02.asbnva02.us.bb.gin.ntt.net [129.250.66
.49]
9 97 ms 96 ms 89 ms ae-69.r06.asbnva02.us.bb.gin.ntt.net [129.250.5.
193]
10 28 ms 37 ms 29 ms ae-2.r23.asbnva02.us.bb.gin.ntt.net [129.250.2.1
32]
11 88 ms 89 ms 89 ms ae-10.r22.snjsca04.us.bb.gin.ntt.net [129.250.6.
237]
12 163 ms 95 ms 94 ms ae-19.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.
27]
13 93 ms 99 ms 99 ms ae-1.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.3
1]
14 93 ms 94 ms 94 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129
.250.195.46]
15 93 ms 94 ms * 204.2.229.234
16 92 ms 92 ms 89 ms 204.2.229.9

Trace complete.

(a couple hours pass)

Tracing route to 204.2.229.9 over a maximum of 30 hops

1 13 ms 1 ms <1 ms 10.0.0.1
2 10 ms 14 ms 14 ms 96.120.18.125
3 14 ms 9 ms 9 ms te-1-4-sr01.powhatan.va.richmond.comcast.net [68
.86.127.57]
4 11 ms 17 ms 13 ms ge-3-24-ur01.salem.va.richmond.comcast.net [68.8
6.125.185]
5 19 ms 19 ms 19 ms ae-27-0-ar02.charlvilleco.va.richmond.comcast.ne
t [69.139.165.109]
6 22 ms 26 ms 24 ms be-21508-cr02.ashburn.va.ibone.comcast.net [68.8
6.91.53]
7 22 ms 26 ms 24 ms hu-0-10-0-7-pe07.ashburn.va.ibone.comcast.net [6
8.86.86.54]
8 91 ms 96 ms 89 ms ae-16.a02.asbnva02.us.bb.gin.ntt.net [129.250.66
.49]
9 92 ms 91 ms 174 ms ae-69.r06.asbnva02.us.bb.gin.ntt.net [129.250.5.
193]
10 107 ms 101 ms 97 ms ae-2.r23.asbnva02.us.bb.gin.ntt.net [129.250.2.1
32]
11 89 ms 87 ms 97 ms ae-10.r22.snjsca04.us.bb.gin.ntt.net [129.250.6.
237]
12 96 ms 92 ms 91 ms ae-19.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.
27]
13 90 ms 94 ms 93 ms ae-1.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.3
1]
14 93 ms 94 ms 94 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129
.250.195.46]
15 * 94 ms * 204.2.229.234
16 95 ms 94 ms 89 ms 204.2.229.9

Trace complete.

(two days pass)

Tracing route to 204.2.229.9 over a maximum of 30 hops

1 1 ms 11 ms 1 ms 10.0.0.1
2 12 ms 9 ms 9 ms 96.120.18.125
3 14 ms 9 ms 11 ms te-1-4-sr01.powhatan.va.richmond.comcast.net [68
.86.127.57]
4 18 ms 16 ms 14 ms ge-3-24-ur01.salem.va.richmond.comcast.net [68.8
6.125.185]
5 20 ms 19 ms 20 ms ae-27-0-ar02.charlvilleco.va.richmond.comcast.ne
t [69.139.165.109]
6 23 ms 29 ms 24 ms be-21508-cr02.ashburn.va.ibone.comcast.net [68.8
6.91.53]
7 23 ms 21 ms 24 ms hu-0-10-0-7-pe07.ashburn.va.ibone.comcast.net [6
8.86.86.54]
8 59 ms 64 ms 64 ms ae-16.a02.asbnva02.us.bb.gin.ntt.net [129.250.66
.49]
9 99 ms 99 ms 89 ms ae-69.r06.asbnva02.us.bb.gin.ntt.net [129.250.5.
193]
10 49 ms 49 ms 69 ms ae-2.r23.asbnva02.us.bb.gin.ntt.net [129.250.2.1
32]
11 89 ms 88 ms 101 ms ae-10.r22.snjsca04.us.bb.gin.ntt.net [129.250.6.
237]
12 101 ms 99 ms 92 ms ae-19.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.
27]
13 92 ms 92 ms 92 ms ae-1.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.3
1]
14 93 ms 97 ms 93 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129
.250.195.46]
15 93 ms * * 204.2.229.234
16 182 ms 95 ms 91 ms 204.2.229.9

Trace complete.

**Jozu** · 06-20-2017 10:02 AM

Still nothing,no response.The expansion is getting all the attention and to be honest I don't think this issue is going to be fixed anytime soon.

**Sylentmana** · 06-21-2017 01:06 PM

Originally Posted by Jozu

Still nothing,no response.The expansion is getting all the attention and to be honest I don't think this issue is going to be fixed anytime soon.

They've had weeks now to address the issue and they aren't doing anything. They don't care. They're too busy serving their corporate overlords so they can count their fat stacks of cash in comfort.

Thread: Reporting Issues Resulting from the North American Data Center Relocation

Thread Tools

Search Thread

Display