(SE's ISP) NTT Network is unstable and causing major rubberbanding/lag/disconnects

Windows client
Illinois, USA
Comcast Internet
Wired directly in modem
ports all forwarded
Cookies cleared
etc.

I cannot play with this poor performance. My reports are condensed in your Sticky that was moved to separate support as you requested.
http://forum.square-enix.com/ffxiv/t...NA-Data-Center

Can I advance this ticket to customer service for compensation for the lack of service?

I'm pretty serious at this point. I would really appreciate some sort of customer support here. I'm literally at my wits end.

I'm going to keep track of how many days and how much time this has hindered the service. Hopefully I can get compensated for my money for the amount of time this issue is wasting for me.


~~ List of Tracerts during effected time recorded since January 2018 ~~

For anyone who does not understand the tracert, the moment my connection reaches the NTT service (which is employed by Square Enix) my ping sky rockets and packet loss presents itself. The packet loss can be identified with a " * " sign when communication fails. This is my compiled list since the start of this year of just the moments I chose to record during critical play time via raiding or other semi difficult content. Please excuse the long list, but this has effected me for far to long.

01-11-2018 07:09 PM
https://i.imgur.com/pWephpd.png

01-12-2018 09:36 PM
https://i.imgur.com/MvPBDQU.png

01-15-2018 10:09 PM
https://i.imgur.com/cv5vTGT.png

01-18-2018 10:56 PM
https://i.imgur.com/q5QkG9s.jpg

01-23-2018 10:13 PM
https://i.imgur.com/6QTcGyG.png

01-31-2018 09:42 PM
https://i.imgur.com/ZM2cSPo.jpg

02-03-2018 11:59 PM
https://i.imgur.com/QsZc53n.jpg

03-01-2018 09:50 PM
https://i.imgur.com/d2j1XrS.png

03-11-2018 07:50 PM

Code:

---

Tracing route to 204.2.229.97 over a maximum of 30 hops

  1    1 ms    1 ms    1 ms  10.0.0.1
  2    10 ms    11 ms    16 ms  96.120.24.33
  3    9 ms    8 ms    9 ms  GE-1-46-ur01.mortongrove.il.chicago.comcast.net [68.86.117.209]
  4    9 ms    9 ms    12 ms  162.151.37.113
  5    11 ms    9 ms    12 ms  be-124-ar01.elmhurst.il.chicago.comcast.net [69.139.235.53]
  6    11 ms    14 ms    12 ms  be-33491-cr01.chicago.il.ibone.comcast.net [68.86.92.33]
  7    13 ms    13 ms    14 ms  be-10506-cr02.350ecermak.il.ibone.comcast.net [68.86.86.229]
  8    12 ms    12 ms    19 ms  be-10577-pe03.350ecermak.il.ibone.comcast.net [68.86.86.2]
  9    88 ms    93 ms  104 ms  ae-26.a02.chcgil09.us.bb.gin.ntt.net [129.250.66.65]
 10  178 ms  184 ms  182 ms  ae-3.r07.chcgil09.us.bb.gin.ntt.net [129.250.5.111]
 11    *      117 ms  136 ms  ae-5.r21.chcgil09.us.bb.gin.ntt.net [129.250.4.213]
 12  193 ms  168 ms  184 ms  ae-5.r22.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
 13  180 ms  190 ms  189 ms  ae-19.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.27]
 14  191 ms    *      201 ms  ae-4.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.57]
 15  192 ms    *      184 ms  xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
 16  143 ms  138 ms    *    204.2.229.234
 17  194 ms  200 ms  188 ms  204.2.229.97

Trace complete.

---

04-25-2018 09:32 PM

Code:

---

Tracing route to 204.2.229.10 over a maximum of 30 hops

  1    1 ms    1 ms    2 ms  10.0.0.1
  2    11 ms    10 ms    9 ms  96.120.24.33
  3    8 ms    10 ms    10 ms  GE-1-46-ur01.mortongrove.il.chicago.comcast.net [68.86.117.209]
  4    9 ms    9 ms    10 ms  162.151.37.113
  5    11 ms    12 ms    13 ms  be-124-ar01.elmhurst.il.chicago.comcast.net [69.139.235.53]
  6    11 ms    12 ms    12 ms  be-33491-cr01.chicago.il.ibone.comcast.net [68.86.92.33]
  7    13 ms    12 ms    14 ms  be-10506-cr02.350ecermak.il.ibone.comcast.net [68.86.86.229]
  8    11 ms    11 ms    12 ms  be-10577-pe03.350ecermak.il.ibone.comcast.net [68.86.86.2]
  9  100 ms    90 ms    73 ms  ae-26.a02.chcgil09.us.bb.gin.ntt.net [129.250.66.65]
 10    80 ms    68 ms    80 ms  ae-3.r07.chcgil09.us.bb.gin.ntt.net [129.250.5.111]
 11  104 ms    57 ms    86 ms  ae-5.r21.chcgil09.us.bb.gin.ntt.net [129.250.4.213]
 12    *      163 ms  171 ms  ae-5.r22.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
 13  174 ms  186 ms  167 ms  ae-19.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.27]
 14  158 ms  159 ms  152 ms  ae-4.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.57]
 15  181 ms  190 ms  177 ms  xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
 16    70 ms    *        *    204.2.229.234
 17  109 ms  105 ms    99 ms  204.2.229.10

