Reporting Issues Resulting from the North American Data Center Relocation

[DragonEyeMaru]

Type of Issue/Feedback: my ping went from around 30 to 120ish. its not unplayable but its hard to play properly.
Name of your Internet Service Provider (ISP): attlocal.net
State/Country: south carolina/ USA
Date/Time: after the data-center servers were moved
World Name: Leviathan
Frequency: a few times an hour
trace route:
1 4 ms 3 ms 1 ms homeportal [192.168.1.254]
2 27 ms 31 ms 34 ms 99-184-172-1.lightspeed.clmasc.sbcglobal.net [99.184.172.1]
3 21 ms 24 ms 145 ms 99.175.12.69
4 27 ms 22 ms 31 ms 99.131.77.50
5 24 ms 23 ms 26 ms 12.83.113.137
6 31 ms 31 ms 130 ms 12.122.117.121
7 61 ms 59 ms 57 ms 192.205.36.158
8 113 ms 108 ms 104 ms ae-1.r04.atlnga05.us.bb.gin.ntt.net [129.250.5.59]
9 48 ms 40 ms 44 ms ae-4.r21.atlnga05.us.bb.gin.ntt.net [129.250.5.202]
10 47 ms 46 ms 48 ms ae-6.r23.dllstx09.us.bb.gin.ntt.net [129.250.4.116]
11 88 ms 89 ms 90 ms ae-8.r23.snjsca04.us.bb.gin.ntt.net [129.250.4.154]
12 106 ms 164 ms 91 ms ae-45.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.175]
13 90 ms 89 ms 94 ms ae-1.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.31]
14 91 ms 95 ms 98 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
15 90 ms * 90 ms 204.2.229.234
16 90 ms 103 ms 90 ms 204.2.229.100

[AleskaD]

- Type of Issue/Feedback: Ping times goes up from 80 ms before migration to 150+ ms after server migration
- Name of your Internet Service Provider (ISP): JASEC - Infocomunicaciones
- State/Country: Costa Rica
- Date/Time: Since the migration to date
- World Name: Hyperion
- Frequency: All the time
- Traceroute records:

tracert 204.2.229.10

Tracing route to 204.2.229.10 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.100.1
2 1 ms 1 ms <1 ms 172.16.0.3
3 1 ms * 1 ms 172.16.0.18
4 1 ms 1 ms 1 ms 190.242.155.173
5 * 13 ms 12 ms xe-4-0-0.0-corozal-pamiami.fl.us.nama.pan-corzl-mx01.cwc.com [63.245.106.167]
6 63 ms 63 ms 63 ms xe-4-0-4.0-boca-raton.fl.us.nmi-teracore01.cwc.com [63.245.107.228]
7 52 ms * 54 ms xe-0-0-45-1.a00.miamfl02.us.bb.gin.ntt.net [129.250.198.217]
8 150 ms 150 ms 150 ms ae-7.r04.miamfl02.us.bb.gin.ntt.net [129.250.2.202]
9 57 ms 54 ms 54 ms ae-3.r20.miamfl02.us.bb.gin.ntt.net [129.250.2.110]
10 79 ms 79 ms 80 ms ae-4.r23.asbnva02.us.bb.gin.ntt.net [129.250.2.86]
11 149 ms 149 ms 150 ms ae-10.r22.snjsca04.us.bb.gin.ntt.net [129.250.6.237]
12 155 ms 154 ms 154 ms ae-19.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.27]
13 154 ms 154 ms 154 ms ae-1.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.31]
14 154 ms 154 ms 154 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
15 154 ms 154 ms 154 ms 204.2.229.234
16 154 ms 154 ms 154 ms 204.2.229.10

[j103]

Type of Issue/Feedback: Random lag spikes and disconnects, mostly in dungeons. No other software has interruptions during these times.
Name of your Internet Service Provider (ISP): Comcast
State/Country: Tennessee, US
Date/Time: Randomly since the move, latest one about 20ish minutes ago
World Name: Hyperion
Frequency: Randomly, at least once a night

