HUGE CONNECTION PROBLEM

[VoltaAsura]

I am now experiencing lots of lag and 90ks ingame, and it is most definitely not my connection. I'm stuck constant 90k atm because an S rank was called in Outer La Noscea, and immediately after I loaded in the zone, I had lag. Everyone else in the area had red circles above their heads too =/ .

[ProfVukasin]

Still having the same issues I have been having since the 2.4 patch. I had zero issues prior to this patch. And the issue only really begins to creep up when I am trying to FATE grind or if another FATE train happens to roll by. I have to actively check to make sure there are no FATE parties in the area. My only hope now of leveling up my ninja is levequests and instance grinding when someone in my FC is up for it.

[Callinon]

Was having this issue before 2.4, but it's WAY worse now. I'm getting booted every hour or so... which is a problem when melee dps queues are over an hour long and getting d/c'd removes you from the queue.

For the record, this is not just in heavily populated areas. I've sat in my inn room or my FC house all by myself. Doesn't seem to matter where I am.

[JohnPoru]

Same here. Im on ps4 and its lagging like crazy. I was playing fine yesterday, but after the Hotfixes this morning the lag just went nuts. Summoning my mount has a 20 sec delay before it pops out. I just read somewhere that after the patches/updates they switch up something and you need to wait till your ISP refreshes or syncs again with the servers.

[Aiph]

Having really bad lag and packet and connection loss since 2.38 but has increased in severity lately.

Here's a ping test of the JP data center

Ping statistics for 124.150.157.158:
Packets: Sent = 50, Received = 30, Lost = 20 (40% loss),
Approximate round trip times in milli-seconds:
Minimum = 174ms, Maximum = 284ms, Average = 203ms

Route trace

Tracing route to 124.150.157.158 over a maximum of 30 hops

1 8 ms 9 ms 9 ms 10.126.152.1
2 18 ms 11 ms 11 ms 209.148.243.45
3 14 ms 11 ms 11 ms 69.63.248.205
4 15 ms 13 ms 13 ms ae1_2150-bdr04-tor.teksavvy.com [69.196.136.164]

5 11 ms 20 ms 9 ms gw-he.torontointernetxchange.net [206.108.34.112
]
6 80 ms 23 ms 24 ms 100ge13-1.core1.chi1.he.net [184.105.80.5]
7 72 ms 74 ms 75 ms 10ge11-4.core1.pao1.he.net [184.105.222.173]
8 73 ms 74 ms 75 ms 10ge3-1.core1.sjc2.he.net [72.52.92.70]
9 75 ms 73 ms 77 ms pacnet.10gigabitethernet2-2.core1.sjc2.he.net [2
16.218.192.234]
10 74 ms 76 ms 74 ms gi2-0-0.gw1.sjc1.asianetcom.net [202.147.50.210]

11 193 ms 198 ms 184 ms po4-0-0.cr1.nrt1.asianetcom.net [202.147.0.33]
12 198 ms 187 ms 186 ms squareco.asianetcom.net [203.192.149.210]
13 175 ms 212 ms 177 ms 61.195.56.129
14 173 ms 175 ms 172 ms 219.117.144.70
15 176 ms 177 ms 172 ms 219.117.144.49
16 186 ms 186 ms 188 ms 219.117.144.29
17 192 ms 194 ms 194 ms 219.117.147.186
18 173 ms 196 ms 197 ms 124.150.157.158

Trace complete.

Funny thing looking at the traceroute. Packets from NA to JP take ony 74 ms but within JP, there's a pass off that more than doubles that time at asiannetcom which is SE's provider according to the above.

[Raist]

got some signs of congestion coming in trying to get from Toronto through Southern California. Latency spiked to almost 4x cutting through that one hop across Hurricane Electric's line, right around where you are getting exchanged to the transcontinental undersea line to take you over to Asia. The source of the packet loss may be occurring around that Southern Cali area--it's been a hotbed of high congestion and losses for a long time for multiple providers.

TWC seems to now have a direct peering arrangement with PACNET out of LA, so I'm not getting any spikes like that over there atm (my problems are still focused around Hilton Head and Columbia here in SC, not to mention I ran the tests on my wifi from the back of the house) But, it's not uncommon to see the LA/San Jose/Palo Alto areas throw up on themselves under heavy loads, so I might see something skewed if I checked during prime-time.

