Reporting Latency Related Issue (NA Data Center)

[Kowru]

Name of your Internet Service Provider (ISP): Comcast
Ticket or reference number from your ISP: N/A
State/Country: Colorado/United States
Date/Time (When did the issue start happening, at what specific times does this issue arise, if any.): Began December 2015 to present at around 18:00-19:00 till 23:00
Frequency (How often does the issue occur?): Every day
Content (Which content were you playing in-game when the issue occurred?): Everything. Dungeons, in towns, in moghouse, etc.
Which in-game World were you playing on when the issue occurred?: Primal datacenter, Hyperion server.

1 <1 ms 1 ms <1 ms 10.0.0.1
2 17 ms 10 ms 10 ms 96.120.13.137
3 11 ms 12 ms 8 ms xe-9-0-0-sur02.fortcollins.co.denver.comcast.net [162.151.38.137]
4 9 ms 16 ms 8 ms ae-10-sur03.fortcollins.co.denver.comcast.net [68.86.103.105]
5 13 ms 18 ms 16 ms ae-33-ar01.denver.co.denver.comcast.net [68.86.103.37]
6 16 ms 13 ms 16 ms 4.68.63.165
7 58 ms 57 ms 65 ms ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]
8 57 ms 59 ms 58 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.74]
9 85 ms 70 ms 70 ms 192.34.76.10
10 71 ms 71 ms 69 ms 199.91.189.242

[Jaeger]

Something appears to have been fixed or route changed. My route is Colorado to Balmung.

I used to have packet loss at ORMUCO and a couple hops after that as well, every single night NA primetime. Have seen a couple other post this as well. Just wanted to say it has been clean for the past 5 nights for me. I've never had a single NA primetime night where there wasn't extremely bad packet loss.

[nsalex91]

Name of your Internet Service Provider (ISP): Charter
Ticket or reference number from your ISP: None, but I did report it to them.
State/Country: I'm in Wisconsin(USA) but the issue seems to be with one of their Michigan(USA) centers and level3s montreal2 center.
Date/Time (When did the issue start happening, at what specific times does this issue arise, if any.): Started about a week ago and continue till now(at least)
Frequency (How often does the issue occur?): Constant I'll just get random packet loss because of it.
Content (Which content were you playing in-game when the issue occurred?): Any but it's most annoying in stuff like trials where my cooldowns and rotations fall apart because of it.
Which in-game World were you playing on when the issue occurred? Hyperion but considering the issue seems to start between the data centers I don't think it would matter which one.
Traceroute records: From my PC

Tracing route to 199.91.189.57 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1]
2 6 ms 6 ms 6 ms 10.141.24.1
3 8 ms 6 ms 8 ms dtr03jnvlwi-tge-0-6-0-5.jnvl.wi.charter.com [96.34.20.214]
4 8 ms 19 ms 8 ms crr01ftbgwi-tge-0-3-0-7.ftbg.wi.charter.com [96.34.17.28]
5 9 ms 10 ms 8 ms csw02stptwi-gbe-1-3.stpt.wi.charter.com [96.34.24.2]
6 16 ms 14 ms 15 ms crr01stptwi-tge-0-5-0-3.stpt.wi.charter.com [96.34.24.224]
7 18 ms 18 ms 19 ms crr02sgnwmi-tge-0-0-0-4.sgnw.mi.charter.com [96.34.2.153]
8 * * * Request timed out.
9 41 ms 42 ms 41 ms ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]
10 41 ms 40 ms 42 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.74]
11 41 ms 43 ms 42 ms 192.34.76.10
12 42 ms 42 ms 41 ms 199.91.189.242
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

From my router where you can see the issue is actually probably in the Chicago level3 datacenter.

