Reporting Latency Related Issue (NA Data Center)

[EXTREME_MDP]

Name of your Internet Service Provider (ISP): COX Communications

Ticket or reference number from your ISP: don't have one. no problems with ISP.
State/Country: USA

Date/Time (When did the issue start happening, at what specific times does this issue arise, if any.): Since 2-6-2017 in the p.m. hours to current.

Frequency (How often does the issue occur?): constantly since beginning date, 2-6-2017. Freeze-up's lasts 1-3 seconds, and time in between them is random, on average in-between time is approx. 20-45 seconds.

Content (Which content were you playing in-game when the issue occurred?):
It happens when I'm in my subdivision, Lavender Beds with no one else around, while in ANY instance (duty/raid/dungeon/cinematic), in towns Idyllshire, Limsa,..any city/outpost/town. Lags even more around a lot of players in Idyllshire or in a raid, but just standing still looking at environmental animation locks me up too. Oh, and on mounts.

Which in-game World were you playing on when the issue occurred?: Goblin (Aether), but I've also tried Diobolos (Primal) and lagged just the same.

Traceroute records (optional):I would give you these but I don't know how to obtain them. I copy/pasted these form questions from the last person who posted in this forum, and just filled in my own information.

Please help because this has rendered my game unplayable for 2 nights in a row now. If not fixed, I see another night coming up. I miss my addiction!!

I found a fix to my problem (knock on wood!!):
I needed to update my NIC (LAN) driver. I was experiencing a memory leak from a bad driver. Updated the driver from the motherboard website, and no problems!! Fixed! Works beautifully as it should! See you in game!

[Callinon]

I feel like I should just start doing one of these every day since this keeps not improving. Is anyone even bothering to watch this thread I wonder?

[*]Name of your Internet Service Provider (ISP) Comcast
[*]Ticket or reference number from your ISP. None, pretty sure it isn't their problem
[*]State/Country Illinois, USA
[*]Date/Time (When did the issue start happening, at what specific times does this issue arise, if any.) Since patch day for 3.5
[*]Frequency (How often does the issue occur?) Constant.
[*]Content (Which content were you playing in-game when the issue occurred?) All content areas, though particularly noticable in duties since I'm pushing more buttons there.
[*]Which in-game World were you playing on when the issue occurred? Ultros
[*]Traceroute records (optional) (Learn how to generate traceroute record)

C:\Users\Jon>tracert 199.91.189.36

Tracing route to 199.91.189.36 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1]
2 <1 ms <1 ms <1 ms 10.0.0.1
3 9 ms 9 ms 9 ms 96.120.28.53
4 11 ms 9 ms 10 ms te-0-7-0-8-sur03.chicago301.il.chicago.comcast.net [68.85.180.45]
5 13 ms 10 ms 11 ms te-0-7-0-1-sur04.chicago301.il.chicago.comcast.net [69.139.203.222]
6 12 ms 19 ms 14 ms 162.151.45.69
7 * * * Request timed out.
8 33 ms 32 ms 32 ms ae-1-11.bear1.Montreal2.Level3.net [4.69.203.133]
9 36 ms 40 ms 34 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.74]
10 38 ms 39 ms 34 ms 10.2.0.1
11 36 ms 36 ms 34 ms 192.34.76.2
12 40 ms 41 ms 37 ms 199.91.189.234
13 37 ms 34 ms 37 ms 199.91.189.36

Trace complete.

Gameplay is extremely frustrating when a third to half of my button presses are just ignored.

[_Babble_]

Name of your Internet Service Provider (ISP) - Cox

Ticket or reference number from your ISP. - none

State/Country - California

Date/Time (When did the issue start happening, at what specific times does this issue arise, if any.) - 2/15 4:30 am

Frequency (How often does the issue occur?) - this is the first time it's happened

Content (Which content were you playing in-game when the issue occurred?) - The game is unplayable right now, so I wasn't doing anything

Which in-game World were you playing on when the issue occurred? - Leviathan

