North American Data Center Lag

Everyone in my raid group that is South USA or West Coast is experiencing intermittent terrible lag regardless of zone/instance. When I ping the data center, I'm getting intermittent 25% data packet loss.

I've been having the same issues this evening. Frequent disconnects and severe lag.

The issue apears to be Comcast, everyone i talked to that lagged said they used Comcast.

It's not Comcast. Doing a traceroute, it seems to be an NTT node that is the problem.

I can attest to this, this has been affecting everyone I've talked to in the datacenter. There seems to be latency issues going on that needs to be resolved server end.

Quote:

---

Originally Posted by Chudah

It's not Comcast. Doing a traceroute, it seems to be an NTT node that is the problem.

---

I concur. rtt increases significantly or times out when hitting ae-69.r06.asbnva02.us.bb.gin.ntt.net and ae-2.r22.asbnva02.us.bb.gin.ntt.net in my case.

Quote:

---

Originally Posted by Chudah

It's not Comcast. Doing a traceroute, it seems to be an NTT node that is the problem.

---

NTT node? Im playing from Sweden, having zero issues here connecting to the american servers.

Quote:

---

Originally Posted by Windwalker

NTT node? Im playing from Sweden, having zero issues here connecting to the american servers.

---

You're likely being routed through different nodes. Not everyone is having the problem, but everyone who is routed through certain NTT nodes are.

I'm having lag issues as well but some friends on my server are not, one of whom is in the same state.
I'm the only one of us who has Comcast.

I've been experiencing the same problem just now. The error I keep getting is a 90006 error that keeps lagging and disconnecting me out of the game.

You can run a trace route by opening up your command prompt and typing in tracert 204.2.229.9

This is my most recent result. I blanked out my own IP, but as you can see the response time jumps up once it hits the ntt.net nodes

1 2 ms 2 ms 1 ms 10.0.0.1
2 12 ms 11 ms 10 ms xxxxxxxxxx
3 11 ms 11 ms 10 ms be160-rur02.elmhurst.il.chicago.comcast.net [96.110.163.5]
4 10 ms 10 ms 9 ms hu-0-18-0-0-sur07.elmhurst.il.chicago.comcast.net [162.151.92.141]
5 113 ms 27 ms 12 ms be-111-ar01.area4.il.chicago.comcast.net [162.151.92.121]
6 12 ms 14 ms 16 ms be-33491-cr02.350ecermak.il.ibone.comcast.net [68.86.91.165]
7 11 ms 12 ms 34 ms be-10577-pe03.350ecermak.il.ibone.comcast.net [68.86.86.2]
8 117 ms 113 ms 111 ms ae-26.a02.chcgil09.us.bb.gin.ntt.net [129.250.66.65]
9 75 ms 68 ms 67 ms ae-3.r07.chcgil09.us.bb.gin.ntt.net [129.250.5.111]
10 115 ms 126 ms 135 ms ae-5.r21.chcgil09.us.bb.gin.ntt.net [129.250.4.213]
11 76 ms 68 ms 70 ms ae-5.r22.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
12 80 ms 72 ms 72 ms ae-19.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.27]
13 79 ms 73 ms 79 ms ae-4.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.57]
14 78 ms 74 ms 71 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [192.80.16.2]
15 71 ms 71 ms * 204.2.229.234
16 76 ms 75 ms 72 ms 204.2.229.9

Quote:

---

Originally Posted by Chudah

You can run a trace route by opening up your command prompt and typing in tracert 204.2.229.9

This is my most recent result. I blanked out my own IP, but as you can see the response time jumps up once it hits the ntt.net nodes