traceroute to 199.91.189.57 (199.91.189.57), 30 hops max, 38 byte packets
1 10.141.24.1 (10.141.24.1) 9.036 ms 17.940 ms 7.498 ms
2 dtr03jnvlwi-tge-0-6-0-5.jnvl.wi.charter.com (96.34.20.214) 7.830 ms 7.115 ms 8.069 ms
3 crr01ftbgwi-tge-0-3-0-7.ftbg.wi.charter.com (96.34.17.28) 12.935 ms crr01ftbgwi-bue-5.ftbg.wi.charter.com (96.34.16.3) 10.642 ms dtr04jnvlwi-bue-1.jnvl.wi.charter.com (96.34.18.159) 9.327 ms
4 csw02stptwi-gbe-1-3.stpt.wi.charter.com (96.34.24.2) 10.055 ms crr01stptwi-tge-0-5-0-3.stpt.wi.charter.com (96.34.24.224) 20.025 ms crr01onlswi-tge-0-0-0-3.onls.wi.charter.com (96.34.17.2) 9.576 ms
5 crr01stptwi-tge-0-5-0-3.stpt.wi.charter.com (96.34.24.224) 14.879 ms crr02sgnwmi-tge-0-0-0-4.sgnw.mi.charter.com (96.34.2.153) 18.582 ms crr01stptwi-tge-0-5-0-3.stpt.wi.charter.com (96.34.24.224) 18.204 ms
6 crr02sgnwmi-tge-0-0-0-4.sgnw.mi.charter.com (96.34.2.153) 21.602 ms * 18.493 ms
7 lag-112.ear2.Chicago2.Level3.net (4.30.175.85) 1265.818 ms ae-10-10.car2.Montreal2.Level3.net (4.69.153.86) 162.243 ms *
8 ae-10-10.car2.Montreal2.Level3.net (4.69.153.86) 52.405 ms ORMUCO-COMM.car2.Montreal2.Level3.net (4.59.178.74) 40.478 ms ae-10-10.car2.Montreal2.Level3.net (4.69.153.86) 44.335 ms
9 ORMUCO-COMM.car2.Montreal2.Level3.net (4.59.178.74) 41. * *
14 * * *
15 * * *
1611 * * *
12 *

rest are just timed out I assume.

[GTRicky]

Name of your Internet Service Provider (ISP): Century Link
Ticket or reference number from your ISP: None.
State/Country: PHX, AZ
Date/Time (When did the issue start happening, at what specific times does this issue arise, if any.): This last Sunday.
Frequency (How often does the issue occur?): Massive latency and rubberbanding nonstop. From start to end.
Content (Which content were you playing in-game when the issue occurred?): All. Chocobo races, quests, battles, everything.
Which in-game World were you playing on when the issue occurred? Behomoth
Traceroute records:

C:\Users\pppppp>tracert -d 184.107.107.176

Tracing route to 184.107.107.176 over a maximum of 30 hops

1 1 ms 2 ms 4 ms 192.168.1.1
2 3 ms 18 ms 3 ms 192.168.0.1
3 24 ms 29 ms 29 ms 67.40.227.66
4 * 22 ms 29 ms 75.160.238.9
5 * 42 ms 39 ms 67.14.102.110
6 47 ms 69 ms 59 ms 154.54.11.185
7 43 ms 47 ms 50 ms 154.54.41.57
8 60 ms 68 ms 60 ms 154.54.5.65
9 88 ms 92 ms 90 ms 154.54.28.69
10 89 ms 97 ms 94 ms 154.54.7.157
11 95 ms 102 ms 92 ms 154.54.40.105
12 109 ms 109 ms 109 ms 154.54.47.18
13 106 ms 109 ms 109 ms 38.88.194.82
14 104 ms 99 ms 99 ms 67.205.127.117
15 105 ms 101 ms 100 ms 67.205.127.214
16 99 ms 97 ms 107 ms 174.142.115.218
17 104 ms 109 ms 108 ms 184.107.107.176

Trace complete.

C:\Users\pppppp>tracert -d 199.91.189.139

Tracing route to 199.91.189.139 over a maximum of 30 hops

1 1 ms 1 ms 3 ms 192.168.1.1
2 17 ms 9 ms 19 ms 192.168.0.1
3 58 ms 29 ms 29 ms 67.40.227.66
4 27 ms 25 ms 24 ms 75.160.238.9
5 67 ms 34 ms 49 ms 67.14.102.110
6 38 ms 39 ms 39 ms 63.146.27.34
7 108 ms 109 ms 109 ms 4.69.153.86
8 108 ms 109 ms 110 ms 4.59.178.74
9 108 ms 99 ms 99 ms 192.34.76.10
10 98 ms 99 ms 108 ms 199.91.189.242
11 98 ms 109 ms 109 ms 199.91.189.139