Tracing route to 124.150.157.158 over a maximum of 30 hops

  1     2 ms    <1 ms     1 ms  LPTSRV [10.10.100.1]
  2    33 ms    21 ms    16 ms  cpe-066-026-112-001.sc.res.rr.com [66.26.112.1]
  3   100 ms    18 ms    26 ms  cpe-024-031-198-005.sc.res.rr.com [24.31.198.5]
  4    13 ms    12 ms    16 ms  clmasoutheastmyr-rtr2.sc.rr.com [24.31.196.210]
  5    28 ms    27 ms    28 ms  be33.drhmncev01r.southeast.rr.com [24.93.64.180]
  6    31 ms    29 ms    31 ms  107.14.19.44
  7    98 ms    97 ms    99 ms  107.14.17.179
  8    98 ms    98 ms    95 ms  ae-4-0.cr0.lax30.tbone.rr.com [66.109.6.2]
  9    93 ms    95 ms    97 ms  ae-1-0.pr0.lax10.tbone.rr.com [66.109.6.131]
 10    96 ms    97 ms    95 ms  66.109.10.194
 11   203 ms   203 ms   204 ms  ip-202-147-0-52.asianetcom.net [202.147.0.52]
 12   203 ms   201 ms   202 ms  gi1-0-0.gw1.nrt5.asianetcom.net [202.147.0.178]
 13   200 ms   203 ms   202 ms  squareco.asianetcom.net [203.192.149.210]
 14   206 ms   201 ms   204 ms  61.195.56.129
 15   202 ms   199 ms   203 ms  219.117.144.70
 16   194 ms   193 ms   197 ms  219.117.144.57
 17   198 ms   197 ms   197 ms  219.117.144.41
 18   195 ms   197 ms   194 ms  219.117.147.190
 19   213 ms   213 ms   213 ms  124.150.157.158

Trace complete.

Edit:
Yeah... poking around Hurricane's looking glass, things look pretty consistent on the Tokyo side of things, but coming out of Fremont the response times are showing elevated jitter.

core1.fmt2.he.net> traceroute 124.150.157.158 Target 	124.150.157.158
Hop Start 	1
Hop End 	30
Hop 	Packet 1 	Packet 2 	Packet 3 	Hostname
1 	0.232 ms 	0.279 ms 	0.314 ms 	ge5-19.core1.fmt2.he.net (64.71.148.109)
2 	0.621 ms 	0.614 ms 	0.635 ms 	10ge1-1.core1.sjc2.he.net (72.52.92.74)
3 	0.999 ms 	0.994 ms 	1.005 ms 	pacnet.10gigabitethernet2-2.core1.sjc2.he.net (216.218.192.234)
4 	0.726 ms 	103.159 ms 	103.156 ms 	gi2-0-0.gw1.sjc1.asianetcom.net (202.147.50.210) gi9-0-0.cr2.nrt1.asianetcom.net (202.147.50.134)
5 	103.669 ms 	103.674 ms 	114.631 ms 	ge-2-1-0-0.gw3.nrt5.asianetcom.net (202.147.0.182) po4-0-0.cr1.nrt1.asianetcom.net (202.147.0.33)
6 	114.005 ms 	113.948 ms 	113.983 ms 	gi6-0-0.gw1.nrt5.asianetcom.net (202.147.0.45)
7 	114.060 ms 	114.135 ms 	114.611 ms 	squareco.asianetcom.net (203.192.149.210) 61.195.56.129
8 	114.108 ms 	114.112 ms 	107.365 ms 	61.195.56.129 219.117.144.70
9 	106.604 ms 	106.584 ms 	106.695 ms 	219.117.144.49 219.117.144.70
10 	107.482 ms 	108.005 ms 	107.275 ms 	219.117.144.41 219.117.144.29 219.117.144.41
11 	107.657 ms 	107.650 ms 	107.673 ms 	219.117.144.29 219.117.147.190


core1.tyo1.he.net> traceroute 124.150.157.158 Target 	124.150.157.158
Hop Start 	1
Hop End 	30
Hop 	Packet 1 	Packet 2 	Packet 3 	Hostname
1 	6.213 ms 	6.238 ms 	6.255 ms 	ge2-3.core1.tyo1.he.net (74.82.46.5)
2 	1.141 ms 	1.022 ms 	1.054 ms 	as10026-2.ix.jpix.ad.jp (210.171.224.84)
3 	0.629 ms 	0.623 ms 	0.600 ms 	gi3-0-0.gw1.nrt5.asianetcom.net (202.147.1.186)
4 	0.673 ms 	0.656 ms 	0.637 ms 	squareco.asianetcom.net (203.192.149.210)
5 	0.660 ms 	0.745 ms 	0.719 ms 	61.195.56.129
6 	99.787 ms 	99.589 ms 	99.866 ms 	219.117.144.70
7 	100.331 ms 	100.388 ms 	100.375 ms 	219.117.144.57
8 	100.359 ms 	98.766 ms 	100.492 ms 	219.117.144.29 219.117.144.41 219.117.144.29
9 	98.776 ms 	98.849 ms 	98.949 ms 	219.117.147.182 219.117.147.190

[ihatevnecks]

Started getting the same 90k disconnects this morning running FATEs in Costa Del Sol area on Balmung, connected wired via PC.

It's only happening on one character, and it's not connection lag as I can stream Twitch in the background without any interruption while I'm getting repeatedly booted from the game. Sometimes I'll get the 10-15 seconds of lag, and then either disconnected with 90k or it catches up, but other times I've just been immediately disconnected while riding between FATEs.

[Cronolith]

I've been having connection issues since yesterday. Frequent 90ks and a few 10105s; also dropped packets to the NA data center. I've power cycled my modem and router; but I also have run a ping and traceroute to the data center when I am experiencing connection issues. It appeared to be the last few hops to the data center as it had latency spikes (400ms+).

To be clear, I am located in North America and connecting to the North America data center.

[Rigus]

When is this going to be over with, I can't do anything!

[MetalVictini]

I can confirm that I've been having issues today. I have had lag and 90ks all over the place.
I'm on PS4 too.