Traceroute records

[Aeduken]

Type of Issue/Feedback: Ping seems higher than it should be. If the server is in Sacramento, I should be getting a lot less ping since I'm only an hour north of there.
My route shows that its bouncing down to LA before going back up to Sacramento causing me to get around 60 ping. Thats the same ping I have to the LoL server located in Chicago. The routing definitely needs a touch up.
Name of your Internet Service Provider (ISP): Comcast
State/Country: California
Date/Time: No specific times, just ping seems higher than it should be
World Name: Leviathan
Frequency: Always
Traceroute records
1 2 ms 4 ms 1 ms 10.0.0.1
2 21 ms 18 ms 19 ms 96.120.14.53
3 11 ms 9 ms 11 ms xe-11-2-1-sur02.chico.ca.ccal.comcast.net [69.139.197.205]
4 18 ms 19 ms 19 ms ae-5-ar01.fresno.ca.ccal.comcast.net [68.85.196.161]
5 32 ms 24 ms 24 ms be-33667-cr02.losangeles.ca.ibone.comcast.net [68.86.93.37]
6 27 ms 29 ms 29 ms be-11599-pe01.losangeles.ca.ibone.comcast.net [68.86.84.194]
7 28 ms 26 ms 27 ms 50.242.151.62
8 31 ms 29 ms 27 ms ae-3.r23.lsanca07.us.bb.gin.ntt.net [129.250.4.106]
9 56 ms 52 ms 54 ms ae-12.r22.snjsca04.us.bb.gin.ntt.net [129.250.4.150]
10 56 ms 53 ms 54 ms ae-19.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.27]
11 57 ms 58 ms 59 ms ae-1.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.31]
12 57 ms 69 ms 54 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
13 56 ms 59 ms 59 ms 204.2.229.234
14 52 ms 54 ms 54 ms 204.2.229.100

[SGAllaria]

Type of Issue/Feedback: Ping went down to 55~ ping. Large increase to lag spikes. Some last only half a second and some take me out of fights for 5-8 seconds. I've checked the router and have monitored my Resource Monitor for disturbances both in CPU and Network windows and nothing stood out.
Name of your Internet Service Provider (ISP): Century Link
State/Country: Phoenix, AZ
Date/Time: It seems to be a constant occurrence throughout the day. Early morning, High traffic times, and late at night all seem to have the problem.
World Name: Exodus, Primal
Frequency: Frequently. Sometimes multiple in a minute during fights. Sometimes a few minutes in between. Guaranteed to happen multiple times during a trial, raid, or dungeon. Can be seen in towns.
Traceroute records

C:\Users\Allaria>CLIP | tracert 204.2.229.10

Tracing route to 204.2.229.10 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms modem.Home [192.168.0.1]
2 20 ms 19 ms 21 ms phnx-dsl-gw66.phnx.qwest.net [67.40.227.66]
3 21 ms 20 ms 20 ms phnx-agw1.inet.qwest.net [75.160.238.9]
4 37 ms 37 ms 37 ms sjp-brdr-04.inet.qwest.net [67.14.34.42]
5 38 ms 37 ms 38 ms 63.146.27.214
6 42 ms 42 ms 42 ms ae-1.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.31]
7 42 ms 42 ms 42 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
8 42 ms 42 ms * 204.2.229.234
9 42 ms 42 ms 41 ms 204.2.229.10

Trace complete.

C:\Users\Allaria>tracert 204.2.229.10

Tracing route to 204.2.229.10 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms modem.Home [192.168.0.1]
2 20 ms 20 ms 21 ms phnx-dsl-gw66.phnx.qwest.net [67.40.227.66]
3 20 ms 19 ms 20 ms phnx-agw1.inet.qwest.net [75.160.238.9]
4 38 ms 37 ms 37 ms sjp-brdr-04.inet.qwest.net [67.14.34.42]
5 37 ms 37 ms 37 ms 63.146.27.214
6 42 ms 41 ms 43 ms ae-1.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.31]
7 43 ms 42 ms 42 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
8 42 ms * * 204.2.229.234
9 42 ms 42 ms 42 ms 204.2.229.10

