Regarding Reports on Recent Connection Problems with the NA Data Center

**Einmimiria** · 01-17-2018 07:37 AM

Hello everyone,

We are still looking into the connection problems related to the NA Data Center, but we cannot provide a detailed update at this time. This may not be the response many of you were looking for, but we want to stress that our investigation is still ongoing and we are doing everything we can to find a resolution to the issue. If you are still experiencing latency or disconnection issues and have not contributed to this thread, please post the information requested in the initial post of this sticky thread.

We appreciate your patience and understanding on this matter and we will post an update as soon as we are able.

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

**Riko_Futatabi** · 01-18-2018 09:00 AM

Coming up on 5 months of the same old latency issue of getting error 90006 and rubber-banding throughout the day. I don't need a reply from any Moderator to get me to query something. I've troubleshot it all over the passed 5 months. I feel that I'm at the limit of my capability to resolve this issue.

I play on the NA Primal Data Center. My ISP is Sky. I've posted many, many times over the passed few months. If you need any additional info., it's all there in my post history.

Code:

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                          SkyRouter.Home -    0 |  126 |  126 |    0 |    0 |    1 |    0 |
|                   No response from host -  100 |   26 |    0 |    0 |    0 |    0 |    0 |
|             be365.pr2.hobir.isp.sky.com -    0 |  126 |  126 |   16 |   17 |   19 |   17 |
|     ae-3.r02.londen03.uk.bb.gin.ntt.net -    0 |  126 |  126 |   16 |   16 |   18 |   17 |
|     ae-3.r24.londen12.uk.bb.gin.ntt.net -    0 |  126 |  126 |   16 |   16 |   23 |   16 |
|     ae-5.r24.nycmny01.us.bb.gin.ntt.net -   26 |   62 |   46 |   81 |   82 |   87 |   82 |
|     ae-2.r20.sttlwa01.us.bb.gin.ntt.net -   40 |   50 |   30 |  153 |  157 |  185 |  157 |
|     ae-0.r21.sttlwa01.us.bb.gin.ntt.net -   36 |   54 |   35 |  155 |  157 |  175 |  157 |
|     ae-3.r23.snjsca04.us.bb.gin.ntt.net -    0 |  126 |  126 |  168 |  169 |  177 |  169 |
|    ae-45.r01.snjsca04.us.bb.gin.ntt.net -    0 |  126 |  126 |  167 |  167 |  168 |  168 |
|     ae-1.a00.snjsca04.us.bb.gin.ntt.net -    3 |  114 |  111 |  174 |  176 |  202 |  177 |
|xe-0-0-42-1.a00.snjsca04.us.ce.gin.ntt.net -    0 |  126 |  126 |  171 |  171 |  174 |  172 |
|                           204.2.229.242 -   20 |   70 |   56 |  169 |  169 |  170 |  169 |
|                            204.2.229.10 -    0 |  126 |  126 |  172 |  172 |  174 |  173 |
|________________________________________________|______|______|______|______|______|______|

I returned to this game excited for SB launch, but after patch 4.06a my connection went down hill and stayed at the bottom. This has really kicked me in the gut. I want to love your game, I do. But I have never in all my time of playing a MMO had such an awful experience with my connection. Saying all this, I will likely leave this game if patch 4.2 doesn't change anything. I don't want to leave, but having 5 months of getting booted to the title screen multiple times every day is an experience I do not wish to continue.

There was a sweet spot of about 2 months over July and August in 2017 where my connection was perfect and I had no worries. I really hope that whatever happened to my connection and many others connection will be resolved soon and we can get back to that period of having no worries.

So all the best in resolving this and good luck!

**Einmimiria** · 01-19-2018 04:19 AM

Hello everyone,

As we proceed with our investigation, we ask that everyone run a traceroute to this IP address: 204.2.229.9. We would like to get results around the times the latency is being reported (7:30 PM PST / 8:30 PM MST / 10:30 PM EST).

To run a traceroute, press the windows key and “R” which will bring up the run command. Type “cmd” here and press “Enter” or the “OK” button. When the command prompt opens, type “tracert 204.2.229.9” and hit “Enter”. Copy and paste the results (or take a screen shot) here in this thread.