Traceroute records (optional) (Learn how to generate traceroute record)
Tracing route to 199.91.189.93 over a maximum of 30 hops

1 1 ms <1 ms <1 ms 192.168.0.1
2 7 ms 10 ms 7 ms 10.147.0.1
3 7 ms 9 ms 8 ms ip68-6-12-166.sd.sd.cox.net [68.6.12.166]
4 10 ms 9 ms 13 ms visthbrc01-get0702.sd.sd.cox.net [68.6.8.119]
5 12 ms 25 ms 12 ms ae56.bar1.SanDiego1.Level3.net [4.16.104.73]
6 14 ms 39 ms 11 ms ae-0-11.bar2.SanDiego1.Level3.net [4.69.146.66]
7 45 ms 40 ms 39 ms ae-5-5.ebr4.Dallas1.Level3.net [4.69.140.106]
8 40 ms 39 ms 42 ms ae-1-11.ebr5.Dallas1.Level3.net [4.69.134.18]
9 108 ms 102 ms 103 ms ae-3-3.ebr1.NewYork6.Level3.net [4.69.160.82]
10 76 ms 73 ms 74 ms ae-1-11.ebr2.NewYork6.Level3.net [4.69.208.162]
11 74 ms 76 ms 73 ms ae-13-13.ebr4.NewYork1.Level3.net [4.69.210.114]
12 84 ms 84 ms 82 ms ae-2-12.bear1.Montreal2.Level3.net [4.69.203.129]
13 87 ms 82 ms 82 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.74]
14 * * * Request timed out.
15 81 ms 80 ms 80 ms 192.34.76.2
16 82 ms 81 ms 81 ms 199.91.189.234
17 113 ms 112 ms 112 ms 199.91.189.93

Trace complete.

[_Babble_]

Game is still unplayable. Tracert looks the same as above. Its obviously not on my end. Any ETA on a fix?

[Callinon]

So I decided that one tracert actually doesn't illustrate the problem very well.

Here's 3:

Tracing route to 199.91.189.36 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1]
2 <1 ms <1 ms <1 ms 10.0.0.1
3 10 ms 14 ms 12 ms 96.120.28.53
4 11 ms 9 ms 9 ms te-0-7-0-8-sur03.chicago301.il.chicago.comcast.net [68.85.180.45]
5 11 ms 9 ms 9 ms te-0-7-0-1-sur04.chicago301.il.chicago.comcast.net [69.139.203.222]
6 13 ms 12 ms 12 ms 162.151.45.69
7 11 ms 14 ms 14 ms 4.68.63.125
8 33 ms 35 ms 31 ms ae-1-11.bear1.Montreal2.Level3.net [4.69.203.133]
9 33 ms 34 ms 42 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.74]
10 39 ms 35 ms 36 ms 10.2.0.1
11 36 ms 37 ms 39 ms 192.34.76.2
12 38 ms 39 ms 39 ms 199.91.189.234
13 34 ms 37 ms 37 ms 199.91.189.36

Trace complete.

C:\Users\Jon>tracert 199.91.189.36

Tracing route to 199.91.189.36 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1]
2 <1 ms <1 ms <1 ms 10.0.0.1
3 12 ms 9 ms 9 ms 96.120.28.53
4 9 ms 10 ms 11 ms te-0-7-0-8-sur03.chicago301.il.chicago.comcast.net [68.85.180.45]
5 10 ms 18 ms 11 ms te-0-7-0-1-sur04.chicago301.il.chicago.comcast.net [69.139.203.222]
6 15 ms 12 ms 12 ms 162.151.45.69
7 * * * Request timed out.
8 * * 73 ms ae-1-11.bear1.Montreal2.Level3.net [4.69.203.133]
9 32 ms 34 ms 33 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.74]
10 34 ms 34 ms 34 ms 10.2.0.1
11 36 ms 37 ms 39 ms 192.34.76.2
12 39 ms 52 ms 37 ms 199.91.189.234
13 47 ms 34 ms 34 ms 199.91.189.36