[Lionheart892]

Type of issue/Feedback: My roommate and I are experiencing a lot of latency problem. Before our ping was below 100 now it above 250. In game there a very big delay on receiving info which make everything just stand there. I did everything on my end that I can do but still having issues.
Name of your internet service Provider: Xfinity
State/Country: Florida, US
Date/Time: Start what the servers was relocated
World name: Goblin
Frequency: All the time when we enter a dungeon, trail, and/or raid.


P.S. Love playing FFXIV

[PaganWitchcraft]

Type of Issue/Feedback:
My ping before was 100 ms, now 190 ms
Gathering, Mudras, etc. are very poor now........

Name of your Internet Service Provider (ISP):
Rii-Seez Net

State/Country:
Buchs / Switzerland

Date/Time:
After NA servers relocation

World Name:
Sargatanas

Frequency:
Always since relocation

[LastCookie]

It's crazy... I get less latency if I tried to play in the EU servers... and that's on the other continent!

[StaticMew]

Type of Issue/Feedback: Much slower overall. No real issue with 90ks or disconnects of any kind, just a lot slower responses. Ping jumped from 50 to 130+. Not unplayable by any stretch, but it does feel limiting in what I can do. Also, I'm getting lower ping to the EU DC than I am to NA. California is probably the single worst place that it could have gone for myself personally.
Name of your Internet Service Provider (ISP): Bell
State/Country: Newfoundland, Canada
Date/Time: Since the move. Started around 120 ping after the move, but has increased to 135 since.
World Name: Gilgamesh
Frequency: Constant
Traceroute records:

For NA:

1 <1 ms <1 ms <1 ms 192.168.2.1
2 15 ms 41 ms 9 ms loop0.17w.ba05.mtpr.nf.aliant.net [142.163.63.6]

3 7 ms 7 ms 3 ms be14-181.dr01.mtpr.nf.aliant.net [142.166.242.165]
4 6 ms 4 ms 3 ms be8.dr01.stjh.nf.aliant.net [142.166.185.89]
5 26 ms 26 ms 24 ms be5.cr01.drmo.ns.aliant.net [142.166.181.121]
6 23 ms 25 ms 25 ms et-5-1-0-50.cr02.drmo.ns.aliant.net [142.166.218.66]
7 30 ms 29 ms 33 ms ae4.cr02.stjh.nb.aliant.net [142.166.129.65]
8 43 ms 47 ms 45 ms ae0.bx01.toro.on.aliant.net [207.231.227.53]
9 45 ms 46 ms 47 ms ae52.edge1.Toronto2.Level3.net [4.31.208.9]
10 * * * Request timed out.
11 53 ms 51 ms 50 ms NTT-level3-90G.NewYork1.Level3.net [4.68.110.74]

12 49 ms 48 ms 50 ms ae-3.r24.nycmny01.us.bb.gin.ntt.net [129.250.5.61]
13 118 ms 117 ms 117 ms ae-2.r20.sttlwa01.us.bb.gin.ntt.net [129.250.4.13]
14 112 ms 114 ms 110 ms ae-0.r21.sttlwa01.us.bb.gin.ntt.net [129.250.2.54]
15 130 ms 131 ms 131 ms ae-3.r23.snjsca04.us.bb.gin.ntt.net [129.250.3.124]
16 135 ms 135 ms 136 ms ae-45.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.175]
17 136 ms 135 ms 136 ms ae-1.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.31]
18 137 ms 134 ms 135 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
19 * 135 ms 135 ms 204.2.229.234
20 132 ms 132 ms 136 ms 204.2.229.10

For EU, out of curiosity:

