High Packet Loss and Disconnects

[Bluejay]

Starting this afternoon I began to receive high packet loss and frequent server disconnects. The game played fine until today. As it is the game in unplayable. I have tried checking my network connection to other sites and no other service I use is having this problem. It's only when connecting to the FF14 server that I have this issue.

My trace route

Tracing route to 184.107.107.176 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms xxxxxxxxxx [xxx.xxx.xx.x]
2 2 ms 3 ms 5 ms L100.DLLSTX-VFTTP-53.verizon-gni.net [173.71.42.
1]
3 8 ms 6 ms 3 ms G0-9-3-0.DLLSTX-LCR-22.verizon-gni.net [100.41.1
97.230]
4 * * * Request timed out.
5 4 ms 4 ms 4 ms 0.ae2.BR2.DFW13.ALTER.NET [140.222.225.53]
6 5 ms 4 ms 4 ms ix-20-0.tcore1.DT8-Dallas.as6453.net [66.110.56.
17]
7 * 61 ms * 64.86.78.5
8 61 ms 60 ms 62 ms if-22-2.tcore2.CT8-Chicago.as6453.net [64.86.79.
1]
9 62 ms 60 ms 64 ms if-3-2.tcore1.W6C-Montreal.as6453.net [66.198.96
.45]
10 63 ms 61 ms 65 ms 66.198.96.58
11 64 ms * 60 ms te7-3.dr9.mtl.iweb.com [67.205.127.214]
12 62 ms 61 ms 61 ms 72.55.128.44
13 64 ms 65 ms 66 ms 184.107.107.176

Pinging 184.107.107.176 with 32 bytes of data:
Reply from 184.107.107.176: bytes=32 time=68ms TTL=53
Request timed out.
Reply from 184.107.107.176: bytes=32 time=63ms TTL=53
Reply from 184.107.107.176: bytes=32 time=62ms TTL=53
Request timed out.
Reply from 184.107.107.176: bytes=32 time=64ms TTL=53
....
Ping statistics for 184.107.107.176:
Packets: Sent = 100, Received = 88, Lost = 12 (12% loss),
Approximate round trip times in milli-seconds:
Minimum = 62ms, Maximum = 68ms, Average = 63ms

[iKentucky]

Same thing happened to me today. Constant time outs and fast forwarding in dungeons. It was perfectly fine until today. Streams aren't pausing or buffering, skype calls are all still on, everything on my net is fine. It's just the game.

[Bluejay]

I have tested 5 other MMO services and I have 0% packet loss to all of them. Square's server is the only one I am having any issue with.

[matadoor]

me too my tracert was 58ms last 5 hops each added 10ms.

was kicked out of keeper of lake, after first boss.

[MrMaggot]

Having the same problem. No issues up until today. From what I'm gathering seems to be affecting select people. Friend of mine has been having issues to but FC members and brother have said they not experiencing issues. Also, launcher and website seem to be running tremendously slow.

[Strifex]

I'm having the same issue on Behemoth Server. My ISP is Verizon FIOS. I checked with my ISP and the packet loss isn't occurring on their end It has to be SE's servers choking.

[Kenji1134]

On Cactuar I have had no latency issues on Fri, Sat, or Sun. Since Monday I have had latency spikes of 10-15 seconds. Repeated R0s, and several disconnects.
I have Verizon Fios, and have no issues connecting to other games or websites.
So yeah, something happened between Sunday and Monday. Either the servers need a couple reboots, or there is some unexpected congestion on the line going to SE's servers.

Trace Results

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| Wireless_Broadband_Router.home - 0 | 874 | 874 | 2 | 2 | 4 | 3 |
|lo0-100.BSTNMA-VFTTP-302.verizon-gni.net - 0 | 874 | 874 | 6 | 10 | 75 | 9 |
| T1-3-0-8.BSTNMA-LCR-22.verizon-gni.net - 0 | 874 | 874 | 8 | 13 | 18 | 14 |
| ae10-0.BOS-BB-RTR2.verizon-gni.net - 1 | 871 | 870 | 8 | 26 | 132 | 9 |
|xe-9-0-2-0.NY325-BB-RTR2.verizon-gni.net - 0 | 874 | 874 | 18 | 26 | 84 | 21 |
| 0.ae7.BR1.NYC1.ALTER.NET - 0 | 874 | 874 | 16 | 21 | 77 | 19 |
| No response from host - 100 | 175 | 0 | 0 | 0 | 0 | 0 |
| ae-11-11.car2.Montreal2.Level3.net - 0 | 874 | 874 | 43 | 69 | 276 | 48 |
| ae-11-11.car2.Montreal2.Level3.net - 1 | 871 | 870 | 43 | 69 | 333 | 46 |
| ORMUCO-COMM.car2.Montreal2.Level3.net - 0 | 874 | 874 | 38 | 45 | 54 | 41 |
| 192.34.76.10 - 9 | 646 | 588 | 57 | 62 | 114 | 62 |
| 199.91.189.242 - 11 | 623 | 560 | 56 | 60 | 101 | 57 |
| 199.91.189.23 - 13 | 591 | 520 | 51 | 54 | 59 | 57 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

