Reporting Latency Related Issue (NA Data Center)

[Fleshette]

Name of your Internet Service Provider (ISP) - Comcast

Ticket or reference number from your ISP - NA

State/Country - New Jersey, USA

Date/Time Issue began - Late December 2015.

Frequency (How often does the issue occur?) Every day from 6pm-11pm EST, game will stop in place for 3-10 seconds, then all data will come in and game will be in what can best be described as 'fast forward', which can happen in varying frequency from twice a minute to once every ten minute intervals. Also it may come and go during the day on weekends, but not as much.

Content (Which content were you playing in-game when the issue occurred?) - Everywhere.

Which in-game World were you playing on when the issue occurred? Excalibur - Primal data center

[typezer0]

When reporting your issue in this thread, please make sure to provide the following information.
Name of your Internet Service Provider (ISP) - Comcast
Ticket or reference number from your ISP. - N/A
State/Country - FL
Date/Time (When did the issue start happening, at what specific times does this issue arise, if any.) - 5 pm - 12 am EST
Frequency (How often does the issue occur?) Whole time
Content (Which content were you playing in-game when the issue occurred?) - Open world, Dungeons especially though
Which in-game World were you playing on when the issue occurred? - Jenova
Traceroute records (optional) (Learn how to generate traceroute record)

[Cadochan]

Name of your Internet Service Provider (ISP)
Comcast
Ticket or reference number from your ISP.
State/Country
TN, US
Date/Time (When did the issue start happening, at what specific times does this issue arise, if any.)
Daily beginning around 5pm cst
Frequency (How often does the issue occur?)
Daily for the last two weeks
Content (Which content were you playing in-game when the issue occurred?) Dungeon, and open world
Which in-game World were you playing on when the issue occurred?
Occuring on Behemoth and Lamia

1 1 ms 2 ms <1 ms Get-off-my-Lawn [192.168.1.1]
2 1 ms 1 ms 1 ms 10.0.0.1
3 11 ms 9 ms 9 ms 68.52.120.1
4 11 ms 11 ms 10 ms xe-10-3-0-sur02.dickson.tn.nash.comcast.net [68.85.51.177]
5 14 ms 24 ms 12 ms xe-4-1-6-0-ar01.goodslettvll.tn.nash.comcast.net [162.151.23.37]
6 13 ms 14 ms 13 ms ae7.bar2.nashville1.Level3.net [4.68.71.53]
7 57 ms 112 ms 237 ms ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]
8 161 ms 231 ms 231 ms ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]
9 46 ms 53 ms 45 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.74]
10 59 ms * 58 ms 192.34.76.10
11 62 ms 59 ms 61 ms 199.91.189.242
12 59 ms 61 ms 58 ms 199.91.189.40

[Seraphsatan]

•Name of your Internet Service Provider (ISP) Comcast
•Ticket or reference number from your ISP. None
•State/Country Michigan MI, USA
•Date/Time Between 7-11pm est (only time I play during week)
•Frequency very often lag being 1-5 seconds long every 5-10 sec
•Content everywhere world and dungeons (duty finder)
•Which in-game World were you playing on when the issue occurred? Ultros
•Traceroute records (optional)

1 <1ms <1ms <1ms 192.168.0.1
2 10ms 9ms 9ms 96.120.40.185
3 9ms 8ms 9ms xe-9-1-0-sur02.newhaven.mi.michigan.comcast.net [68.85.188.169]
4 17ms 17ms 18ms be-5-ar02.pontiac.mi.michigan.comcast.net [68.87.191.193]
5 16ms 16ms 17ms ae2.bar1.Detroit1.Level3.net [4.68.71.33]
6 41ms 41ms 41ms ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]
7 42ms 41ms 41ms ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]
8 42ms 42ms 43ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.74]
9 59ms 61ms 59ms 192.34.76.10
10 59ms 59ms 61ms 199.91.189.242
11 59ms 60ms * 199.91.189.74
12 61ms 59ms 59ms 199.91.189.74

That time looked good but on subsequent runs LINE # 6 and 7 show randoms spikes to 140ms thru 240ms ( ae-10-10.car2.Montreal2.Level3.net [4.69.153.86])

Edit: Also this seems to be worst ever this week, before it was reasonable and slight.

[Imrathion]

so like everyone else on the past 11 pages, i have the same lag and its been like this for a while. i am personally tired of this, and I'm starting to find it real difficult to pay for a broken game.

The question that I'm sure we are all wanting/demanding at this point is will Square Enix do anything about it? A response from a dev who has some information would be great.

We are Waiting...................

[LunaKaeridge]