1 <1 ms <1 ms <1 ms 192.168.2.1
2 3 ms 3 ms 4 ms loop0.17w.ba05.mtpr.nf.aliant.net [142.163.63.6]
3 5 ms 4 ms 4 ms be14-181.dr01.mtpr.nf.aliant.net [142.166.242.165]
4 4 ms 9 ms 7 ms be8.dr01.stjh.nf.aliant.net [142.166.185.89]
5 27 ms 25 ms 25 ms be5.cr01.drmo.ns.aliant.net [142.166.181.121]
6 23 ms 25 ms 26 ms et-5-1-0-50.cr02.drmo.ns.aliant.net [142.166.218.66]
7 27 ms 30 ms 28 ms ae4.cr02.stjh.nb.aliant.net [142.166.129.65]
8 47 ms 46 ms 46 ms ae0.bx01.toro.on.aliant.net [207.231.227.53]
9 46 ms 46 ms 46 ms bx2-torontoxn_ae3 [184.150.187.56]
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 47 ms 46 ms 47 ms ae55.bar2.Toronto1.Level3.net [4.28.138.45]
15 125 ms 124 ms 126 ms ae-1-3107.edge5.Frankfurt1.Level3.net [4.69.163.18]
16 127 ms 135 ms 128 ms 212.162.4.98
17 129 ms 128 ms 127 ms 195.82.60.29
18 132 ms 131 ms 132 ms 195.82.61.14
19 132 ms 131 ms 131 ms 195.82.50.234
20 129 ms 131 ms 127 ms 195.82.50.9

[Oglaf]

Problem: Higher ping since server relocation, ping higher than EU servers.
Name of your Internet Service Provider (ISP): VIVO
Ticket or reference number from your ISP: Will not investigate since the problem is not at their end.
State/Country: SP/Brazil
Date/Time: Started May 17, 2017 after the server move.
Frequency: All the time. Latency used to be 160-180 and now is consistently 300+, I get better pings from EU servers (around 220-240).
Content: Impacts all activities.
Which in-game World were you playing on when the issue occurred?: Exodus.
Traceroute records: See below.

Trace route:
Tracing route to 204.2.229.109 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.0.1
2 <1 ms <1 ms <1 ms openrg.home [192.168.1.1]
3 * * * Request timed out.
4 4 ms 10 ms 7 ms 187-100-39-217.dsl.telesp.net.br [187.100.39.217]
5 8 ms 9 ms 9 ms 201-0-5-73.dsl.telesp.net.br [201.0.5.73]
6 17 ms 11 ms 8 ms 187-100-35-21.dsl.telesp.net.br [187.100.35.21]
7 9 ms 8 ms 9 ms 84.16.6.102
8 121 ms 127 ms 127 ms 5.53.3.143
9 159 ms 156 ms 166 ms 213.140.35.14
10 241 ms 253 ms 247 ms 213.140.33.104
11 236 ms 235 ms 235 ms 213.140.35.1
12 266 ms 270 ms 277 ms ae1-0-ntt-grtamstc1.net.telefonicaglobalsolutions.com [213.140.53.97]
13 278 ms 277 ms 271 ms ae-4.r25.amstnl02.nl.bb.gin.ntt.net [129.250.2.146]
14 248 ms 245 ms 245 ms ae-5.r23.asbnva02.us.bb.gin.ntt.net [129.250.6.162]
15 297 ms 294 ms 294 ms ae-10.r22.snjsca04.us.bb.gin.ntt.net [129.250.6.237]
16 294 ms 294 ms 294 ms ae-40.r02.snjsca04.us.bb.gin.ntt.net [129.250.3.121]
17 301 ms 294 ms 294 ms ae-2.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.33]
18 301 ms 304 ms 294 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
19 296 ms 294 ms 294 ms 204.2.229.234
20 300 ms 294 ms 294 ms 204.2.229.109

Trace complete.

I tested VPN programs like Kill Ping and it solved the problem, which makes me 100% sure that the problem is with the route AFTER it reaches USA servers.