Reporting Latency Related Issue (NA Data Center)

[Downdrop]

This issue has plagued my FC since release. We used to joke about people getting off wifi and that we would mail them a 100 ft. ethernet cord to plug straight in. First it was a couple from NE Canada, then it was a couple from NW Canada, and now its me and my other friend in south Florida. Same time at around 7-10 pm EST. We got to the point where we don't even raid together anymore because its impossible to play during these times and are the only times we can all get together. We all met in 1.0 and continued playing together until all this started and destroyed our ability to play together.

This issue started for me when I was in diadem. We all soon realized through shouts that most that were affected were on PC and using Comcast. PS4 seemed to be unaffected.( due to PSN? do they run different routes to SE servers?)

I find it strange that we haven't even has somewhat of an update on whats going on. Just looking at all the posts there seems to be evidence where the problem is. It has been a few days short of 2 months since this post was created.

My husband played this game over a year ago and said he had the exact same problems as what is going on now. This problem as you said has been going on for much longer then Square Enix wants to admit. When I asked him about it he said he was told that the game uses certain ports that make it appear to be peer 2 peer filesharing and that many ISPs throttle known filesharing ports. I would think that PSN uses different ports then the PC but I'm talking about stuff I don't know much about. I will say that my pings are low despite having a large packet loss which to me feels more like being throttled then internet congestion which would also cause a high ping.

Isn't this a net neutrality issue if it is in fact throttling?

[Blacktestament7]

Name of your Internet Service Provider (ISP): Comcast
Ticket or reference number from your ISP: cr554913330
State/Country: Baltimore, Maryland, USA
Date/Time: 2000 (8:00PM), 2/1/2016
Frequency: Alot alothough this is the first time I've gotten a 90k disconnect
Content: lag spikes in Duty Roulette: Trials - Battle at Big Keep then expanded to full 90k and packet loss while Mining in the Churning Mists afterward
Which in-game World were you playing on when the issue occurred? Siren

Traceroute records
C:\WINDOWS\system32>tracert 184.107.107.176

Tracing route to 184.107.107.176 over a maximum of 30 hops

1 <1 ms 1 ms <1 ms router.asus.com [192.168.1.1]
2 12 ms 18 ms 9 ms 96.120.104.109
3 9 ms 11 ms 8 ms xe-9-2-0-32767-sur01.kirkave.md.bad.comcast.net [69.139.215.61]
4 11 ms 8 ms 9 ms ae-32-0-ar01.whitemarsh.md.bad.comcast.net [68.85.114.249]
5 * * 11 ms lag-5.bear1.Baltimore1.Level3.net [4.68.71.113]
6 14 ms 20 ms 11 ms ae-1-11.bear2.Baltimore1.Level3.net [4.69.204.174]
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 24 ms 26 ms 27 ms ae-5-5.car1.Montreal2.Level3.net [4.69.141.5]
12 26 ms 29 ms 38 ms ae-11-11.car2.Montreal2.Level3.net [4.69.141.1]
13 32 ms 27 ms 25 ms 4.59.178.62
14 53 ms 52 ms 52 ms te5-5.cr1.mtl.iweb.com [184.107.1.65]
15 26 ms 28 ms 25 ms te7-3.dr9.mtl.iweb.com [67.205.127.214]
16 26 ms 26 ms 49 ms 174.142.115.218
17 30 ms 28 ms 27 ms 184.107.107.176

Trace complete.

I do know when I tracerouted with the game up, during that request timed out period I got a 90k disconnect.

[szalkerous]

I find it strange that we haven't even has somewhat of an update on whats going on. Just looking at all the posts there seems to be evidence where the problem is. It has been a few days short of 2 months since this post was created.

Absolutely agreed. Having dead silence from SE on this topic, tied to a lack of stuff to do until 3.2 comes out, really has me considering suspending my subscription. I don't want to spend what little time I can every day watching everything stutter and lock up.