Trace complete.

---

05-08-2018 10:28 PM

Code:

---

Tracing route to 204.2.229.84 over a maximum of 30 hops

  1    1 ms    1 ms    2 ms  10.0.0.1
  2    11 ms    11 ms    9 ms  96.120.24.33
  3    8 ms    9 ms    9 ms  GE-1-46-ur01.mortongrove.il.chicago.comcast.net [68.86.117.209]
  4    9 ms    9 ms    18 ms  162.151.37.113
  5    12 ms    11 ms    11 ms  be-124-ar01.elmhurst.il.chicago.comcast.net [69.139.235.53]
  6    11 ms    12 ms    12 ms  be-33491-cr01.chicago.il.ibone.comcast.net [68.86.92.33]
  7    22 ms    12 ms    12 ms  be-10506-cr02.350ecermak.il.ibone.comcast.net [68.86.86.229]
  8    16 ms    12 ms    12 ms  be-10577-pe03.350ecermak.il.ibone.comcast.net [68.86.86.2]
  9  124 ms  131 ms  132 ms  ae-26.a02.chcgil09.us.bb.gin.ntt.net [129.250.66.65]
 10    *      193 ms  188 ms  ae-4.r08.chcgil09.us.bb.gin.ntt.net [129.250.4.157]
 11  135 ms  126 ms  140 ms  ae-0.r21.chcgil09.us.bb.gin.ntt.net [129.250.2.205]
 12  189 ms  189 ms  181 ms  ae-5.r22.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
 13  193 ms  189 ms  194 ms  ae-40.r02.snjsca04.us.bb.gin.ntt.net [129.250.3.121]
 14  194 ms  185 ms  192 ms  ae-3.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.11]
 15  187 ms  193 ms  191 ms  xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
 16  187 ms  191 ms    *    204.2.229.234
 17  194 ms    *      187 ms  204.2.229.84

---

05-16-18 08:10pm

Code:

---

Tracing route to 204.2.229.97 over a maximum of 30 hops

  1    1 ms    1 ms    1 ms  10.0.0.1
  2    9 ms    10 ms    8 ms  96.120.24.33
  3    8 ms    9 ms    9 ms  te-0-7-0-0-sur04.elmhurst.il.chicago.comcast.net [68.86.117.209]
  4    9 ms    10 ms    17 ms  162.151.37.113
  5    11 ms    10 ms    10 ms  be-124-ar01.elmhurst.il.chicago.comcast.net [69.139.235.53]
  6    10 ms    15 ms    11 ms  be-33491-cr01.chicago.il.ibone.comcast.net [68.86.92.33]
  7    12 ms    12 ms    12 ms  be-10506-cr02.350ecermak.il.ibone.comcast.net [68.86.86.229]
  8    12 ms    12 ms    11 ms  be-10577-pe03.350ecermak.il.ibone.comcast.net [68.86.86.2]
  9    11 ms    14 ms    19 ms  ae-26.a02.chcgil09.us.bb.gin.ntt.net [129.250.66.65]
 10  189 ms  191 ms  181 ms  ae-3.r07.chcgil09.us.bb.gin.ntt.net [129.250.5.111]
 11    11 ms    11 ms    11 ms  ae-5.r21.chcgil09.us.bb.gin.ntt.net [129.250.4.213]
 12  179 ms    *      193 ms  ae-5.r22.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
 13  195 ms    *      196 ms  ae-40.r02.snjsca04.us.bb.gin.ntt.net [129.250.3.121]
 14  188 ms    *        *    ae-3.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.11]
 15    *      191 ms  193 ms  xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
 16    *        *      193 ms  204.2.229.234
 17  193 ms  191 ms  195 ms  204.2.229.97

---

05-17-2018 08:03 PM

Code:

---

Tracing route to 204.2.229.97 over a maximum of 30 hops

  1    1 ms    1 ms    1 ms  10.0.0.1
  2    11 ms    11 ms    9 ms  96.120.24.33
  3    9 ms    9 ms    8 ms  GE-1-46-ur01.mortongrove.il.chicago.comcast.net [68.86.117.209]
  4    11 ms    9 ms    9 ms  162.151.37.113
  5    12 ms    12 ms    19 ms  be-124-ar01.elmhurst.il.chicago.comcast.net [69.139.235.53]
  6    12 ms    16 ms    15 ms  be-33491-cr01.chicago.il.ibone.comcast.net [68.86.92.33]
  7    13 ms    12 ms    21 ms  be-10506-cr02.350ecermak.il.ibone.comcast.net [68.86.86.229]
  8    11 ms    12 ms    18 ms  be-10577-pe03.350ecermak.il.ibone.comcast.net [68.86.86.2]
  9  138 ms  115 ms  105 ms  ae-26.a02.chcgil09.us.bb.gin.ntt.net [129.250.66.65]
 10    *      177 ms  164 ms  ae-3.r07.chcgil09.us.bb.gin.ntt.net [129.250.5.111]
 11  113 ms  116 ms  113 ms  ae-5.r21.chcgil09.us.bb.gin.ntt.net [129.250.4.213]
 12  183 ms  181 ms  185 ms  ae-5.r22.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
 13  188 ms  187 ms    *    ae-40.r02.snjsca04.us.bb.gin.ntt.net [129.250.3.121]
 14  184 ms  193 ms  187 ms  ae-3.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.11]
 15  194 ms  192 ms    *    xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
 16  189 ms    *        *    204.2.229.234
 17  177 ms  181 ms  166 ms  204.2.229.97