1 2 ms 2 ms 1 ms 10.0.0.1
2 12 ms 11 ms 10 ms xxxxxxxxxx
3 11 ms 11 ms 10 ms be160-rur02.elmhurst.il.chicago.comcast.net [96.110.163.5]
4 10 ms 10 ms 9 ms hu-0-18-0-0-sur07.elmhurst.il.chicago.comcast.net [162.151.92.141]
5 113 ms 27 ms 12 ms be-111-ar01.area4.il.chicago.comcast.net [162.151.92.121]
6 12 ms 14 ms 16 ms be-33491-cr02.350ecermak.il.ibone.comcast.net [68.86.91.165]
7 11 ms 12 ms 34 ms be-10577-pe03.350ecermak.il.ibone.comcast.net [68.86.86.2]
8 117 ms 113 ms 111 ms ae-26.a02.chcgil09.us.bb.gin.ntt.net [129.250.66.65]
9 75 ms 68 ms 67 ms ae-3.r07.chcgil09.us.bb.gin.ntt.net [129.250.5.111]
10 115 ms 126 ms 135 ms ae-5.r21.chcgil09.us.bb.gin.ntt.net [129.250.4.213]
11 76 ms 68 ms 70 ms ae-5.r22.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
12 80 ms 72 ms 72 ms ae-19.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.27]
13 79 ms 73 ms 79 ms ae-4.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.57]
14 78 ms 74 ms 71 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [192.80.16.2]
15 71 ms 71 ms * 204.2.229.234
16 76 ms 75 ms 72 ms 204.2.229.9

---

Hmm, gave it a try, but after the first line im only getting "Request timed out."

Mine won't even make the second jump. Times out every time after the first route... >_<

This has been happening to me as well. Just got the 900006 error screen d/c. Wish square would say something about it :(

Same issue here. Had a ton of people lagging in Copied Factory. After that, I could even craft because of a four-second delay after each button press.

Had the issue last night as well, I tried using a VPN to help but it either took too long to take the helm or it passed naturally.

Couldn't even finish our Eden Savage weeklies because it was so darn bad.

I have been experiencing the same issue. I performed a series of tracerts and notice the bottleneck at the NTT side of things. I have frequent spikes of 90% packet loss to the point where a crafting macro won't even complete successfully. This ultimately results in a 90006 disconnect. I'm on Aether data center connecting from Nashville, TN.

I was experiencing that last night as well, only 1 time during a dungeon run helping my husband during Leveling. Then later during crafting, I don't use any macros for crafting but just hitting a skill and takes several seconds for the skill to go/ watch animation happen. Luckily I waited after each click but it was so annoying having to do that. :(

Can also confirm this issue is still happening now. SE really needs to set this straight. I couldn't even do a roulette because the delay was so awful.

Hello. Still having the same problem as yesterday. Severe lag in instances. I was able to do a expert roulette today ok. But tried a 24 man in copied factory. A good majority of the raid was lagging really bad. I seemed ok in the world but there is some serious issues going on right now with the lag.

This is the only game I'm lagging on. I've tried other games and they work just fine. FF XIV is the issue. I'm typing this as our entire raid in the alliance is dead.

It's started again about 10 or so minutes ago. Was fighting an S Rank and there was more than 30 seconds of lag between what was happening in chat versus what was happening in the battle. Completely unplayable and I laid dead more than 75% of the fight.

Please Square find out what the problem is and fix it. I cannot play like this.

Same here, was fine basically all day but now it's back.

Expect to put up with it for another 3 1/2 to 4 hours. Even if it vanishes during that timeframe it tends to pick back up shortly after. It lasted for like a year and a half of stormblood's lifespan so the only workaround is a VPN or to play very late at night.

It tended to happen almost EVERY, SINGLE, DAY.

Started happening last night at 7 pm EST or so, and started again tonight around the same time, horrible unplayable levels of lag.

Tracing route to 204.2.229.105 over a maximum of 30 hops

1 <1 ms <1 ms 1 ms 192.168.1.1
2 8 ms 7 ms 7 ms 96.120.75.29
3 15 ms 8 ms 8 ms 68.85.129.173
4 8 ms 7 ms 8 ms 96.108.48.162
5 8 ms 9 ms 9 ms 68.86.209.133
6 14 ms 12 ms 13 ms be-101-ar03.plainfield.nj.panjde.comcast.net [96.108.49.105]
7 15 ms 15 ms 14 ms be-33659-cr01.newark.nj.ibone.comcast.net [68.86.90.21]
8 14 ms 15 ms 15 ms be-10203-cr02.newyork.ny.ibone.comcast.net [68.86.85.186]
9 14 ms 15 ms 14 ms be-10381-pe02.111eighthave.ny.ibone.comcast.net [68.86.86.250]
10 127 ms 126 ms 125 ms 50.242.151.70
11 137 ms * * ae-12.r21.nwrknj03.us.bb.gin.ntt.net [129.250.4.130]
12 145 ms 141 ms 132 ms ae-1.r20.chcgil09.us.bb.gin.ntt.net [129.250.2.166]
13 148 ms 132 ms 126 ms ae-4.r21.chcgil09.us.bb.gin.ntt.net [129.250.2.163]
14 203 ms 199 ms * ae-5.r22.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
15 * * 208 ms ae-19.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.27]
16 211 ms 202 ms 210 ms ae-4.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.57]
17 207 ms 212 ms 207 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [192.80.16.2]
18 208 ms 210 ms 207 ms 204.2.229.234
19 210 ms 210 ms 202 ms 204.2.229.105