Thank you in advance for you cooperation and understanding in this matter. We hope we can use this information in our investigation to find a solution. Moving forward, we will continue to post updates as they are available.

**Ekko** · 01-19-2018 04:34 AM

Same kind of issue with ISP Free and ragnarok

PHP Code:


|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                          FREEBOX_SERVER -    0 |  186 |  186 |    0 |    0 |    4 |    0 |
|   oss65-1-88-126-217-254.fbx.proxad.net -    0 |  186 |  186 |    4 |    4 |   10 |    4 |
|                          213.228.34.126 -    0 |  186 |  186 |    5 |    5 |   14 |    5 |
|toulouse-9k-1-be1005.intf.routers.proxad.net -    0 |  186 |  186 |    7 |    9 |   21 |    8 |
|bzn-crs16-2-be1107.intf.routers.proxad.net -    0 |  186 |  186 |   18 |   20 |   24 |   19 |
| bzn-9k-7-be1000.intf.routers.proxad.net -    0 |  186 |  186 |   18 |   19 |   39 |   18 |
|                   No response from host -  100 |   37 |    0 |    0 |    0 |    0 |    0 |
|   ae-1-3107.edge5.Frankfurt1.Level3.net -   23 |   99 |   77 |   79 |   80 |   90 |   79 |
|                            212.162.4.98 -   12 |  127 |  112 |   80 |   85 |  102 |   89 |
|                            195.82.60.29 -   16 |  115 |   97 |    0 |   83 |  103 |   92 |
|                            195.82.61.14 -   13 |  124 |  109 |   79 |   81 |  105 |   80 |
|                           195.82.50.234 -   12 |  127 |  112 |   80 |   80 |   89 |   80 |
|                            195.82.50.47 -   18 |  111 |   92 |   79 |   80 |   89 |   80 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

**Callinon** · 01-19-2018 11:59 AM

Originally Posted by Einmimiria

Hello everyone,

As we proceed with our investigation, we ask that everyone run a traceroute to this IP address: 204.2.229.9. We would like to get results around the times the latency is being reported (7:30 PM PST / 8:30 PM MST / 10:30 PM EST).

To run a traceroute, press the windows key and “R” which will bring up the run command. Type “cmd” here and press “Enter” or the “OK” button. When the command prompt opens, type “tracert 204.2.229.9” and hit “Enter”. Copy and paste the results (or take a screen shot) here in this thread.

Thank you in advance for you cooperation and understanding in this matter. We hope we can use this information in our investigation to find a solution. Moving forward, we will continue to post updates as they are available.

Enjoy:

Code:

Tracing route to 204.2.229.9 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  RT-AC68U-5570 [192.168.1.1]
  2     9 ms     8 ms     9 ms  96.120.28.53
  3    18 ms     8 ms     9 ms  te-0-7-0-8-sur03.chicago301.il.chicago.comcast.net [68.85.180.45]
  4     8 ms    10 ms     8 ms  68.85.183.142
  5    12 ms    10 ms    10 ms  be-144-ar01.area4.il.chicago.comcast.net [162.151.45.69]
  6    10 ms    11 ms    12 ms  be-33491-cr02.350ecermak.il.ibone.comcast.net [68.86.91.165]
  7    11 ms    10 ms    16 ms  be-10577-pe03.350ecermak.il.ibone.comcast.net [68.86.86.2]
  8    16 ms    12 ms    10 ms  ae-26.a02.chcgil09.us.bb.gin.ntt.net [129.250.66.65]
  9   193 ms   185 ms   185 ms  ae-4.r08.chcgil09.us.bb.gin.ntt.net [129.250.4.157]
 10    27 ms    10 ms    20 ms  ae-0.r21.chcgil09.us.bb.gin.ntt.net [129.250.2.205]
 11   189 ms   182 ms   186 ms  ae-5.r22.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
 12   181 ms   186 ms     *     ae-40.r02.snjsca04.us.bb.gin.ntt.net [129.250.3.121]
 13   174 ms   181 ms   182 ms  ae-2.a00.snjsca04.us.bb.gin.ntt.net [129.250.3.58]
 14   187 ms   189 ms   187 ms  xe-0-0-42-1.a00.snjsca04.us.ce.gin.ntt.net [129.250.195.42]
 15   182 ms   188 ms   177 ms  204.2.229.242
 16   192 ms   188 ms   189 ms  204.2.229.9