Trace complete.

C:\Users\Jon>tracert 199.91.189.36

Tracing route to 199.91.189.36 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1]
2 <1 ms <1 ms <1 ms 10.0.0.1
3 10 ms 9 ms 9 ms 96.120.28.53
4 19 ms 8 ms 9 ms te-0-7-0-8-sur03.chicago301.il.chicago.comcast.net [68.85.180.45]
5 14 ms 9 ms 12 ms te-0-7-0-1-sur04.chicago301.il.chicago.comcast.net [69.139.203.222]
6 33 ms 34 ms 34 ms 162.151.45.69
7 * * * Request timed out.
8 33 ms * * ae-1-11.bear1.Montreal2.Level3.net [4.69.203.133]
9 33 ms 32 ms 32 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.74]
10 36 ms 39 ms 37 ms 10.2.0.1
11 39 ms 34 ms 34 ms 192.34.76.2
12 36 ms 36 ms 39 ms 199.91.189.234
13 38 ms 34 ms 37 ms 199.91.189.36

Trace complete.

See what's happening there at hops 7 and 8? That's the problem. There it is. Right there.

[Randomcast]

Lag spikes and getting kicked from the game every 3-9 minutes.

Name of your Internet Service Provider (ISP): Aureon Network Services
Ticket or reference number from your ISP: N/A
State/Country: Iowa, USA
Date/Time (When did the issue start happening, at what specific times does this issue arise, if any.): 10AM-on
Frequency (How often does the issue occur?): Whole time about 3-9 minutes
Content (Which content were you playing in-game when the issue occurred?): Heavensward/all
Which in-game World were you playing on when the issue occurred?: Exodus
Traceroute records (optional) (Learn how to generate traceroute record):


Tracing route to 199.91.189.36 over a maximum of 30 hops

1 4 ms 2 ms 3 ms DeviceDHCP.Home [192.168.1.1]
2 3 ms 13 ms 4 ms 208.126.28.254
3 8 ms 6 ms 6 ms 167.142.65.17
4 8 ms 9 ms 7 ms ins-border10-ds1-61-197.desm.netins.net [167.142.61.197]
5 13 ms 11 ms 11 ms ins-dc2-be400.desm.netins.net [167.142.58.12]
6 11 ms 10 ms 10 ms ins-wc1-po20.wdmn.netins.net.67.142.167.in-addr.arpa [167.142.67.34]
7 25 ms 24 ms 24 ms be4902.rcr21.dsm01.atlas.cogentco.com [38.104.184.49]
8 25 ms 24 ms 25 ms be2640.ccr42.ord01.atlas.cogentco.com [154.54.29.125]
9 33 ms 31 ms 31 ms be2718.ccr22.cle04.atlas.cogentco.com [154.54.7.130]
10 41 ms 40 ms 41 ms be2994.ccr22.yyz02.atlas.cogentco.com [154.54.31.234]
11 70 ms 69 ms 70 ms be2093.ccr22.ymq01.atlas.cogentco.com [154.54.44.106]
12 * * 72 ms hu0-4-0-0.ccr22.ymq02.atlas.cogentco.com [154.54.31.221]
13 69 ms * 70 ms 38.122.42.34
14 * * * Request timed out.
15 70 ms 71 ms * 192.34.76.2
16 * 71 ms 73 ms 199.91.189.234
17 * 69 ms * 199.91.189.36
18 70 ms 69 ms 69 ms 199.91.189.36

Trace complete.

[Callinon]

Here are today's tracert's after getting d/c'd twice this morning and getting a ton of lag in the meantime...

C:\Users\Jon>tracert 199.91.189.36