---

05-23-18 09:40pm

Code:

---

Tracing route to 204.2.229.97 over a maximum of 30 hops

  1    1 ms    1 ms    1 ms  10.0.0.1
  2    12 ms    13 ms    9 ms  96.120.24.33
  3    9 ms    9 ms    9 ms  te-0-7-0-0-sur04.elmhurst.il.chicago.comcast.net [68.86.117.209]
  4    18 ms    9 ms    9 ms  162.151.37.113
  5    11 ms    12 ms    11 ms  be-124-ar01.elmhurst.il.chicago.comcast.net [69.139.235.53]
  6    13 ms    14 ms    14 ms  be-33491-cr01.chicago.il.ibone.comcast.net [68.86.92.33]
  7    13 ms    20 ms    12 ms  be-10506-cr02.350ecermak.il.ibone.comcast.net [68.86.86.229]
  8    11 ms    12 ms    13 ms  be-10577-pe03.350ecermak.il.ibone.comcast.net [68.86.86.2]
  9    17 ms    12 ms    11 ms  ae-26.a02.chcgil09.us.bb.gin.ntt.net [129.250.66.65]
 10  191 ms  195 ms    *    ae-3.r07.chcgil09.us.bb.gin.ntt.net [129.250.5.111]
 11    14 ms    13 ms    27 ms  ae-5.r21.chcgil09.us.bb.gin.ntt.net [129.250.4.213]
 12    *      195 ms  189 ms  ae-5.r22.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
 13  183 ms  185 ms  183 ms  ae-40.r02.snjsca04.us.bb.gin.ntt.net [129.250.3.121]
 14  188 ms  182 ms  191 ms  ae-3.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.11]
 15  193 ms  185 ms  184 ms  xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
 16  191 ms    *      191 ms  204.2.229.234
 17  197 ms  190 ms    *    204.2.229.97
 18  184 ms  190 ms  185 ms  204.2.229.97

Trace complete.

---

05-28-18 09:15pm

Code:

---

Tracing route to 204.2.229.97 over a maximum of 30 hops

  1    1 ms    1 ms    1 ms  10.0.0.1
  2    12 ms    11 ms    9 ms  96.120.24.33
  3    8 ms    9 ms    9 ms  GE-1-46-ur01.mortongrove.il.chicago.comcast.net [68.86.117.209]
  4    9 ms    10 ms    9 ms  162.151.37.113
  5    11 ms    10 ms    12 ms  be-124-ar01.elmhurst.il.chicago.comcast.net [69.139.235.53]
  6    12 ms    12 ms    13 ms  be-33491-cr01.chicago.il.ibone.comcast.net [68.86.92.33]
  7    12 ms    12 ms    14 ms  be-10506-cr02.350ecermak.il.ibone.comcast.net [68.86.86.229]
  8    11 ms    14 ms    19 ms  be-10577-pe03.350ecermak.il.ibone.comcast.net [68.86.86.2]
  9  130 ms  120 ms  127 ms  ae-26.a02.chcgil09.us.bb.gin.ntt.net [129.250.66.65]
 10  188 ms  186 ms    *    ae-3.r07.chcgil09.us.bb.gin.ntt.net [129.250.5.111]
 11  130 ms  117 ms  120 ms  ae-5.r21.chcgil09.us.bb.gin.ntt.net [129.250.4.213]
 12  157 ms  149 ms  155 ms  ae-5.r22.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
 13  164 ms  164 ms  159 ms  ae-40.r02.snjsca04.us.bb.gin.ntt.net [129.250.3.121]
 14  190 ms  190 ms  196 ms  ae-3.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.11]
 15  130 ms  123 ms  112 ms  xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
 16    *        *        *    Request timed out.
 17  144 ms  140 ms  140 ms  204.2.229.97

Trace complete.


Trace complete.

---

Aether DC
Windows PC
Florida, USA
Comcast, directly connected, all ports forwarded, etc. etc. etc.

Posting in this thread just to leave this message somewhere.
My husband and I switched servers from EU to NA about 3 months ago. We experienced little to no connection issues connecting to EU, and expected a better connection to NA. Instead we started immediately having on and off connection issues, ruining raid nights or keeping us from even doing simple dungeons. We've suffered random disconnections, delay, and input lag that lead the game to being unplayable. We have tried all solutions, even using VPNs but then the instability of those services was just as bothersome.

So you've lost 2 more subscribers due to this issue, and I sincerely hope that this individual and all the others that continue to support your game, get some kind of compensation or at the very least, finally see an end to these issues.