**Kangaax** · 01-19-2018 12:04 PM

Code:

Tracing route to 204.2.229.9 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  192.168.10.1
  2     7 ms     6 ms     7 ms  10.71.56.1
  3     7 ms    11 ms     8 ms  ip68-4-11-168.oc.oc.cox.net [68.4.11.168]
  4     7 ms     6 ms     7 ms  ip68-4-11-8.oc.oc.cox.net [68.4.11.8]
  5    11 ms    10 ms    13 ms  68.1.1.63
  6    13 ms    13 ms    12 ms  ae-7.a00.lsanca20.us.bb.gin.ntt.net [129.250.194.165]
  7    18 ms    20 ms    18 ms  ae-3.r01.lsanca20.us.bb.gin.ntt.net [129.250.2.233]
  8    17 ms    16 ms    16 ms  ae-8.r23.lsanca07.us.bb.gin.ntt.net [129.250.6.48]
  9    32 ms    32 ms    32 ms  ae-12.r22.snjsca04.us.bb.gin.ntt.net [129.250.4.150]
 10    32 ms    33 ms    33 ms  ae-40.r02.snjsca04.us.bb.gin.ntt.net [129.250.3.121]
 11    34 ms    24 ms    27 ms  ae-2.a00.snjsca04.us.bb.gin.ntt.net [129.250.3.58]
 12    36 ms    34 ms    35 ms  xe-0-0-42-1.a00.snjsca04.us.ce.gin.ntt.net [129.250.195.42]
 13     *        *       21 ms  204.2.229.242
 14    36 ms    35 ms    36 ms  204.2.229.9

**Kerwin** · 01-19-2018 12:56 PM

Originally Posted by Einmimiria

Hello everyone,

As we proceed with our investigation, we ask that everyone run a traceroute to this IP address: 204.2.229.9. We would like to get results around the times the latency is being reported (7:30 PM PST / 8:30 PM MST / 10:30 PM EST).

To run a traceroute, press the windows key and “R” which will bring up the run command. Type “cmd” here and press “Enter” or the “OK” button. When the command prompt opens, type “tracert 204.2.229.9” and hit “Enter”. Copy and paste the results (or take a screen shot) here in this thread.

Thank you in advance for you cooperation and understanding in this matter. We hope we can use this information in our investigation to find a solution. Moving forward, we will continue to post updates as they are available.

Here's a fresh one from tonight around 8pm CST.

**Zetsumei_Tsunarashi** · 01-19-2018 01:02 PM

Not sure if this was posted already, but here's a reddit thread about this issue which may have some useful information for investigation.

https://www.reddit.com/r/ffxiv/comme...ng_south_east/

**Rbstr** · 01-19-2018 01:15 PM

Code:

Tracing route to 204.2.229.9 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2     9 ms     8 ms    10 ms  96.120.24.121
  3     8 ms     8 ms     8 ms  162.151.124.109
  4     8 ms     8 ms    10 ms  68.87.231.137
  5    15 ms    14 ms    14 ms  be-167-ar01.area4.il.chicago.comcast.net [162.151.144.101]
  6    21 ms    14 ms    27 ms  be-33491-cr02.350ecermak.il.ibone.comcast.net [68.86.91.165]
  7    12 ms    12 ms    13 ms  be-10577-pe03.350ecermak.il.ibone.comcast.net [68.86.86.2]
  8    35 ms    23 ms    25 ms  ae-26.a02.chcgil09.us.bb.gin.ntt.net [129.250.66.65]
  9   105 ms   103 ms   110 ms  ae-3.r07.chcgil09.us.bb.gin.ntt.net [129.250.5.111]
 10     *      129 ms    27 ms  ae-5.r21.chcgil09.us.bb.gin.ntt.net [129.250.4.213]
 11   166 ms   159 ms   159 ms  ae-5.r22.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
 12   176 ms   179 ms   162 ms  ae-19.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.27]
 13   178 ms     *      190 ms  ae-1.a00.snjsca04.us.bb.gin.ntt.net [129.250.2.228]
 14   188 ms   192 ms   195 ms  xe-0-0-42-1.a00.snjsca04.us.ce.gin.ntt.net [129.250.195.42]
 15   174 ms   166 ms     *     204.2.229.242
 16   171 ms   188 ms   178 ms  204.2.229.9