Trace complete.

The 100ms latency is something I've played with before and it was never this bad for rubberbanding. I have attempted isolating my own network and ISP. I have tried new network gear (modem, router, switches) and done FTP uploads to datacenters in Utah and Canada (west coast) with no more than 40-80ms of latency. My ISP and pathing outside of FFXIV is fine. But going to the FFXIV servers I get the 100ms hops. Did someone mess with the routing tables?

[ZephyrusVenti]

Name of your Internet Service Provider (ISP): Comcast
Ticket or reference number from your ISP.: None. They insist it is all on XIV's end.
State/Country: MA/USA
Date/Time: Starts 4:30pm -> Ends 2:00am
Frequency: Everyday, every few minutes within time period above.
Content: All content
Which in-game World were you playing on when the issue occurred? Coeurl- Aether Datacenter
Traceroute records:

Tracing route to 199.91.189.27 over a maximum of 30 hops

1 2 ms <1 ms <1 ms router.asus.com [192.168.1.1]
2 8 ms 17 ms 11 ms 96.120.65.253
3 9 ms 9 ms 13 ms 68.85.184.85
4 15 ms 14 ms 18 ms be-135-ar01.needham.ma.boston.comcast.net [68.85
.37.141]
5 21 ms 11 ms 12 ms 4.68.71.217
6 * 134 ms 134 ms ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]

7 132 ms 133 ms * ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.
74]
8 143 ms 136 ms 134 ms 192.34.76.10
9 134 ms 134 ms 139 ms 199.91.189.242
10 133 ms 136 ms * 199.91.189.27
11 131 ms 131 ms 140 ms 199.91.189.27

Trace complete.

Can we get any information from SE employee if they are actually looking into it, and if anything is going to be done?

[Drk_v3nd3tta]

Getting Sick of not being able to play past 10-15 mins. I even bought a new internet provider with fast speed and still get disconnected. Square please fix this or im done for good! 3 of my friends are having the same problem and are getting sick of it

[Melondra]

Got the same problem now form time warner getting dropped every 5 min on Excalibur.

[PondHollow]

ISP: TSTT
Ticket: Tbd
State/Country: Trinidad and Tobago
Date/Time: Lag spikes at 12.25 AM Atlantic Standard Time on March 12th, 2016; 90002 error from early February to now, between 6pm atlantic standard time and 8am. Neither problem occurs during the day.
Frequency: Lag spikes every few seconds straight for a few times a week; 90002 error every 10-20 minutes, between 6pm atlantic standard time and 8am. Neither problem occurs during the day.
Content: All
World: Ultros
Traceroute records:

Traced to the Ultros server several times over a few minutes and the following two results are typical.

1 <1 ms <1 ms 1 ms 192.168.1.1
2 61 ms 43 ms 165 ms 186-45-32-1.dynamic.tstt.net.tt [186.45.32.1]
3 33 ms 33 ms 32 ms 201.238.123.65.business.static.tstt.net.tt [201.238.123.65]
4 35 ms 34 ms 37 ms 190-58-255-26.business.static.tstt.net.tt [190.58.255.26]
5 29 ms 30 ms 42 ms 190-58-255-25.business.static.tstt.net.tt [190.58.255.25]
6 30 ms 34 ms 29 ms cuscon66792.tstt.net.tt [190.58.140.10]
7 97 ms 93 ms 93 ms TenGigE0-3-0-2.GW8.MIA4.ALTER.NET [157.130.84.161]
8 88 ms 87 ms 88 ms 0.ae3.BR1.MIA19.ALTER.NET [140.222.225.111]
9 88 ms 87 ms 88 ms lag-10.ear4.Miami2.Level3.net [4.68.71.169]
10 119 ms 240 ms 120 ms ae-11-11.car2.Montreal2.Level3.net [4.69.141.1]
11 120 ms 120 ms 120 ms ae-11-11.car2.Montreal2.Level3.net [4.69.141.1]
12 128 ms 129 ms 129 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.74]
13 129 ms 129 ms 143 ms 192.34.76.10
14 120 ms 120 ms 121 ms 199.91.189.242
15 128 ms 129 ms 129 ms 199.91.189.36