• Name of your Internet Service Provider (ISP): Comcast
• Ticket or reference number from your ISP: None, Comcast blames FFXIV.
• State/Country: Illinois/USA
• Date/Time: 8:00 PM +/- 2 hours, especially noticeable on Fridays/Weekends
• Frequency: Every week.
• Content: Happens everywhere, but particularly bad in instanced content
• Which in-game World were you playing on when the issue occurred?: Lamia
• Traceroute records: Tracing route to 199.91.189.45 over a maximum of 30 hops
  
  1 <1 ms <1 ms <1 ms 192.168.0.1
  2 10 ms 8 ms 8 ms 96.120.25.21
  3 9 ms 9 ms 9 ms te-0-5-0-17-sur03.mtprospect.il.chicago.comcast.net [162.151.34.157]
  4 22 ms 11 ms 12 ms te-0-8-0-10-ar01.elmhurst.il.chicago.comcast.net [68.87.231.1]
  5 * * * Request timed out.
  6 30 ms 31 ms 32 ms ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]
  7 30 ms 32 ms 29 ms ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]
  8 30 ms 30 ms 31 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.74]
  9 54 ms 43 ms 66 ms 192.34.76.10
  10 43 ms 44 ms 44 ms 199.91.189.242
  11 44 ms 44 ms 51 ms 199.91.189.45 )

[Paintedtarget]

Name of your Internet Service Provide:r Comcast
Ticket or reference number from your ISP: They would not give me one as it is a level 3 problem outside of the United States
State/Country Florida / United States
Date/Time: 6pm est till around 12am est
Frequency: Every night at those times with lag lasting up to 15 seconds
Content: All content
Which in-game World were you playing on when the issue occurred? Leviathan
Traceroute records (optional)

Tracing route to 199.91.189.42 over a maximum of 30 hops
1 1 ms 1 ms <1 ms 192.168.1.1
2 9 ms 8 ms 8 ms 96.120.21.13
3 8 ms 8 ms 8 ms xe-7-1-5-sur01.ftcaroline.fl.jacksvil.comcast.net [68.86.169.97]
4 10 ms 11 ms 11 ms te-0-3-0-1-ar02.southside.fl.jacksvil.comcast.net [68.86.168.189]
5 17 ms 18 ms 18 ms be-33489-cr01.miami.fl.ibone.comcast.net [68.86.95.45]
6 22 ms 16 ms 15 ms ae12.edge2.Miami1.level3.net [4.68.127.205]
7 51 ms 108 ms 150 ms ae-11-11.car2.Montreal2.Level3.net [4.69.141.1]
8 156 ms 189 ms 250 ms ae-11-11.car2.Montreal2.Level3.net [4.69.141.1]
9 51 ms 50 ms 50 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.74]
10 * 69 ms * 192.34.76.10
11 70 ms 70 ms 70 ms 199.91.189.242
12 70 ms * 70 ms 199.91.189.42
Trace complete.

[MoruteAshera]

• ISP: Xfinity Comcast
• Ticket #: Did not get one this time. There have been three techs out to the place for the last two months, one modem swapped out by them and forwarded/reset everything on their end and mine multiple times. They say that it is not their lines or their services causing it and boy do those technician charges add up.
• State/Country: Washington State
• Date/Time: 01-25-16 / 01-28-16 @ 6pm-9pm PST.
• Frequency: Spikes between 1 GDC to 3 minute freezes.
• Content: Roulettes (lvl 50, 60, expert), Void Ark, Thordan EX, Savage Alexander 1-4
• Server: Primal
• World: Behemoth
• Traceroute:
  

  Tracing route to 199.91.189.40 over a maximum of 30 hops
  
  1 3 ms 2 ms 1 ms 10.0.0.1
  2 * * * Request timed out.
  3 18 ms 14 ms 17 ms te-0-5-0-9-sur03.everett.wa.seattle.comcast.net
  [68.85.240.201]
  4 21 ms 17 ms 16 ms be-29-ar01.seattle.wa.seattle.comcast.net [69.13
  9.164.217]
  5 35 ms 19 ms 19 ms 4.68.71.73
  6 86 ms 91 ms 91 ms ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]
  
  7 90 ms 92 ms 99 ms ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]
  
  8 88 ms 89 ms 99 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.
  74]
  9 128 ms 134 ms 124 ms 192.34.76.10
  10 126 ms 124 ms 124 ms 199.91.189.242
  11 120 ms 121 ms 128 ms 199.91.189.40
  
  Trace complete.

  Tracing route to 199.91.189.40 over a maximum of 30 hops
  
  1 2 ms 5 ms 4 ms 10.0.0.1
  2 * * * Request timed out.
  3 16 ms 13 ms 16 ms te-0-5-0-9-sur03.everett.wa.seattle.comcast.net
  [68.85.240.201]
  4 20 ms 19 ms 34 ms be-29-ar01.seattle.wa.seattle.comcast.net [69.13
  9.164.217]
  5 33 ms 19 ms 29 ms 4.68.71.73
  6 86 ms 85 ms 89 ms ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]
  
  7 119 ms 98 ms 89 ms ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]
  
  8 87 ms 89 ms 99 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.
  74]
  9 128 ms 189 ms 128 ms 192.34.76.10
  10 125 ms 119 ms 123 ms 199.91.189.242
  11 121 ms 135 ms 130 ms 199.91.189.40
  
  Trace complete.

  Tracing route to 199.91.189.40 over a maximum of 30 hops
  
  1 7 ms 4 ms 4 ms 10.0.0.1
  2 * * * Request timed out.
  3 18 ms 19 ms 45 ms te-0-5-0-9-sur03.everett.wa.seattle.comcast.net
  [68.85.240.201]
  4 17 ms 20 ms 24 ms be-29-ar01.seattle.wa.seattle.comcast.net [69.13
  9.164.217]
  5 23 ms 14 ms 19 ms 4.68.71.73
  6 85 ms 87 ms 85 ms ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]
  
  7 86 ms 95 ms 88 ms ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]
  
  8 87 ms 89 ms 89 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.
  74]
  9 128 ms 124 ms 124 ms 192.34.76.10
  10 122 ms 123 ms 139 ms 199.91.189.242
  11 123 ms 124 ms 124 ms 199.91.189.40
  
  Trace complete.