Tracing route to 199.91.189.36 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1]
2 <1 ms <1 ms <1 ms 10.0.0.1
3 10 ms 9 ms 9 ms 96.120.28.53
4 11 ms 9 ms 9 ms te-0-7-0-8-sur03.chicago301.il.chicago.comcast.net [68.85.180.45]
5 11 ms 11 ms 14 ms te-0-7-0-1-sur04.chicago301.il.chicago.comcast.net [69.139.203.222]
6 13 ms 16 ms 12 ms 162.151.45.69
7 * 13 ms 9 ms 4.68.63.125
8 33 ms 64 ms 32 ms ae-1-11.bear1.Montreal2.Level3.net [4.69.203.133]
9 32 ms 39 ms 32 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.74]
10 * * * Request timed out.
11 36 ms 36 ms 39 ms 192.34.76.2
12 36 ms 39 ms 39 ms 199.91.189.234
13 38 ms 35 ms 37 ms 199.91.189.36

Trace complete.

C:\Users\Jon>tracert 199.91.189.36

Tracing route to 199.91.189.36 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1]
2 <1 ms <1 ms <1 ms 10.0.0.1
3 13 ms 9 ms 9 ms 96.120.28.53
4 13 ms 9 ms 9 ms te-0-7-0-8-sur03.chicago301.il.chicago.comcast.net [68.85.180.45]
5 14 ms 12 ms 9 ms te-0-7-0-1-sur04.chicago301.il.chicago.comcast.net [69.139.203.222]
6 11 ms 14 ms 12 ms 162.151.45.69
7 * * * Request timed out.
8 * 34 ms 32 ms ae-1-11.bear1.Montreal2.Level3.net [4.69.203.133]
9 41 ms 32 ms 35 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.74]
10 * * * Request timed out.
11 35 ms 37 ms 35 ms 192.34.76.2
12 39 ms 39 ms 39 ms 199.91.189.234
13 38 ms 44 ms 37 ms 199.91.189.36

Trace complete.

C:\Users\Jon>tracert 199.91.189.36

Tracing route to 199.91.189.36 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1]
2 <1 ms <1 ms <1 ms 10.0.0.1
3 10 ms 9 ms 9 ms 96.120.28.53
4 18 ms 19 ms 9 ms te-0-7-0-8-sur03.chicago301.il.chicago.comcast.net [68.85.180.45]
5 11 ms 13 ms 12 ms te-0-7-0-1-sur04.chicago301.il.chicago.comcast.net [69.139.203.222]
6 14 ms 14 ms 12 ms 162.151.45.69
7 * 13 ms 12 ms 4.68.63.125
8 34 ms 34 ms 32 ms ae-1-11.bear1.Montreal2.Level3.net [4.69.203.133]
9 31 ms 38 ms * ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.74]
10 * * * Request timed out.
11 36 ms 47 ms 39 ms 192.34.76.2
12 38 ms 39 ms 39 ms 199.91.189.234
13 38 ms 39 ms 34 ms 199.91.189.36

Trace complete.

It'd be really nice to know that someone from SE is actually reading this and gives a crap about finding a solution. Your game is borderline unplayable for what has to be a good chunk of the US.

[Sneeziewantch]

Name of your Internet Service Provider: Bell Aliant
Ticket or reference number from your ISP: Claim nothing is wrong (always do)
State/Country Halifax , Canada
Date/Time :3 days ago
Frequency : all the time mostly in instances
Content all
Which in-game World were you playing on when the issue occurred? Leviathan
Traceroute records

Microsoft Windows [Version 10.0.14393]
(c) 2016 Microsoft Corporation. All rights reserved.

C:\Users\Scott>tracert 199.91.189.40

Tracing route to 199.91.189.40 over a maximum of 30 hops