I'm also in Illinois but using Verizon wireless and I can't access any ffxiv related services... Like playing the game on my ps4 or accessing any websites... Like the lodestone forums either...

Good luck getting an answer. Their stance is "It's not our problem."

http://forum.square-enix.com/ffxiv/t...=1#post4672168

Quote:

---

Originally Posted by dark494

Good luck getting an answer. Their stance is "It's not our problem."

http://forum.square-enix.com/ffxiv/t...=1#post4672168

---

That post is ridiculous. If Square Enix is unable to "affect any individual connection route" for their own service provider, with which I assume they have some kind of contract, how are individual users supposed to affect nodes from their service provider? Do they expect us to ask COX or Comcast to route around the bad nodes on NTT's end? That seems unlikely given that I only have control over a small box in my house.

Quote:

---

Originally Posted by Kerwin

Windows client
Illinois, USA
Comcast Internet
Wired directly in modem
ports all forwarded
Cookies cleared
etc.

Code:

---

Tracing route to 204.2.229.97 over a maximum of 30 hops...


  9    11 ms    14 ms    19 ms  ae-26.a02.chcgil09.us.bb.gin.ntt.net [129.250.66.65]
 10  189 ms  191 ms  181 ms  ae-3.r07.chcgil09.us.bb.gin.ntt.net [129.250.5.111]
 11    11 ms    11 ms    11 ms  ae-5.r21.chcgil09.us.bb.gin.ntt.net [129.250.4.213]
 12  179 ms    *      193 ms  ae-5.r22.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
 13  195 ms    *      196 ms  ae-40.r02.snjsca04.us.bb.gin.ntt.net [129.250.3.121]
 14  188 ms    *        *    ae-3.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.11]
 15    *      191 ms  193 ms  xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
 16    *        *      193 ms  204.2.229.234
 17  193 ms  191 ms  195 ms  204.2.229.97

---

---

Specifically to help point out the issue. The issue is communications to/from San Jose. The routers that have the issue are the ones indicated as "snjsca04" in the name. This is on NTT's end and NOT the user's ISP.

So... How is it that SE seems to be swearing up and down that this is not their problem and they can’t do anything about it while offering the same ineffective copy past solutions to everyone that complains when the issue lies with their ISP. Maybe I’m not understanding properly, but it seems they have all the control over this and are the only ones who can fix it by switching who they do business with and that there is nothing short of buying vpn service that can be done on the users end. Seems like they basically do not care about any affected users and potentially losing that sub money.

I guess correcting the issue would cost them more than the potential loss of customers.

My Verizon wireless issue has been resolved...

Hello everyone and thank you for posting on the Final Fantasy XIV Technical Support Forums.

The investigation that was conducted in the thread you are referring to came to the conclusion that the Data Center was not the cause of the issue you are describing. The issue stems from the route which your connection takes to reach the Data Center. This is something we unfortunately cannot control.

In regards to the nodes you are referring to, the lost packets represent information that is not returned to your computer. It's difficult to come to the conclusion that any one node is at fault based on a trace route alone.

It's an unfortunate situation and we wish there was an easy way to solve it, however, there is a limit to what we can do to assist.

Thank you for visiting the Final Fantasy XIV Technical Support Forums.

Quote:

---

Originally Posted by Einmimiria

Hello everyone and thank you for posting on the Final Fantasy XIV Technical Support Forums.

The investigation that was conducted in the thread you are referring to came to the conclusion that the Data Center was not the cause of the issue you are describing. The issue stems from the route which your connection takes to reach the Data Center. This is something we unfortunately cannot control.

In regards to the nodes you are referring to, the lost packets represent information that is not returned to your computer. It's difficult to come to the conclusion that any one node is at fault based on a trace route alone.

It's an unfortunate situation and we wish there was an easy way to solve it, however, there is a limit to what we can do to assist.

Thank you for visiting the Final Fantasy XIV Technical Support Forums.

---

The service I'm getting right now, as we speak, is unplayable.

Tracert as of RIGHT NOW, I cannot raid with this.

Code:

---

Tracing route to 204.2.229.97 over a maximum of 30 hops

  1    1 ms    1 ms    1 ms  10.0.0.1
  2    11 ms    11 ms    9 ms  96.120.24.33
  3    9 ms    9 ms    8 ms  GE-1-46-ur01.mortongrove.il.chicago.comcast.net [68.86.117.209]
  4    11 ms    9 ms    9 ms  162.151.37.113
  5    12 ms    12 ms    19 ms  be-124-ar01.elmhurst.il.chicago.comcast.net [69.139.235.53]
  6    12 ms    16 ms    15 ms  be-33491-cr01.chicago.il.ibone.comcast.net [68.86.92.33]
  7    13 ms    12 ms    21 ms  be-10506-cr02.350ecermak.il.ibone.comcast.net [68.86.86.229]
  8    11 ms    12 ms    18 ms  be-10577-pe03.350ecermak.il.ibone.comcast.net [68.86.86.2]
  9  138 ms  115 ms  105 ms  ae-26.a02.chcgil09.us.bb.gin.ntt.net [129.250.66.65]
 10    *      177 ms  164 ms  ae-3.r07.chcgil09.us.bb.gin.ntt.net [129.250.5.111]
 11  113 ms  116 ms  113 ms  ae-5.r21.chcgil09.us.bb.gin.ntt.net [129.250.4.213]
 12  183 ms  181 ms  185 ms  ae-5.r22.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
 13  188 ms  187 ms    *    ae-40.r02.snjsca04.us.bb.gin.ntt.net [129.250.3.121]
 14  184 ms  193 ms  187 ms  ae-3.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.11]
 15  194 ms  192 ms    *    xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
 16  189 ms    *        *    204.2.229.234
 17  177 ms  181 ms  166 ms  204.2.229.97