[NolLacnala]

• Name of your Internet Service Provider: Comcast
• Ticket or reference number from your ISP: NA
• State/Country: Sacramento, CA USA
• Date/Time: Shortly after Heavensward, somewhere from patch 3.05 to 3.1
• Frequency: Every day from 4pm to 7pm PST
• Content: All, most noticeable in Alexander Savage
• Which in-game World were you playing on when the issue occurred?: Cactuar
• Traceroute records: To Cactuar, see below

tracert 199.91.189.23

Tracing route to 199.91.189.23 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 <1 ms <1 ms <1 ms 10.0.0.1
3 9 ms 21 ms 9 ms 96.120.14.97
4 10 ms 9 ms 8 ms xe-11-2-1-sur02.yubacity.ca.ccal.comcast.net [68.87.203.217]
5 16 ms 17 ms 17 ms ae-15-ar01.fresno.ca.ccal.comcast.net [162.151.40.61]
6 22 ms 22 ms 21 ms ae-20.edge2.SanJose.Level3.net [4.68.71.25]
7 92 ms 92 ms 92 ms ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]

8 96 ms 92 ms 93 ms ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]

9 93 ms 93 ms 92 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.74]
10 133 ms 101 ms 107 ms 192.34.76.10
11 101 ms 102 ms 102 ms 199.91.189.242
12 101 ms 101 ms 101 ms 199.91.189.23

Trace complete.

ping 68.87.203.217 -n 30

Pinging 68.87.203.217 with 32 bytes of data:
Reply from 68.87.203.217: bytes=32 time=11ms TTL=61
General failure.
Reply from 68.87.203.217: bytes=32 time=11ms TTL=61