In other words, the last 3 hops on my trace to the Cactuar server are seeing 9-13% packet loss.
This is generally not enough to force a disconnection, but it does add up to a lot of very large lag spikes.

[Kassi]

I am having the exact same issue. I am on the East Coast and on Verizon FIOS as well. Only thing having the issue with FFXIV.

[Raist]

Tracing route to 184.107.107.176 over a maximum of 30 hops

Invalid IP address... that is a webserver on the other side of town, managed by a different company with different ASN and such (can impact routing decisions).

If you can't/don't want to lookup the IP your client is actually using, at least test against the lobby servers (neolobby02, neolobby04, neolobby06 are in Canada--odd numbered ones are in Japan). For Aether it is neolobby02.ffxiv.com. Notice when you run the trace it starts with 199, and the name near the end is Ormuco and not i-web.

Otherwise... it looks like there are issues coming through TATA's segments (as6453) coming across Texas on the way to Montreal. If you still take that route and show the bad lag spikes and intermittent time outs, then you need to get your ISP's Tier3 team involved. Your ISP's routing policies are putting you on that congested path.

[Raist]

On Cactuar I have had no latency issues on Fri, Sat, or Sun. Since Monday I have had latency spikes of 10-15 seconds. Repeated R0s, and several disconnects.
I have Verizon Fios, and have no issues connecting to other games or websites.
So yeah, something happened between Sunday and Monday. Either the servers need a couple reboots, or there is some unexpected congestion on the line going to SE's servers.

Trace Results

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| Wireless_Broadband_Router.home - 0 | 874 | 874 | 2 | 2 | 4 | 3 |
|lo0-100.BSTNMA-VFTTP-302.verizon-gni.net - 0 | 874 | 874 | 6 | 10 | 75 | 9 |
| T1-3-0-8.BSTNMA-LCR-22.verizon-gni.net - 0 | 874 | 874 | 8 | 13 | 18 | 14 |
| ae10-0.BOS-BB-RTR2.verizon-gni.net - 1 | 871 | 870 | 8 | 26 | 132 | 9 |
|xe-9-0-2-0.NY325-BB-RTR2.verizon-gni.net - 0 | 874 | 874 | 18 | 26 | 84 | 21 |
| 0.ae7.BR1.NYC1.ALTER.NET - 0 | 874 | 874 | 16 | 21 | 77 | 19 |
| No response from host - 100 | 175 | 0 | 0 | 0 | 0 | 0 |
| ae-11-11.car2.Montreal2.Level3.net - 0 | 874 | 874 | 43 | 69 | 276 | 48 |
| ae-11-11.car2.Montreal2.Level3.net - 1 | 871 | 870 | 43 | 69 | 333 | 46 |
| ORMUCO-COMM.car2.Montreal2.Level3.net - 0 | 874 | 874 | 38 | 45 | 54 | 41 |
| 192.34.76.10 - 9 | 646 | 588 | 57 | 62 | 114 | 62 |
| 199.91.189.242 - 11 | 623 | 560 | 56 | 60 | 101 | 57 |
| 199.91.189.23 - 13 | 591 | 520 | 51 | 54 | 59 | 57 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

In other words, the last 3 hops on my trace to the Cactuar server are seeing 9-13% packet loss.
This is generally not enough to force a disconnection, but it does add up to a lot of very large lag spikes.

There are issues early on in your Verizon segments that may be compounding with other issues further down your route when you are handed off to Level3. There is way too much jitter there, indicating things like signalling issues or elevated congestion that needs to be addressed (part of it could be due to your wireless, but it gets really ugly deeper in...probably congestion or other issues at those locations).

Again... need to get this data to your ISP's Tier3 support for further analysis. We've seen these issues going on for years across various services and ISP's. Just not enough people put the pressure on them to fix it and it just keeps rearing it's ugly head. Happening more and more now that we rely on our internet for so much more than we ever did before. And it has the potential to just get worse....