**Sereneisis** · 01-19-2018 03:22 PM

Location: Near Metro Atlanta
ISP: Comcast

Code:

10:10 PM EST 01/18/2018
  1     1 ms     1 ms     1 ms  [REDACTED]
  2     9 ms     9 ms    15 ms  [REDACTED]
  3    12 ms    12 ms    10 ms  [REDACTED] 
  4    12 ms    13 ms    10 ms  [REDACTED] 
  5    14 ms    12 ms    11 ms  ae-35-ar01.b0atlanta.ga.atlanta.comcast.net [162.151.89.153] 
  6    12 ms    12 ms    12 ms  be-7725-cr02.56marietta.ga.ibone.comcast.net [68.86.93.125] 
  7    10 ms    10 ms    10 ms  be-11486-pe03.56marietta.ga.ibone.comcast.net [68.86.85.254] 
  8    18 ms    19 ms    11 ms  50.242.151.58 
  9    12 ms    14 ms    12 ms  ae-1.r04.atlnga05.us.bb.gin.ntt.net [129.250.5.59] 
 10    11 ms    11 ms    17 ms  ae-4.r21.atlnga05.us.bb.gin.ntt.net [129.250.5.202] 
 11    31 ms    38 ms    35 ms  ae-6.r23.dllstx09.us.bb.gin.ntt.net [129.250.4.116] 
 12   144 ms   131 ms   129 ms  ae-8.r23.snjsca04.us.bb.gin.ntt.net [129.250.4.154] 
 13   114 ms   115 ms   121 ms  ae-45.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.175] 
 14   124 ms   117 ms   127 ms  ae-1.a00.snjsca04.us.bb.gin.ntt.net [129.250.2.228] 
 15   115 ms   127 ms   125 ms  xe-0-0-42-1.a00.snjsca04.us.ce.gin.ntt.net [129.250.195.42] 
 16   189 ms   189 ms     *     204.2.229.242 
 17   193 ms   199 ms   187 ms  204.2.229.9

Code:

10:11 PM EST 01/18/2018

  1     2 ms     1 ms     1 ms  [REDACTED]
  2     9 ms    10 ms     9 ms  [REDACTED] 
  3    11 ms    12 ms    11 ms  [REDACTED] 
  4    14 ms    15 ms    12 ms  [REDACTED]
  5    11 ms    14 ms    12 ms  ae-35-ar01.b0atlanta.ga.atlanta.comcast.net [162.151.89.153] 
  6    15 ms    13 ms    21 ms  be-7725-cr02.56marietta.ga.ibone.comcast.net [68.86.93.125] 
  7    12 ms    17 ms    27 ms  be-11486-pe03.56marietta.ga.ibone.comcast.net [68.86.85.254] 
  8    11 ms    19 ms    12 ms  50.242.151.58 
  9    14 ms    15 ms    10 ms  ae-1.r04.atlnga05.us.bb.gin.ntt.net [129.250.5.59] 
 10    10 ms    15 ms    13 ms  ae-4.r21.atlnga05.us.bb.gin.ntt.net [129.250.5.202] 
 11    34 ms    32 ms    33 ms  ae-6.r23.dllstx09.us.bb.gin.ntt.net [129.250.4.116] 
 12   119 ms   127 ms   134 ms  ae-8.r23.snjsca04.us.bb.gin.ntt.net [129.250.4.154] 
 13   128 ms   127 ms   119 ms  ae-45.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.175] 
 14   129 ms   123 ms   122 ms  ae-1.a00.snjsca04.us.bb.gin.ntt.net [129.250.2.228] 
 15   132 ms   131 ms   135 ms  xe-0-0-42-1.a00.snjsca04.us.ce.gin.ntt.net [129.250.195.42] 
 16     *      197 ms     *     204.2.229.242 
 17   175 ms   182 ms   161 ms  204.2.229.9