As can be seen, it begins as soon as it leaves the comcast network and enters the NTT network. Even the Lodestone will lag when loading, it's definitely something downstream and on their end.

Quote:

---

Originally Posted by Mesarthim

Expect to put up with it for another 3 1/2 to 4 hours. Even if it vanishes during that timeframe it tends to pick back up shortly after. It lasted for like a year and a half of stormblood's lifespan so the only workaround is a VPN or to play very late at night.

---

If that's the case I'm considering unsubscribing. This is the only time my brother and I can play together and that's the main reason I play FF14. Unless the game is playable in the afternoon and evening PST I'm unable to enjoy the prime reason I subscribe...

Please at least tell us you're working on it SE.

I'm having the same issue. Never had any major lag problems until last night. Then last night suddenly it's freezing for over 30secs at a time, got booted twice in a dungeon. Finally gave up and couldn't do my dailies. I noticed a little lag when i logged on today but manageable, now suddenly it's freezing up again.
Considering this wasn't really happening until last night, obviously there is an issue somewhere that needs to be fixed.

Quote:

---

Originally Posted by Eva-Shogouki

If that's the case I'm considering unsubscribing. This is the only time my brother and I can play together and that's the main reason I play FF14. Unless the game is playable in the afternoon and evening PST I'm unable to enjoy the prime reason I subscribe...

Please at least tell us you're working on it SE.

---

I wish I could sugercoat it but I'm dead serious. The only help Square Enix will give you is some nonsense about ports... which is completely unhelpful because the problem is their ISP. NTT won't help because we aren't the customer, Square Enix is. We're just the "unlucky ones" who have to deal with ISPs who won't fix their equipment.

https://i.imgur.com/3Xv4XJR.jpg

Average / Minimum / Current

Myself, multiple people in my FC, and half our raid team are having this issue. I wish SE would acknolwedge it, the silence is incredibly disappointing.

Honest question, but if this is something that occurred previously, why is it suddenly happening just now? Been playing since January with only the periodic hiccups you expect with any online service, got through 5.0 release with no issues at all (just the DDoS) and suddenly last night the game became partially unplayable.

Quote:

---

Originally Posted by lymefrogz

Honest question, but if this is something that occurred previously, why is it suddenly happening just now? Been playing since January with only the periodic hiccups you expect with any online service, got through 5.0 release with no issues at all (just the DDoS) and suddenly last night the game became partially unplayable.

---

This is something I'm really curious about too. I didn't have any problems like this in SB or in the last couple months and I haven't changed locales. Could it be that NTT themselves are getting hammered with DDoS attacks?

Welp, day 2 and it's still going like everyone else it seems.

1 <1 ms <1 ms <1 ms 192.168.1.1
2 8 ms 8 ms 10 ms 96.120.118.9
3 9 ms 8 ms 8 ms ae-252-1216-rur02.egypt.tx.houston.comcast.net [96.110.196.121]
4 9 ms 9 ms 8 ms ae-2-rur01.egypt.tx.houston.comcast.net [162.151.135.117]
5 9 ms 18 ms 18 ms ae-41-ar01.bearcreek.tx.houston.comcast.net [68.85.244.97]
6 19 ms 16 ms 15 ms be-33662-cr02.dallas.tx.ibone.comcast.net [68.86.92.61]
7 15 ms 15 ms 14 ms be-12495-pe03.1950stemmons.tx.ibone.comcast.net [68.86.85.194]
8 14 ms 14 ms 21 ms ae-19.a01.dllstx09.us.bb.gin.ntt.net [129.250.66.29]
9 115 ms 100 ms 101 ms ae-3.r11.dllstx09.us.bb.gin.ntt.net [129.250.3.31]
10 18 ms 31 ms 18 ms ae-1.r23.dllstx09.us.bb.gin.ntt.net [129.250.5.25]
11 142 ms 136 ms 135 ms ae-8.r23.snjsca04.us.bb.gin.ntt.net [129.250.4.154]
12 125 ms 137 ms 132 ms ae-45.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.175]
13 151 ms 166 ms 168 ms ae-4.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.57]
14 118 ms 114 ms 118 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [192.80.16.2]
15 155 ms 161 ms 173 ms 204.2.229.234
16 110 ms 111 ms 119 ms 204.2.229.105