---

What can you do to solve this problem? What can you do to compensate this problem?

Quote:

---

Originally Posted by Einmimiria

snip

---

It is good that the Data Center was looked at and determined to not be the issue; which is fine, expected and even great. The problem is that it looks like they just dropped it as soon as it wasn't the data center. Which if you follow my deduction below I can see where it isn't the data center. Unfortunately when it comes to hosting servers your "up-time" doesn't just extend to your data center but also the circuits it uses to get out and back in to said DC.


Basically if your internet gateway is mismanaging traffic, you can say that SE's servers and the gateway have 99.9% uptime but that doesn't mean that your gateway is directing traffic to you appropriately.


I also have a resume to submit if anyone is interested.

Quote:

---

Originally Posted by Einmimiria

however, there is a limit to what we can do to assist.

---

I'm continually inching closer and closer to just qutting the game altogether but I've stuck it out this long hoping for a change (because if I did quit I'd never come back due to poor service and losing a house), a change that apparently is never coming. So you're telling me that you will not lift a finger because "It's difficult" to determine the problem? Have you guys not once contacted the people that give you service to determine the problem?

It really feels like you guys aren't being transparent at all with the effort you're putting in.

Quote:

---

Originally Posted by Einmimiria

Hello everyone and thank you for posting on the Final Fantasy XIV Technical Support Forums.

The investigation that was conducted in the thread you are referring to came to the conclusion that the Data Center was not the cause of the issue you are describing. The issue stems from the route which your connection takes to reach the Data Center. This is something we unfortunately cannot control.

In regards to the nodes you are referring to, the lost packets represent information that is not returned to your computer. It's difficult to come to the conclusion that any one node is at fault based on a trace route alone.

It's an unfortunate situation and we wish there was an easy way to solve it, however, there is a limit to what we can do to assist.

Thank you for visiting the Final Fantasy XIV Technical Support Forums.

---

Einmimiria, the problem is we are all seeing the issues in hops on NTT's network which IS the ISP that SE has chosen to go with. These things are never that simple. Maybe Comcast and others are in a price disagreement. Maybe NTT doesn't recognize the issue. I completely agree that the issue is not with your datacenter. But as a direct customer of NTT your company has far more power than any of us. Tickets opened to Comcast are either closed outright because internet is working or if you do get a good enough tech they explain that NTT controls those routes and that its not on Comcast at all. As a customer we are stuck in the middle.

If SE has more information from NTT that we can use to start opening tickets en mass to our personal ISP's we would gladly do it. Without that knowledge though we have no ground to stand on.

Quote:

---

Originally Posted by Athoen

SNIP

---

Essentially this, very well put (better than I could word). Once our ISP reaches NTT's network it is completely out of the control of our ISP. This is why I frequently mention San Jose's routers being the issue. Once we reach our first NTT router it is up to that router configuration to determine where to go next and not the ISP.

Using Kerwin's and my hops: http://forum.square-enix.com/ffxiv/t...T-Router-Issue here is what I believe is going on in steps:

1. You to ISP
2. ISP to NTT
3. NTT Routes to nearest NTT WAN Router Junction to Data Center (San Jose Routers Labeled *.SNJSCA04.*)
4. Lag or flooded connectivity occurs at the NTT WAN Routers/Load-balancers at SNJSCA04 junction causing connections to drop or be delayed.
-> Could be a bad configuration of load balancing (Config issue).
-> Could be that the total allotted broadband spectrum at NTT is at full capacity via Hardware/Soft config. This is usually indicative of not enough hardware or licensing to handle the data load.
-> Could be a DOS attack, or a DOS issue caused by heavy activity at specific times.
5. San Jose routes to physical DC that SE's NA servers reside. (Sacramento routers labeled *.SCRMCA02.*)
6. Sacramento routers route to SE's physical/virtual hardware at 204.2.229.X

Using the above deduction. We can surmise that SE is indeed right, its not the data center; but it is a choke point at the routers (that NTT owns) short ways up stream.

The reason why I am so upset is that this problem continues to plague this game for me everynight.

Do I continue to post new threads in regards to the issue or is the mod team expecting me to just deal with it and tell me "Oh well!"

I pay a sub for service. And I know in the user agreement that the service may go down, but in this case the service is still available, but at such poor quality.

What am I supposed to do about this? My ISP has no power over NTT's network. NTT will not deal with people who are not their customers and Square Enix Mods tell me to contact my ISP! It's a circle of passing blame!

I will condense my reports and tracerts to this thread if I must. Since the Mod team will now be dealing with people individually, I suspect a large amount new threads will start popping up regarding this issue.

I just wanted to say this is affecting me as well. I have tried all of the troubleshooting steps and it seems like I'm in the same position as everyone here. I want to play the game, but I'm not even sure what I'm supposed to do... Is this something that's going to be fixed, or is everyone affected by this just out of luck?

At this point, it seems clear that SE's stance is "Screw you, thanks for the money." Hope it's worth losing thousands of customers in the U.S. over the issue. Most people won't even bother to come here and complain, they'll just stop playing and move on.

Effectively when I have to quit because of this, you lose 6 subs because my static group will be leaving with me. Comcast levels of bad customer support in this game.

Nice start to the patch day!

Thank you! :mad:

As of 7:30 PM CST:

Code:

---

Tracing route to 204.2.229.97 over a maximum of 30 hops

  1    1 ms    1 ms    1 ms  10.0.0.1
  2    14 ms    13 ms    10 ms  96.120.24.33
  3    16 ms    11 ms    13 ms  te-0-7-0-0-sur04.elmhurst.il.chicago.comcast.net [68.86.117.209]
  4    9 ms    9 ms    10 ms  162.151.37.113
  5    11 ms    12 ms    12 ms  be-124-ar01.elmhurst.il.chicago.comcast.net [69.139.235.53]
  6    12 ms    12 ms    14 ms  be-33491-cr01.chicago.il.ibone.comcast.net [68.86.92.33]
  7    13 ms    13 ms    12 ms  be-10506-cr02.350ecermak.il.ibone.comcast.net [68.86.86.229]
  8    14 ms    11 ms    11 ms  be-10577-pe03.350ecermak.il.ibone.comcast.net [68.86.86.2]
  9    16 ms    15 ms    18 ms  ae-26.a02.chcgil09.us.bb.gin.ntt.net [129.250.66.65]
 10  185 ms  189 ms  187 ms  ae-3.r07.chcgil09.us.bb.gin.ntt.net [129.250.5.111]
 11    14 ms    13 ms    20 ms  ae-5.r21.chcgil09.us.bb.gin.ntt.net [129.250.4.213]
 12  185 ms  183 ms  185 ms  ae-5.r22.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
 13    *      188 ms  179 ms  ae-40.r02.snjsca04.us.bb.gin.ntt.net [129.250.3.121]
 14  181 ms  193 ms  189 ms  ae-3.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.11]
 15  190 ms  193 ms  182 ms  xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
 16  183 ms    *      181 ms  204.2.229.234
 17  161 ms  164 ms  164 ms  204.2.229.97