Ping statistics for 68.87.203.217:
Packets: Sent = 30, Received = 29, Lost = 1 (3% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 19ms, Average = 11ms

ping 162.151.40.61

Pinging 162.151.40.61 with 32 bytes of data:
Reply from 162.151.40.61: bytes=32 time=19ms TTL=60

Ping statistics for 162.151.40.61:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 18ms, Maximum = 19ms, Average = 18ms

ping 162.151.40.61 -n 20

Pinging 162.151.40.61 with 32 bytes of data:
Reply from 162.151.40.61: bytes=32 time=19ms TTL=60

Ping statistics for 162.151.40.61:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 17ms, Maximum = 28ms, Average = 19ms

ping 4.68.71.25 -n 20

Pinging 4.68.71.25 with 32 bytes of data:
Reply from 4.68.71.25: bytes=32 time=23ms TTL=59

Ping statistics for 4.68.71.25:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 21ms, Maximum = 33ms, Average = 24ms

ping 4.69.153.86 -n 20

Pinging 4.69.153.86 with 32 bytes of data:
Reply from 4.69.153.86: bytes=32 time=93ms TTL=243
Reply from 4.69.153.86: bytes=32 time=114ms TTL=243
Reply from 4.69.153.86: bytes=32 time=138ms TTL=243
Reply from 4.69.153.86: bytes=32 time=208ms TTL=243
Reply from 4.69.153.86: bytes=32 time=101ms TTL=243
Reply from 4.69.153.86: bytes=32 time=158ms TTL=243
Reply from 4.69.153.86: bytes=32 time=98ms TTL=243

Ping statistics for 4.69.153.86:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 93ms, Maximum = 208ms, Average = 108ms

ping 4.59.178.74 -n 20

Pinging 4.59.178.74 with 32 bytes of data:
Reply from 4.59.178.74: bytes=32 time=98ms TTL=243

Ping statistics for 4.59.178.74:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 93ms, Maximum = 98ms, Average = 94ms

ping 192.34.76.10 -n 20

Pinging 192.34.76.10 with 32 bytes of data:
Reply from 192.34.76.10: bytes=32 time=118ms TTL=49
General failure.
Reply from 192.34.76.10: bytes=32 time=118ms TTL=49
Request timed out.
Reply from 192.34.76.10: bytes=32 time=118ms TTL=49

Ping statistics for 192.34.76.10:
Packets: Sent = 20, Received = 18, Lost = 2 (10% loss),
Approximate round trip times in milli-seconds:
Minimum = 117ms, Maximum = 149ms, Average = 120ms

ping 199.91.189.242 -n 20

Pinging 199.91.189.242 with 32 bytes of data:
Reply from 199.91.189.242: bytes=32 time=120ms TTL=239
Request timed out.
Reply from 199.91.189.242: bytes=32 time=118ms TTL=239
Request timed out.

Ping statistics for 199.91.189.242:
Packets: Sent = 20, Received = 18, Lost = 2 (10% loss),
Approximate round trip times in milli-seconds:
Minimum = 113ms, Maximum = 120ms, Average = 117ms

ping 199.91.189.23 -n 20

Pinging 199.91.189.23 with 32 bytes of data:
Reply from 199.91.189.23: bytes=32 time=124ms TTL=47
Request timed out.
Reply from 199.91.189.23: bytes=32 time=118ms TTL=47

Ping statistics for 199.91.189.23:
Packets: Sent = 20, Received = 19, Lost = 1 (5% loss),
Approximate round trip times in milli-seconds:
Minimum = 117ms, Maximum = 133ms, Average = 119ms

Seems like it's either a problem at the last hop from L3 or in the datacenter itself, never lagged prior to Heavensward

[Iluvwrenches]

Name of your Internet Service Provider: Rogers Cable
Ticket or reference number from your ISP: None
State/Country: Ontario, Canada
Date/Time: Since day 1 for me, which is about a week ago.
Frequency: Every hour of every day... theres never NOT a time I don't have lag issues.
Content: Its irrelevant what I am doing. I could be questing in West Thanalan or doing a dungeon like Halatii and it will still happen.
Which in-game World were you playing on when the issue occurred: Adamantoise

Tracing route to 199.91.189.74 over a maximum of 30 hops

1 1 ms 1 ms 1 ms vlan1.phub.net.cable.rogers.com [192.168.0.1]
2 8 ms 15 ms 9 ms 7.11.162.193
3 26 ms 11 ms 12 ms 69.63.242.73
4 130 ms 716 ms * 24.156.157.81
5 28 ms 29 ms 27 ms van58-9-230-26.dynamic.rogerstelecom.net [209.14
8.230.26]
6 930 ms 1637 ms 1331 ms be812.ccr41.iad02.atlas.cogentco.com [154.54.11.
217]
7 290 ms 38 ms 30 ms be2171.ccr41.dca01.atlas.cogentco.com [154.54.31
.105]
8 36 ms 35 ms 37 ms be2806.ccr41.jfk02.atlas.cogentco.com [154.54.40
.105]
9 39 ms 39 ms 39 ms be2106.ccr21.alb02.atlas.cogentco.com [154.54.3.
50]
10 44 ms 43 ms 43 ms be2088.ccr21.ymq02.atlas.cogentco.com [154.54.43
.17]
11 52 ms 51 ms 49 ms 38.122.42.34
12 231 ms 203 ms 50 ms 192.34.76.10
13 545 ms 42 ms 43 ms 199.91.189.242
14 43 ms 43 ms 52 ms 199.91.189.74

Trace complete.

Here is a Ping test:

Pinging 199.91.189.74 with 32 bytes of data:
Reply from 199.91.189.74: bytes=32 time=44ms TTL=49
Reply from 199.91.189.74: bytes=32 time=44ms TTL=49
Reply from 199.91.189.74: bytes=32 time=648ms TTL=49
Reply from 199.91.189.74: bytes=32 time=1379ms TTL=49

Ping statistics for 199.91.189.74:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 44ms, Maximum = 1379ms, Average = 528ms

There is a very clear issue with one of the results from my trace... and no, it isn't my ISP. WoW, Gw2, Gw1, CS:GO and a plethora of other games I have 0 connectivity issues with. I paid $25 on steam for this and I'm currently playing with the included game time. If I can't play without lag, I definitely will not be subscribing.