Same thing as others,as soon as it leave the isp, the ping sky rockets.

I'm also noticing issues with the forum loading. It's slow to load and sometimes only half loads.

The slightly higher ping times I could deal with, it's the packet loss that's a deal breaker. I'm hopeful that if we make enough noise about this SE will do something.

1 <1 ms <1 ms <1 ms 192.168.1.1
2 10 ms 8 ms 10 ms 96.120.102.209
3 10 ms 10 ms 9 ms po-109-rur102.everett.wa.seattle.comcast.net [96.108.165.173]
4 15 ms 10 ms 10 ms be-29-ar01.seattle.wa.seattle.comcast.net [69.139.164.217]
5 12 ms 14 ms 12 ms be-33650-cr01.seattle.wa.ibone.comcast.net [68.86.93.165]
6 13 ms 11 ms 11 ms be-10847-pe02.seattle.wa.ibone.comcast.net [68.86.86.226]
7 127 ms * 132 ms ae-31.a00.sttlwa01.us.bb.gin.ntt.net [129.250.66.149]
8 157 ms 152 ms 160 ms ae-14.r05.sttlwa01.us.bb.gin.ntt.net [129.250.5.133]
9 123 ms * 131 ms ae-6.r23.sttlwa01.us.bb.gin.ntt.net [129.250.2.88]
10 145 ms 147 ms * ae-3.r23.snjsca04.us.bb.gin.ntt.net [129.250.3.124]
11 151 ms 149 ms 153 ms ae-45.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.175]
12 150 ms 149 ms * ae-4.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.57]
13 * 149 ms 150 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [192.80.16.2]
14 151 ms 162 ms * 204.2.229.234
15 147 ms * * 204.2.229.105
16 153 ms 150 ms 152 ms 204.2.229.105

Just adding my two cents. Average latency I play with is 78-80. Last few nights it has been 200+, not including spikes, and makes the game essentially unplayable for someone not accustomed to such latency. Crafting is dangerous for the obvious reasons and doing something as simple as Copied Factory is quite troublesome. I'm not sure what SE could do or who they could lean on to fix this problem, but it is going to impact the player base in the long run if things aren't adjusted in a reasonable time.

Doing my duty and adding my voice, many in our raid team had lag issues tonight, and the forums are also taking a very long time to load. Please fix this.

Adding to it, several FC mates on Zalera having same issues, some are still playable, some hitting lag so back they are 30s + behind the fight.

Quote:

---

Originally Posted by Sakon90

Adding to it, several FC mates on Zalera having same issues, some are still playable, some hitting lag so back they are 30s + behind the fight.

---

This happened to me when the lag started spiking during an S rank hunt. The hunt target was still had over 25% HP when the people in chat said that it was already dead. Took literally 30+ seconds for my side to catch up. Completely unplayable.

Sounding off, my group had some rough issues with lag last night. I don't think the NTT node is anything Square can do anything about though :/

Quote:

---

Originally Posted by SaberMaxwell

Sounding off, my group had some rough issues with lag last night. I don't think the NTT node is anything Square can do anything about though :/

---

This isn't something SE can do anything about. It's the route your data takes, nothing SE can do about that. A VPN should solve your issues, and they aren't expensive. I used one for a couple of years a while back before we got our EU servers.

I do appreciate it's horribly frustrating but please stop blaming SE. There are plenty of things they do need to sort out, this is not one of them. They can't do anything about this

I was able to run expert rou this morning 7 AM EST without any issues. Not sure if it's due to the issue being resolved or the lack of people online, but I can say for the time I ran the dungeon I didn't have any problems.

Here's hoping it's fixed otherwise it's just going to be related to that many people being online at the same time.