1 2 ms 2 ms 2 ms 192.168.2.1
2 4 ms 3 ms 3 ms loop0.6cw.ba17.hlfx.ns.aliant.net [142.176.50.10]
3 8 ms 33 ms 7 ms BE14-181.cr01.hlfx.ns.aliant.net [142.166.181.125]
4 7 ms 8 ms 8 ms BE16.cr01.stjh.nb.aliant.net [142.166.185.65]
5 7 ms 6 ms 6 ms ae3-50.cr02.stjh.nb.aliant.net [142.166.181.110]
6 29 ms 33 ms 28 ms ae0.bx01.toro.on.aliant.net [207.231.227.53]
7 35 ms 41 ms 38 ms bx2-torontoxn_ae3 [184.150.187.56]
8 40 ms 39 ms 39 ms tcore4-torontoxn_hundredgige0-6-0-0.net.bell.ca [64.230.97.146]
9 36 ms 35 ms 34 ms bx1-torontoxn_et4-0-0.net.bell.ca [64.230.97.159]
10 25 ms 25 ms 29 ms xe-8-1-0.edge1.Toronto2.Level3.net [4.59.181.1]
11 * * 35 ms ae-1-11.bear1.Montreal2.Level3.net [4.69.203.133]
12 32 ms 34 ms 34 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.74]
13 * * * Request timed out.
14 32 ms 35 ms 35 ms 192.34.76.2
15 32 ms 31 ms 32 ms 199.91.189.234
16 35 ms 32 ms 31 ms 199.91.189.40

Trace complete.

[Callinon]

Several d/c's today, lots of eaten button presses too.

Here's your bloody tracert, enjoy:

Tracing route to 199.91.189.36 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1]
2 <1 ms <1 ms <1 ms 10.0.0.1
3 9 ms 9 ms 9 ms 96.120.28.53
4 10 ms 9 ms 9 ms te-0-7-0-8-sur03.chicago301.il.chicago.comcast.net [68.85.180.45]
5 12 ms 10 ms 9 ms te-0-7-0-1-sur04.chicago301.il.chicago.comcast.net [69.139.203.222]
6 15 ms 11 ms 12 ms 162.151.45.69
7 * * * Request timed out.
8 41 ms 33 ms 33 ms ae-1-11.bear1.Montreal2.Level3.net [4.69.203.133]
9 32 ms 34 ms 39 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.74]
10 * * * Request timed out.
11 60 ms 49 ms 49 ms 192.34.76.2
12 46 ms 44 ms 54 ms 199.91.189.234
13 43 ms 42 ms 39 ms 199.91.189.36

Trace complete.

At what point does this become unacceptable network quality, SE? Either your ISP or their direct backbone is clearly not up to handling your traffic, especially with how sensitive the game is to latency and lost packets.

[Vhailor]

Same issue here, lots of disconnects. Haven't had any for the past few weeks (up until today), but they've occurred sporadically since I returned to the game about two months ago. Here's the tracert:

Tracing route to 199.91.189.40 over a maximum of 30 hops

1 9 ms 5 ms 46 ms 10.0.0.1
2 26 ms 15 ms 14 ms 96.120.13.9
3 18 ms 13 ms 17 ms ae-202-sur02.longmont.co.denver.comcast.net [68.85.220.65]
4 22 ms 19 ms 24 ms ae-10-sur03.longmont.co.denver.comcast.net [68.85.89.53]
5 26 ms 51 ms 18 ms ae-32-ar01.denver.co.denver.comcast.net [68.85.89.189]
6 * 41 ms 29 ms lag-16.ear2.Denver1.Level3.net [4.68.63.165]
7 * 65 ms 66 ms ae-1-11.bear1.Montreal2.Level3.net [4.69.203.133]
8 65 ms 64 ms 62 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.74]
9 * * * Request timed out.
10 65 ms 66 ms 72 ms 192.34.76.2
11 63 ms 66 ms 69 ms 199.91.189.234
12 68 ms 69 ms 69 ms 199.91.189.40

Trace complete.

This seriously needs to get resolved. I know some people continually blame Level3, but if that's indeed the problem, SE needs to relocate their servers out of Canada. I have never experienced an online game with these performance issues before, excepting FFXIV (and, occasionally, FFXI, which had servers located in Japan). We're paying for this service, SE. Whatever you're doing that's causing FFXIV to not function like every other title out there needs to be fixed.