Not sure if I should post this here but I have had horrendous lag issues, dropped packets and all around bad gameplay. Tried WTFast and it definitely worked, well tonite. Gonna try again tomorrow but it looks promising. I have COMCAST 105mb nearly top tier and this is the only game I have ever had serious issues and by a country mile. I will report back if this works tomorrow. Gonna wait till it gets bad and try to see if it really does make a difference.

Based on the chart/log after playing WTFast lost 0 packets the regular connection lost 309. That is the problem.

WTFast routes user around the trouble point(s), so it was a great bandaid fix until they removed the free service and require users pay now, which combined with the usual FFXIV monthly charge is more than I want to spend on an MMO.

[Downdrop]

This thread, created on 12/04/15 is at the time I write this nearly 2 months old. This thread has nearly 24,000 views.

The other sticky topic, a welcome thread, created in 2013 has only 16,000 views.

Based on that observation alone one can deduce there are a lot of people suffering from this problem.

[Magiksan]

It's cause they really dont care to fix the issue. Its awesome! I mean you see like 5 people AFK everywhere I go and they dont get DC apparently but Active players do.

[Mikikaoru]

Is it possible the issue could be with some Square servers as well? I noticed that two of your IP addresses always give me packet loss, and they did on the below report.

Name of your Internet Service Provider (ISP): Time Warner Cable
Ticket or reference number from your ISP: N/A
State/Country: OH, USA
Date/Time (When did the issue start happening, at what specific times does this issue arise, if any.): Daily, generally at any time.
Frequency (How often does the issue occur?): Continuously
Content (Which content were you playing in-game when the issue occurred?): Dungeons, questing, raiding, PF, Fates
Which in-game World were you playing on when the issue occurred?: Balmung
Traceroute records (optional) (Learn how to generate traceroute record)

C:\Users\xxxxx>pathping 184.107.107.176

Tracing route to 184.107.107.176 over a maximum of 30 hops

0 Mikikaoru [192.168.0.3]
1 192.168.0.1
2 cpe-71-65-64-1.cinci.res.rr.com [71.65.64.1]
3 24.29.5.105
4 be32.blasohdp01r.midwest.rr.com [65.29.38.28]
5 be28.clmkohpe01r.midwest.rr.com [65.29.1.44]
6 bu-ether25.chctilwc00w-bcr00.tbone.rr.com [107.14.19.16]
7 bu-ether11.chcgildt87w-bcr00.tbone.rr.com [66.109.6.20]
8 0.ae0.pr1.chi10.tbone.rr.com [107.14.17.192]
9 ix-27-0.tcore2.CT8-Chicago.as6453.net [64.86.79.97]
10 if-3-2.tcore1.W6C-Montreal.as6453.net [66.198.96.45]
11 66.198.96.58
12 te7-3.dr9.mtl.iweb.com [67.205.127.214]
13 174.142.115.218
14 184.107.107.176

Computing statistics for 350 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Mikikaoru [192.168.0.3]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.0.1
0/ 100 = 0% |
2 13ms 0/ 100 = 0% 0/ 100 = 0% cpe-71-65-64-1.cinci.res.rr.com [7
1.65.64.1]
0/ 100 = 0% |
3 20ms 1/ 100 = 1% 1/ 100 = 1% 24.29.5.105
0/ 100 = 0% |
4 15ms 0/ 100 = 0% 0/ 100 = 0% be32.blasohdp01r.midwest.rr.com [6
5.29.38.28]
0/ 100 = 0% |
5 19ms 0/ 100 = 0% 0/ 100 = 0% be28.clmkohpe01r.midwest.rr.com [6
5.29.1.44]
0/ 100 = 0% |
6 29ms 1/ 100 = 1% 1/ 100 = 1% bu-ether25.chctilwc00w-bcr00.tbone
.rr.com [107.14.19.16]
0/ 100 = 0% |
7 31ms 0/ 100 = 0% 0/ 100 = 0% bu-ether11.chcgildt87w-bcr00.tbone
.rr.com [66.109.6.20]
0/ 100 = 0% |
8 29ms 0/ 100 = 0% 0/ 100 = 0% 0.ae0.pr1.chi10.tbone.rr.com [107.
14.17.192]
0/ 100 = 0% |
9 26ms 0/ 100 = 0% 0/ 100 = 0% ix-27-0.tcore2.CT8-Chicago.as6453.
net [64.86.79.97]
0/ 100 = 0% |
10 44ms 0/ 100 = 0% 0/ 100 = 0% if-3-2.tcore1.W6C-Montreal.as6453.
net [66.198.96.45]
0/ 100 = 0% |
11 --- 100/ 100 =100% 100/ 100 =100% 66.198.96.58
0/ 100 = 0% |
12 --- 100/ 100 =100% 100/ 100 =100% te7-3.dr9.mtl.iweb.com [67.205.127
.214]
0/ 100 = 0% |
13 47ms 0/ 100 = 0% 0/ 100 = 0% 174.142.115.218
0/ 100 = 0% |
14 46ms 0/ 100 = 0% 0/ 100 = 0% 184.107.107.176

