Regarding Reports on Recent Connection Problems with the NA Data Center

[SaltyNuggy]

Adding my traceroute as well, latency doubles on NTT nodes (highlighted).

Here is traceroute:

  3   25ms     0/ 100 =  0%     0/ 100 =  0%  tge7-4.gahgohcv01h.midwest.rr.com [24.164.98.1] 
                                0/ 100 =  0%   |
  4   16ms     0/ 100 =  0%     0/ 100 =  0%  be24.mcdnohbg01r.midwest.rr.com [24.33.103.96] 
                                0/ 100 =  0%   |
  5   21ms     0/ 100 =  0%     0/ 100 =  0%  be14.pltsohae01r.midwest.rr.com [65.29.1.87] 
                                0/ 100 =  0%   |
  6   25ms     0/ 100 =  0%     0/ 100 =  0%  be25.clmkohpe01r.midwest.rr.com [65.29.1.28] 
                                0/ 100 =  0%   |
  7   35ms     0/ 100 =  0%     0/ 100 =  0%  107.14.17.252 
                                0/ 100 =  0%   |
  8   36ms     0/ 100 =  0%     0/ 100 =  0%  bu-ether11.chcgildt87w-bcr00.tbone.rr.com [66.109.6.20] 
                                0/ 100 =  0%   |
  9   31ms     0/ 100 =  0%     0/ 100 =  0%  0.ae4.pr1.chi10.tbone.rr.com [66.109.1.66] 
                                0/ 100 =  0%   |
 10   32ms     0/ 100 =  0%     0/ 100 =  0%  ix-ae-27-0.tcore2.CT8-Chicago.as6453.net [64.86.79.97] 
                                0/ 100 =  0%   |
 11   32ms     0/ 100 =  0%     0/ 100 =  0%  if-ae-22-2.tcore1.CT8-Chicago.as6453.net [64.86.79.2] 
                                0/ 100 =  0%   |
 12   34ms     0/ 100 =  0%     0/ 100 =  0%  64.86.78.18 
                                0/ 100 =  0%   |
 13   32ms     0/ 100 =  0%     0/ 100 =  0%  ae-21.r08.chcgil09.us.bb.gin.ntt.net [129.250.3.158] 
                                0/ 100 =  0%   |
 14   33ms     0/ 100 =  0%     0/ 100 =  0%  ae-0.r21.chcgil09.us.bb.gin.ntt.net [129.250.2.205] 
                                0/ 100 =  0%   |
 15   89ms     0/ 100 =  0%     0/ 100 =  0%  ae-5.r22.snjsca04.us.bb.gin.ntt.net [129.250.5.17] 
                                0/ 100 =  0%   |
 16   81ms     0/ 100 =  0%     0/ 100 =  0%  ae-40.r02.snjsca04.us.bb.gin.ntt.net [129.250.3.121] 
                                0/ 100 =  0%   |
 17   94ms     0/ 100 =  0%     0/ 100 =  0%  ae-3.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.11] 
                                0/ 100 =  0%   |
 18   95ms     0/ 100 =  0%     0/ 100 =  0%  xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46] 
                                0/ 100 =  0%   |
 19   94ms     0/ 100 =  0%     0/ 100 =  0%  204.2.229.234 
                                0/ 100 =  0%   |
 20   93ms     0/ 100 =  0%     0/ 100 =  0%  204.2.229.111

[Frent]

About a week ago, I logged on to FFXIV for the first time in a few months. I had upgraded to a new router; had no issues logging on or playing. We got a house and spent all night furnishing it. Fast forward to this past weekend and I started getting random 90006 disconnects every few minutes. Couldn't play; figured DDoS and quit for the night.

Now it's a couple of days later and I'm getting the same problems. I was able to log in and do Ananta dailies for about 5 minutes before getting kicked. Went to the forums; set up the proper port forwarding; came back and now it's 90006-ing me about 30 seconds after I log in, each time. Even after I disabled the port forwarding I did, nothing changed.

Not sure if it's a coincidence, but this has happened after 8 p.m. CST each night. After further testing, this happens anytime I'm logged in, day or night. I'm in Arkansas in the U.S., my ISP is Comcast, and I am including a traceroute I attempted to run -- not sure if I did it right. I play on PC.



I've played more than 3,500 hours of FF over several years and I've never had this issue before. I know the new router seems like a red flag, but I've had zero issues playing any other game on PC or PS4, and I ran FFXIV perfectly the same night I replaced the router.