Reporting Issues Resulting from the North American Data Center Relocation

[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

[BernAlmasy]

tomorrow well hit 2 weeks of it. lots of complaining, and no dev answer so far. we all want to know if SE is taking any action regarding this. all of us who pre ordered stormblood before server location changed and had a good ping, we deserve a decent answer. its not a free game, were paying for this. Please, take care of ur costummers, or they will end up somewhere else, playing some other game. Be honest with us and let us know if any maintenance will happen at any time.

[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.

[Kitsu]

Type of Issue/Feedback: Sporadic High Packet Loss only at IP 204.2.229.234
Name of your Internet Service Provider (ISP): Ting
State/Country: Virginia, USA
Date/Time: Since NA Server Move
World Name: Balmung
Frequency: Every weekday between 3pm EST and 3am EST - several times a minute - and all day on weekends

I haved used pingplotter at a trace interval of 5 seconds to monitor my connection to 204.2.229.86 when connected to Balmung over the last week. I have found that my connection is packet loss free with pretty good ms until my connection from Virginia goes from 129.250.195.46 to 204.2.229.234. At 204.2.229.234, I lose an average of 10-20% of my packets. In-game, this causes the following situation: I queue up the wrong 3 second spell, so I immediately move to interrupt it, except it suceeds if my packets drop. This is a very huge problem for avoiding AoE. I normally can dodge fine, except when my packets drop and I can't.

I've tested this in-game as well - I typically can interrupt a spell at .3 second. However, if I am experiencing packet loss to 204.2.229.234, I will not be able to interrupt the spell at even .5 second, and sometimes not even between 1-3 seconds.

Edit: Found a post from 2014 that references high packet loss within the NTT network while playing League of Legends. Could this be related to our issues since both problem hop and the one before it belong to NTT? NTT's site says we should not be experiencing more than 0.1% packet loss over a month while using their network. Using a VPN that changes the last hop before 204.2.229.86 to something outside of NTT's network seems to resolve the packet drops.
https://www.reddit.com/r/leagueofleg...nning_through/

Edit2: Today at Tuesday 11 AM EST, I have no packet loss. There's definitely something going on towards your guys' end once my connection hits the FFXIV servers during weekends/"prime time" which is causing up to a third of my connection to be entirely dropped for up to 3 seconds. I spent several hours looking for a solution on my end over the holiday weekend, and the only thing that worked for me to fix the connection was Mudfish with FullVPN enabled. It almost seems like our traffic is being filtered in general once it hits a certain threshold of users. I also cannot download or patch FFXIV without using a VPN - the connection will constantly drop and cause the download to cancel. I do not have this problem with the WoW servers that are also located in LA - I have 25ms with no packet loss during primetime vs FFXIV's 80ms and 30% packetloss during mid-peak hours.

Edit3: Still using Mudfish to resolve packetloss issues. Their item for FFXIV works for me now, so I no longer have to use FullVPN.

[LadyAmanita]

Type of Issue/Feedback: Lots more lag, frequent disconnects
Name of your Internet Service Provider (ISP): Bell Aliant
State/Country: Nova Scotia, Canada
Date/Time: (When did the issue start happening, at what specific times does this issue arise, if any.) This started happening after the server migration
World Name: Hyperion
Frequency: often

[coldrazer]

Type of Issue/Feedback: Very high ping, from an average of 180-200 before migration to 300-330 afterwards
Name of your Internet Service Provider (ISP): Vivo
State/Country: MT/Brazil
Date/Time: since the datacenters migration
World Name: Brynhildr
Frequency: Permanent
Traceroute records:

Rastreando a rota para 204.2.229.100 com no máximo 30 saltos

1 <1 ms <1 ms <1 ms 192.168.0.1
2 <1 ms <1 ms <1 ms PowerBox.home [192.168.25.1]
3 5 ms 5 ms 4 ms gvt-b-se01.cba.gvt.net.br [189.59.241.130]
4 6 ms 5 ms 5 ms 177.205.8.157.static.adsl.gvt.net.br [177.205.8.157]
5 38 ms 31 ms 31 ms 201.22.64.99.dynamic.dialup.gvt.net.br [201.22.64.99]
6 40 ms 40 ms 39 ms xe-7-0-6-4-grtsanem4.priv.net.telefonicaglobalsolutions.com [216.184.112.122]
7 147 ms 150 ms 151 ms 94.142.98.155
8 174 ms 174 ms 174 ms 176.52.251.202
9 331 ms 256 ms 266 ms 213.140.35.209
10 268 ms 267 ms 267 ms 5.53.3.18
11 270 ms 269 ms 269 ms ae1-0-ntt-grtamstc1.net.telefonicaglobalsolutions.com [213.140.53.97]
12 273 ms 272 ms 272 ms ae-4.r25.amstnl02.nl.bb.gin.ntt.net [129.250.2.146]
13 263 ms 263 ms 264 ms ae-5.r23.asbnva02.us.bb.gin.ntt.net [129.250.6.162]
14 319 ms 318 ms 319 ms ae-10.r22.snjsca04.us.bb.gin.ntt.net [129.250.6.237]
15 320 ms 319 ms 320 ms ae-40.r02.snjsca04.us.bb.gin.ntt.net [129.250.3.121]
16 319 ms 319 ms 318 ms ae-2.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.33]
17 325 ms 324 ms 325 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
18 320 ms 320 ms 319 ms 204.2.229.234
19 319 ms 319 ms 319 ms 204.2.229.100

Rastreamento concluído.