Trace complete.

---

As of 9:40pm CST:

Code:

---

Tracing route to 204.2.229.97 over a maximum of 30 hops

  1    1 ms    1 ms    1 ms  10.0.0.1
  2    12 ms    13 ms    9 ms  96.120.24.33
  3    9 ms    9 ms    9 ms  te-0-7-0-0-sur04.elmhurst.il.chicago.comcast.net [68.86.117.209]
  4    18 ms    9 ms    9 ms  162.151.37.113
  5    11 ms    12 ms    11 ms  be-124-ar01.elmhurst.il.chicago.comcast.net [69.139.235.53]
  6    13 ms    14 ms    14 ms  be-33491-cr01.chicago.il.ibone.comcast.net [68.86.92.33]
  7    13 ms    20 ms    12 ms  be-10506-cr02.350ecermak.il.ibone.comcast.net [68.86.86.229]
  8    11 ms    12 ms    13 ms  be-10577-pe03.350ecermak.il.ibone.comcast.net [68.86.86.2]
  9    17 ms    12 ms    11 ms  ae-26.a02.chcgil09.us.bb.gin.ntt.net [129.250.66.65]
 10  191 ms  195 ms    *    ae-3.r07.chcgil09.us.bb.gin.ntt.net [129.250.5.111]
 11    14 ms    13 ms    27 ms  ae-5.r21.chcgil09.us.bb.gin.ntt.net [129.250.4.213]
 12    *      195 ms  189 ms  ae-5.r22.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
 13  183 ms  185 ms  183 ms  ae-40.r02.snjsca04.us.bb.gin.ntt.net [129.250.3.121]
 14  188 ms  182 ms  191 ms  ae-3.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.11]
 15  193 ms  185 ms  184 ms  xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
 16  191 ms    *      191 ms  204.2.229.234
 17  197 ms  190 ms    *    204.2.229.97
 18  184 ms  190 ms  185 ms  204.2.229.97

Trace complete.

---

Terrible terrible service! This lag makes this game unplayable! Still awful connection pushing over 2 hours now!

I'm getting the same thing, just different nodes from NTT starting with "ae-5.a00.lsanca20.us.bb.gin.ntt.net".

But don't worry I'm sure they'll tell you they won't talk to their ISP about it and instead tell us to talk to ours despite it being out of their jurisdiction.