1 <1 ms 1 ms 1 ms 192.168.1.1
2 47 ms 32 ms 38 ms 186-45-32-1.dynamic.tstt.net.tt [186.45.32.1]
3 33 ms 33 ms 33 ms 201.238.123.65.business.static.tstt.net.tt [201.238.123.65]
4 37 ms 35 ms 56 ms 190-58-255-26.business.static.tstt.net.tt [190.58.255.26]
5 47 ms 29 ms 46 ms 190-58-255-25.business.static.tstt.net.tt [190.58.255.25]
6 29 ms 31 ms 30 ms cuscon66792.tstt.net.tt [190.58.140.10]
7 92 ms 93 ms 93 ms TenGigE0-3-0-2.GW8.MIA4.ALTER.NET [157.130.84.161]
8 88 ms 87 ms 87 ms 0.ae3.BR1.MIA19.ALTER.NET [140.222.225.111]
9 * * * Request timed out.
10 119 ms 118 ms 140 ms ae-11-11.car2.Montreal2.Level3.net [4.69.141.1]
11 120 ms 120 ms 119 ms ae-11-11.car2.Montreal2.Level3.net [4.69.141.1]
12 129 ms 128 ms 129 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.74]
13 129 ms 129 ms 128 ms 192.34.76.10
14 120 ms 120 ms 120 ms 199.91.189.242
15 129 ms 128 ms 129 ms 199.91.189.36

The problem *just* occurred. This is typical:

1 <1 ms <1 ms 1 ms 192.168.1.1
2 34 ms 39 ms 39 ms 186-45-32-1.dynamic.tstt.net.tt [186.45.32.1]
3 33 ms 32 ms 36 ms 201.238.123.65.business.static.tstt.net.tt [201.238.123.65]
4 36 ms 35 ms 32 ms 190-58-255-26.business.static.tstt.net.tt [190.58.255.26]
5 29 ms 28 ms 33 ms 190-58-255-25.business.static.tstt.net.tt [190.58.255.25]
6 31 ms 31 ms 31 ms cuscon66792.tstt.net.tt [190.58.140.10]
7 92 ms 93 ms 94 ms TenGigE0-3-0-2.GW8.MIA4.ALTER.NET [157.130.84.161]
8 88 ms 89 ms 86 ms 0.ae3.BR1.MIA19.ALTER.NET [140.222.225.111]
9 88 ms 87 ms 87 ms lag-10.ear4.Miami2.Level3.net [4.68.71.169]
10 121 ms 121 ms 120 ms ae-11-11.car2.Montreal2.Level3.net [4.69.141.1]
11 118 ms 120 ms 121 ms ae-11-11.car2.Montreal2.Level3.net [4.69.141.1]
12 128 ms 129 ms 127 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.74]
13 127 ms 129 ms 128 ms 192.34.76.10
14 120 ms 120 ms 120 ms 199.91.189.242
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

I'll withhold blaming Level3 for this.

[Zebediah]

Please fix this! The problem isnt on the NA Datacentre exclusive, its on Chaos too i know 40-50 ppl that got problems with connection to the lobby server all the time. Have some Trouble to login for 15 Minutes every day, after 15 minutes i come in and loose Server Connection in ca 4 minutes. after this i again have login trouble and then when i came in i stay in game. dont understand what the Servers have for Problems.

Iam on Shiva have Path Pinged in CMD to the Server and this IP Adress make some Problems 94/ 100 = 94% | 9 282ms 94/ 100 = 94% 0/ 100 = 0% 195.82.50.234

94% Packet lost in the moment of the Pings!!!!!!!!!!!!! thats amazing at the Servers in "Düsseldorf- Germany" please fix this!!!!

This Problems are since we got the 3.2 Update!!!!!!! 3 Weeks now!!!

Here a Reddit Post https://www.reddit.com/r/ffxiv/comments/48m2fi/something_wrong_with_eu_and_na_servers/

Iam Really Angry!