Trace complete.

C:\Users\Michael>tracert 184.107.107.176

Tracing route to 184.107.107.176 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.0.1
2 30 ms 21 ms 50 ms cpe-71-65-64-1.cinci.res.rr.com [71.65.64.1]
3 22 ms 54 ms 22 ms 24.29.5.105
4 13 ms 15 ms 11 ms be32.blasohdp01r.midwest.rr.com [65.29.38.28]
5 16 ms 16 ms 15 ms be28.clmkohpe01r.midwest.rr.com [65.29.1.44]
6 29 ms 27 ms 23 ms bu-ether25.chctilwc00w-bcr00.tbone.rr.com [107.1
4.19.16]
7 32 ms 31 ms 31 ms bu-ether11.chcgildt87w-bcr00.tbone.rr.com [66.10
9.6.20]
8 55 ms 35 ms 25 ms 0.ae0.pr1.chi10.tbone.rr.com [107.14.17.192]
9 26 ms 25 ms 50 ms ix-27-0.tcore2.CT8-Chicago.as6453.net [64.86.79.
97]
10 42 ms 41 ms 40 ms if-3-2.tcore1.W6C-Montreal.as6453.net [66.198.96
.45]
11 42 ms 42 ms 45 ms 66.198.96.58
12 42 ms 60 ms 44 ms te7-3.dr9.mtl.iweb.com [67.205.127.214]
13 43 ms 44 ms 60 ms 174.142.115.218
14 60 ms 44 ms 63 ms 184.107.107.176

Trace complete.

[Kaleb916]

Name of your Internet Service Provider (ISP): Comcast
Ticket or reference number from your ISP: Not going to bother
State/Country: California
Date/Time: This problem occurs nightly anywhere between 4pm to 8pm pst.
Frequency: Everyday. It has been happening for about a week.
Content: Whole world
World: Excalibur

So after reviewing the forums, this seems to mainly be a Comcast problem and it starts at 4 pm pst (7 pm est). And there does not seem to be any point in contacting Comcast about this issue as most people have received a "not a problem on our end" reply. I really hope that this gets resolved soon, it really is frustrating when there is a problem that you have no control over.

[Phosion]

Here is another latency issue:
ISP: Comcast
Ticket from ISP: they refused to open a ticket
State/Country: Indiana, US
Date/Time: every night from 7:00 pm - 11:00 pm EST.
Frequency: Every night
Content: Any
Server: Brynhildr
Tracert: See below

3 15 ms 28 ms 15 ms Te0-7-0-5-sur02.kokomo.in.indiana.comcast.net [162.151.34.221]
4 40 ms 21 ms 20 ms te-8-1-ur01.wchicago.il.chicago.comcast.net [68.87.233.125]
5 85 ms 81 ms 26 ms te-1-1-0-2-ar01.indianapolis.in.indiana.comcast.net [69.139.201.173]
6 29 ms 29 ms 39 ms hu-1-13-0-0-ar01.area4.il.chicago.comcast.net [68.86.187.245]
7 * 30 ms 45 ms 4.68.63.125
8 178 ms 229 ms 226 ms ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]
9 104 ms 204 ms 213 ms ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]
10 49 ms 48 ms 60 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.74]
11 64 ms 79 ms 62 ms 192.34.76.10
12 67 ms 63 ms 64 ms 199.91.189.242
13 65 ms * 61 ms 199.91.189.46