I am also suffering from the same issue. There is literally nothing wrong with my connection and my ISP, but I can't even do a Quest Duty without it disconnecting me. So what do we, paying customers do? I can't play the game I'm subbing for at reasonable quality? This is not out of your control Square, you provide the game, you must also provide quality connections from your end as well. I expect compensation for hours of unplayable game time, Square Enix. We are the reason this game is sustainable. I understand that there are limits to what can be done, but it has been an ongoing issue since patch 4.2 that has yet to be resolved. What must we say to garner further attention? What must happen that it warrants undivided attention? The response here is disrespectful to the players, who are going out of their way to *show* you that is not their fault, and that Square Enix are the only ones who can provide a solution. Unacceptable.

Only thing you can do is vote with your feet/wallet. I went from a year of flawless play to five days of straight unplayabilty.

So I turned off my renewing subscription. I have 42 days left on my account. That's their countdown to fix it.

I live in Sacramento, California and during prime time my connection to Japanese servers in FF11 is better. The server is in the same city as me and I want it back in Canada because at least I can play consistently. The issue is with the NTT nodes and has been for nearly a year. At this point I dread doing anything on ff14 when I get home because I don't know how bad the lag or packet loss will be.

I have been hopeful that at some point the issue will be resolved(or at least mitigated), but given last weeks response that seems unlikely. Since the service I am getting is too poor to use adequately I have canceled my automatic renew. My boyfriend has also done the same.

We got tired of posting tracert after tracert in the other thread since they moved the servers 1 year ago. It's always been bad and it's always been NTT's fault and SE has consistently refused to do anything about it. They chose this partnership with NTT and they're going to reap what they've sowed. This cycle just never ends.

Consider my subscription cancelled.

Just a second opinion my cousin had same thing with NTT but he decided to change all cords and had the internet company come out and change the ones on outside due to they were outdated from back in the 80's I suggest you check the cords they might be out of date and picking up noise.

new cords are better and seems to got rid of his issue.

also note the guys who came out found out another company had installed a noise filter on the end of his cord running to his out which lowers the noise so that others dont get messed up but lowers quality of your internet and signal.

it was this orange tag and that orange filter they removed it and everything went back to normal.

Quote:

---

Originally Posted by Zeonx

Just a second opinion my cousin had same thing with NTT but he decided to change all cords and had the internet company come out and change the ones on outside due to they were outdated from back in the 80's I suggest you check the cords they might be out of date and picking up noise.

new cords are better and seems to got rid of his issue.

also note the guys who came out found out another company had installed a noise filter on the end of his cord running to his out which lowers the noise so that others dont get messed up but lowers quality of your internet and signal.

---

I did that a little over a year ago and have had many techs out here since then as well as over the phone customer support. Both my ISP and I are in agreement that NTT is to blame for this connectivity issue and they have informed me that there is nothing they can do. Though thanks for your input, this problem lies with Square Enix.

Quote:

---

Originally Posted by Kerwin

I did that a little over a year ago and have had many techs out here since then as well as over the phone customer support. Both my ISP and I are in agreement that NTT is to blame for this connectivity issue and they have informed me that there is nothing they can do. Though thanks for your input, this problem lies with Square Enix.

---

you see that orange tag he had that and that orange thing on the end that screws on messes with your internet it blocks signals so that others don't get messed up.

they removed it off his and it fixed it. thing is he had to push them to come and fix it and it was messed up for months.

sometimes it can be under the road on main line and yes he lives right near where the servers are and was getting drops from NTT but after that thing was removed it seem to fix it.

http://i.imgur.com/wFFlMNB.jpg

Quote:

---

Originally Posted by Zeonx

you see that orange tag he had that and that orange thing on the end that screws on messes with your internet it blocks signals so that others don't get messed up.

they removed it off his and it fixed it. thing is he had to push them to come and fix it and it was messed up for months.

sometimes it can be under the road on main line and yes he lives right near where the servers are and was getting drops from NTT but after that thing was removed it seem to fix it.

http://i.imgur.com/wFFlMNB.jpg

---

It's absolutely NOT this. It has nothing to do with this recurring problem.

As of 10:00pm CST. Again. Every night.

Code:

---

Tracing route to 204.2.229.97 over a maximum of 30 hops

  1    1 ms    1 ms    1 ms  10.0.0.1
  2    10 ms    9 ms    10 ms  96.120.24.33
  3    9 ms    11 ms    12 ms  te-0-7-0-0-sur04.elmhurst.il.chicago.comcast.net [68.86.117.209]
  4    8 ms    8 ms    16 ms  162.151.37.113
  5    12 ms    12 ms    9 ms  be-124-ar01.elmhurst.il.chicago.comcast.net [69.139.235.53]
  6    11 ms    12 ms    11 ms  be-33491-cr01.chicago.il.ibone.comcast.net [68.86.92.33]
  7    14 ms    12 ms    14 ms  be-10506-cr02.350ecermak.il.ibone.comcast.net [68.86.86.229]
  8    15 ms    17 ms    14 ms  be-10577-pe03.350ecermak.il.ibone.comcast.net [68.86.86.2]
  9    12 ms    12 ms    12 ms  ae-26.a02.chcgil09.us.bb.gin.ntt.net [129.250.66.65]
 10  187 ms  181 ms  181 ms  ae-3.r07.chcgil09.us.bb.gin.ntt.net [129.250.5.111]
 11    12 ms    16 ms    19 ms  ae-5.r21.chcgil09.us.bb.gin.ntt.net [129.250.4.213]
 12    *      183 ms  187 ms  ae-5.r22.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
 13  184 ms  197 ms  187 ms  ae-40.r02.snjsca04.us.bb.gin.ntt.net [129.250.3.121]
 14  189 ms  185 ms  200 ms  ae-3.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.11]
 15  192 ms  187 ms  178 ms  xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
 16    *        *      191 ms  204.2.229.234
 17  180 ms  183 ms  187 ms  204.2.229.97