And a what I think is "normal" latency

Code:

10:20PM EST 01/18/2018

  1     1 ms     1 ms     2 ms  [REDACTED]
  2     9 ms    10 ms     9 ms  [REDACTED] 
  3    12 ms    18 ms    12 ms  [REDACTED] 
  4    13 ms    19 ms    11 ms  [REDACTED] 
  5    10 ms    11 ms    10 ms  ae-35-ar01.b0atlanta.ga.atlanta.comcast.net [162.151.89.153] 
  6    10 ms    14 ms    11 ms  be-7725-cr02.56marietta.ga.ibone.comcast.net [68.86.93.125] 
  7    11 ms    11 ms    10 ms  be-11486-pe03.56marietta.ga.ibone.comcast.net [68.86.85.254] 
  8    21 ms    11 ms    14 ms  50.242.151.58 
  9    12 ms    14 ms    11 ms  ae-1.r04.atlnga05.us.bb.gin.ntt.net [129.250.5.59] 
 10    23 ms    23 ms    19 ms  ae-4.r21.atlnga05.us.bb.gin.ntt.net [129.250.5.202] 
 11    31 ms    31 ms    39 ms  ae-6.r23.dllstx09.us.bb.gin.ntt.net [129.250.4.116] 
 12    77 ms    76 ms    84 ms  ae-8.r23.snjsca04.us.bb.gin.ntt.net [129.250.4.154] 
 13    78 ms    88 ms    84 ms  ae-45.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.175] 
 14    82 ms    77 ms    78 ms  ae-1.a00.snjsca04.us.bb.gin.ntt.net [129.250.2.228] 
 15    85 ms    81 ms    80 ms  xe-0-0-42-1.a00.snjsca04.us.ce.gin.ntt.net [129.250.195.42] 
 16    86 ms    80 ms    77 ms  204.2.229.242 
 17    80 ms    93 ms    86 ms  204.2.229.9

Code:

~01:00 AM 01/19/2018

  1     1 ms     1 ms     1 ms  [REDACTED]
  2    11 ms    10 ms    16 ms  [REDACTED]
  3    12 ms    13 ms    10 ms  [REDACTED]
  4    18 ms    44 ms    41 ms  [REDACTED]
  5    30 ms    30 ms    29 ms  be-7725-cr02.350ecermak.il.ibone.comcast.net [68.86.92.237] 
  6    28 ms    28 ms    28 ms  be-10577-pe03.350ecermak.il.ibone.comcast.net [68.86.86.2] 
  7    32 ms    30 ms    30 ms  ae-26.a02.chcgil09.us.bb.gin.ntt.net [129.250.66.65] 
  8    82 ms    80 ms    88 ms  ae-4.r08.chcgil09.us.bb.gin.ntt.net [129.250.4.157] 
  9    31 ms    30 ms    28 ms  ae-0.r21.chcgil09.us.bb.gin.ntt.net [129.250.2.205] 
 10    81 ms    80 ms    80 ms  ae-5.r22.snjsca04.us.bb.gin.ntt.net [129.250.5.17] 
 11    81 ms    81 ms    80 ms  ae-40.r02.snjsca04.us.bb.gin.ntt.net [129.250.3.121] 
 12    90 ms    80 ms    95 ms  ae-2.a00.snjsca04.us.bb.gin.ntt.net [129.250.3.58] 
 13    94 ms    85 ms    84 ms  xe-0-0-42-1.a00.snjsca04.us.ce.gin.ntt.net [129.250.195.42] 
 14    82 ms    83 ms    83 ms  204.2.229.242 
 15    84 ms    84 ms    82 ms  204.2.229.9

Thread: Regarding Reports on Recent Connection Problems with the NA Data Center

Thread Tools

Search Thread

Display

Just an update on my situation.

Same kind of issue with ISP Free and ragnarok