[Sub-Xero]

•Name of your Internet Service Provider (ISP): Comcast
•Ticket or reference number from your ISP: Unable to obtain one.
•State/Country: WA, USA
•Date/Time (When did the issue start happening, at what specific times does this issue arise, if any.: This started happening consistently for me about three weeks ago. It happens every, single evening around the same time(s). It generally starts around 3-4PM PST and ends around 730-8PM PST.
•Frequency (How often does the issue occur?): Every evening/night.
•Content (Which content were you playing in-game when the issue occurred?): Any and all content.
•Which in-game World were you playing on when the issue occurred?: Gilgamesh.
•Traceroute records: Tracing route to 199.91.189.57 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 12 ms 11 ms 11 ms te-0-0-0-4-sur01.tumwater.wa.seattle.comcast.net [68.86.113.97]
4 23 ms 13 ms 13 ms be-44-ar01.burien.wa.seattle.comcast.net [69.139.164.18]
5 14 ms 16 ms 12 ms 4.68.71.77
6 84 ms 84 ms 83 ms ae-32-52.ebr2.Seattle1.Level3.net [4.69.147.182]
7 83 ms 83 ms 86 ms ae-2-2.ebr2.Denver1.Level3.net [4.69.132.54]
8 * * * Request timed out.
9 83 ms 83 ms 82 ms ae-6-6.ebr1.Chicago1.Level3.net [4.69.140.189]
10 272 ms 213 ms 214 ms ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]
11 84 ms 92 ms 84 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.74]
12 128 ms 96 ms 96 ms 192.34.76.10
13 97 ms 106 ms 96 ms 199.91.189.242

Every hop after that is "request timed out."

[Desire]

now getting dc'd every few min PLEASE fix this is stupid!

see previous post for info

Tracing route to 184.107.107.176 over a maximum of 30 hops

1 7 ms 3 ms 5 ms 192.168.1.1
2 21 ms 33 ms 19 ms 96.120.24.209
3 20 ms 11 ms 8 ms te-0-2-0-3-sur04.algonquin.il.chicago.comcast.net [68.86.118.237]
4 18 ms 15 ms 19 ms te-2-7-0-7-ar01.area4.il.chicago.comcast.net [68.86.196.201]
5 * * * Request timed out.
6 200 ms 213 ms 218 ms ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]
7 178 ms 116 ms 210 ms ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]
8 34 ms 33 ms 38 ms 4.59.178.62
9 50 ms 54 ms 47 ms te5-5.cr1.mtl.iweb.com [184.107.1.65]
10 43 ms 41 ms 42 ms te7-3.dr9.mtl.iweb.com [67.205.127.214]
11 61 ms 49 ms 41 ms 174.142.115.218
12 42 ms 41 ms 41 ms 184.107.107.176

Trace complete.


Tracing route to 184.107.107.176 over a maximum of 30 hops

1 2 ms <1 ms 1 ms 192.168.1.1
2 18 ms 17 ms 11 ms 96.120.24.209
3 16 ms 10 ms 17 ms te-0-2-0-3-sur04.algonquin.il.chicago.comcast.net [68.86.118.237]
4 12 ms 14 ms 28 ms te-8-2-ur01.griffith.in.chicago.comcast.net [69.139.201.69]
5 * * * Request timed out.
6 33 ms 32 ms 40 ms ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]
7 33 ms 35 ms 37 ms ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]
8 32 ms 34 ms 33 ms 4.59.178.62
9 * * 47 ms te5-5.cr1.mtl.iweb.com [184.107.1.65]
10 57 ms 41 ms 40 ms te7-3.dr9.mtl.iweb.com [67.205.127.214]
11 40 ms 40 ms 42 ms 174.142.115.218
12 41 ms 42 ms 42 ms 184.107.107.176

Trace complete.