Trace complete.

---

Guess what? I was forced to leave the new lighthouse 24 man raid because of this again! Thank you for ruining the experience! Thank you for fixing this problem! :mad:

I took this 10 minute snapshot while doing the new 24-man raid, but this problem has been happening for several months now.

https://i.imgur.com/YCZ7kxJ.png - a 10 minute snapshot taken using Pingplotter. Red bars = no data sent to or recieved from game servers (and as you can see from the bar graph on top, that all starts when the data hits NTT servers)

ISPs will not fix this routing issue. Us customers cannot fix this. This requires some work from your end, SE. Anyone blaming anything other than NTT servers directly has no idea what we're talking about.

That's just depressing. I'm affected too but since I play from hawaii I always have around 100 ping anyway. It must really suck if you live near the servers as the impact is much more severe.

Seriously just what is it going to take for a real reply from Square Enix? And I'm not talking about the unhelpful moderator responses telling us to up open ports up or talk to our ISPs (no offense forum employees).

I would just like to update this group with the situation. As it stands I had to purchase Mudfish VPN in order to properly raid without lag during my normal playtime because SE refuses to acknowledge the problem. Also to help make a point, while using mudfish I specifically connected to nodes in San Jose and had the exact same issue and had to bounce off another node in order to reduce the lag. I feel like this confirms my initial suspicions that the issue is ongoing from NTT routers upstream from the Data Center. I implore SE to acknowledge that there are internet routing issues related to NTT.

Code:

---

Tracing route to 204.2.229.97 over a maximum of 30 hops

  1    1 ms    1 ms    1 ms  10.0.0.1
  2    12 ms    11 ms    9 ms  96.120.24.33
  3    8 ms    9 ms    9 ms  GE-1-46-ur01.mortongrove.il.chicago.comcast.net [68.86.117.209]
  4    9 ms    10 ms    9 ms  162.151.37.113
  5    11 ms    10 ms    12 ms  be-124-ar01.elmhurst.il.chicago.comcast.net [69.139.235.53]
  6    12 ms    12 ms    13 ms  be-33491-cr01.chicago.il.ibone.comcast.net [68.86.92.33]
  7    12 ms    12 ms    14 ms  be-10506-cr02.350ecermak.il.ibone.comcast.net [68.86.86.229]
  8    11 ms    14 ms    19 ms  be-10577-pe03.350ecermak.il.ibone.comcast.net [68.86.86.2]
  9  130 ms  120 ms  127 ms  ae-26.a02.chcgil09.us.bb.gin.ntt.net [129.250.66.65]
 10  188 ms  186 ms    *    ae-3.r07.chcgil09.us.bb.gin.ntt.net [129.250.5.111]
 11  130 ms  117 ms  120 ms  ae-5.r21.chcgil09.us.bb.gin.ntt.net [129.250.4.213]
 12  157 ms  149 ms  155 ms  ae-5.r22.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
 13  164 ms  164 ms  159 ms  ae-40.r02.snjsca04.us.bb.gin.ntt.net [129.250.3.121]
 14  190 ms  190 ms  196 ms  ae-3.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.11]
 15  130 ms  123 ms  112 ms  xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
 16    *        *        *    Request timed out.
 17  144 ms  140 ms  140 ms  204.2.229.97

Trace complete.

---

Thanks for nothing. Wonderful lag!

Quote:

---

Originally Posted by Zephanoa

I would just like to update this group with the situation. As it stands I had to purchase Mudfish VPN in order to properly raid without lag during my normal playtime because SE refuses to acknowledge the problem. Also to help make a point, while using mudfish I specifically connected to nodes in San Jose and had the exact same issue and had to bounce off another node in order to reduce the lag. I feel like this confirms my initial suspicions that the issue is ongoing from NTT routers upstream from the Data Center. I implore SE to acknowledge that there are internet routing issues related to NTT.

---

Yeah, i'm on EU and i use Mudfish too and it kinda removes most lag, using fast connect and a server that has low Ping but not much traffic stat as those are the servers with most people and can cause spikes in latency.

Hello!

I will be moving this thread to "separate support required" Being that we have suggested contacting your ISP regarding these issue. If you ever have any other technical support issues please do not hesitate to create a new thread so we can assist.

Thank you for playing Final Fantasy XIV! Hope to see you online.