Reporting Latency Related Issue (NA Data Center)

[Kitakaze]

Name of your Internet Service Provider (ISP): Xfinity (Comcast)

Ticket or reference number from your ISP: N/A

State/Country: Florida, USA

Date/Time (When did the issue start happening, at what specific times does this issue arise, if any.): Everytime I log in since the recovery/maintenance on July 9, 2016.

Frequency (How often does the issue occur?): Lag occurs every few seconds.

Content (Which content were you playing in-game when the issue occurred?): Being idle around town. Players running around Idyllshire and suddenly stops and go at the same time (like a stop dance) gives me a hint that playing content will be frustrating and thus unplayable.

Which in-game World were you playing on when the issue occurred: Cactuar (NA)

[DrakvaGaelicos]

Name of your Internet Service Provider (ISP): Comcast/Xfinity
Ticket or reference number from your ISP: N/A; they claim issue is not on their end or out of their control. Traceroute records seem to support.
State/Country: CA/USA
Date/Time: First week of December 2015 and ongoing ever since.
Constant, severe, unplayable spikes at 5:30-9:30 P.M. PST and frequent unplayable spikes at 1:00-3:00 A.M.
Frequency: Daily, Rare days of solid connection (fewer than 3 per month)
Content: Anything
Which in-game World were you playing on when the issue occurred? Malboro
Traceroute records: Run at approx. 9:30 P.M. when issue is just calming down. During peak times (5:30-8:30) times can range from 450ms-800ms per hop from steps 6 through 11, or time out altogether.

Tracing route to 199.91.189.24 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 15 ms 9 ms 8 ms 96.120.86.5
3 8 ms 8 ms 8 ms 68.85.104.89
4 10 ms 9 ms 10 ms 162.151.40.17
5 14 ms 14 ms 14 ms 4.68.71.25
6 89 ms 108 ms 99 ms ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]
7 85 ms 83 ms 90 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.74]
8 101 ms 101 ms 100 ms 10.2.0.1
9 * 98 ms 97 ms 192.34.76.2
10 98 ms * 103 ms 199.91.189.234
11 100 ms 100 ms 100 ms 199.91.189.24

Trace complete.

-----------------------------------------------------------------------------------

Tracing route to 199.91.189.24 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 8 ms 8 ms 15 ms 96.120.86.5
3 8 ms 8 ms 9 ms 68.85.104.89
4 10 ms 9 ms 11 ms 162.151.40.17
5 15 ms 15 ms 15 ms 4.68.71.25
6 84 ms 84 ms 83 ms ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]
7 83 ms 84 ms 84 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.74]
8 101 ms * 101 ms 10.2.0.1
9 97 ms 97 ms 97 ms 192.34.76.2
10 * 98 ms 97 ms 199.91.189.234
11 * 101 ms 100 ms 199.91.189.24

Trace complete.

-----------------------------------------------------------------------------------

Tracing route to 199.91.189.24 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 8 ms 8 ms 8 ms 96.120.86.5
3 25 ms 8 ms 8 ms 68.85.104.89
4 10 ms 9 ms 10 ms 162.151.40.17
5 15 ms 14 ms 14 ms 4.68.71.25
6 84 ms 83 ms 84 ms ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]
7 84 ms 84 ms 84 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.74]
8 101 ms 101 ms * 10.2.0.1
9 97 ms 97 ms 97 ms 192.34.76.2
10 97 ms 97 ms 97 ms 199.91.189.234
11 101 ms 101 ms 100 ms 199.91.189.24

Trace complete.

-----------------------------------------------------------------------------------

Tracing route to 199.91.189.24 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 16 ms 8 ms 9 ms 96.120.86.5
3 8 ms 8 ms 8 ms 68.85.104.89
4 9 ms 9 ms 9 ms 162.151.40.17
5 15 ms 14 ms 14 ms 4.68.71.25
6 87 ms 83 ms 83 ms ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]
7 84 ms 83 ms 83 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.74]
8 101 ms * * 10.2.0.1
9 97 ms 99 ms 97 ms 192.34.76.2
10 98 ms 98 ms 98 ms 199.91.189.234
11 * 101 ms 100 ms 199.91.189.24

Trace complete.

=======================================================

This issue has trouble me for seven months and there's been no relief. I'm unable to play progression content at times where a majority of groups run it, and that is the only activity that I haven't done. Prior to December 2015, gameplay was immaculate at all times of day.

Edit: Collapsing trace for space saving.

[NakaNoob]

Alright, this has become a nightly occurrence with FFXIV, particularly excruciating when running any sort of instanced (Dungeon, Raid, Roulette) content. There are several posts on Reddit with the same information, complaints, and requests for help.

Name of your Internet Service Provider (ISP): Comcast/Xfinity
Ticket or reference number from your ISP: Comcast states issue lies upstream with Level3, and traceroutes and pings support this information wholly.
State/Country: Colorado, USA
Date/Time: Occurring since December, 2015.
Symptoms: Constant, severe, unplayable spikes during expected Peak Times of Internet Traffic and player traffic to Canada. (6:00 P.M. MDT - 10:30 P.M. MDT typically)
Frequency: This occurs almost every single night, and it is becoming extremely frustrating.
Content: Anything
Which in-game World were you playing on when the issue occurred? Gilgamesh
Traceroute records: Run at approx. 10:00 P.M. MDT when issue appeared to be at its worst for me during this evening.

All troubleshooting techniques used below were run simultaneously.

Pings to Gilgamesh's IP (supposedly 199.91.189.26):
Reply from 199.91.189.26: bytes=32 time=78ms TTL=52
Request timed out.
Reply from 199.91.189.26: bytes=32 time=74ms TTL=52
Reply from 199.91.189.26: bytes=32 time=82ms TTL=52
Reply from 199.91.189.26: bytes=32 time=71ms TTL=52
Request timed out.
Reply from 199.91.189.26: bytes=32 time=80ms TTL=52
Reply from 199.91.189.26: bytes=32 time=71ms TTL=52
Request timed out.
Reply from 199.91.189.26: bytes=32 time=71ms TTL=52
Reply from 199.91.189.26: bytes=32 time=78ms TTL=52

Ping statistics for 199.91.189.26:
    Packets: Sent = 113, Received = 86, Lost = 27 (23% loss),
Approximate round trip times in milli-seconds:
    Minimum = 70ms, Maximum = 85ms, Average = 73ms


Pings to Google DNS (8.8.8.8):
Reply from 8.8.8.8: bytes=32 time=18ms TTL=57
Reply from 8.8.8.8: bytes=32 time=15ms TTL=57
Reply from 8.8.8.8: bytes=32 time=37ms TTL=57
Reply from 8.8.8.8: bytes=32 time=14ms TTL=57
Reply from 8.8.8.8: bytes=32 time=16ms TTL=57
Reply from 8.8.8.8: bytes=32 time=24ms TTL=57
Reply from 8.8.8.8: bytes=32 time=22ms TTL=57
Reply from 8.8.8.8: bytes=32 time=24ms TTL=57
Reply from 8.8.8.8: bytes=32 time=20ms TTL=57
Reply from 8.8.8.8: bytes=32 time=20ms TTL=57
Reply from 8.8.8.8: bytes=32 time=15ms TTL=57
Reply from 8.8.8.8: bytes=32 time=19ms TTL=57
Reply from 8.8.8.8: bytes=32 time=16ms TTL=57

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

Traceroute to Gilgamesh's IP: C:>tracert 199.91.189.26
Tracing route to 199.91.189.26 over a maximum of 30 hops

  1     1 ms     1 ms     2 ms  10.0.0.1
  2    12 ms    17 ms    11 ms  96.120.13.13
  3    13 ms    15 ms    14 ms  xe-9-1-0-sur03.longmont.co.denver.comcast.net [68.85.220.69]
  4    12 ms    17 ms    16 ms  ae-32-ar01.denver.co.denver.comcast.net [68.85.89.189]
  5    15 ms    11 ms    17 ms  4.68.63.165
  6    61 ms    59 ms    59 ms  ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]
  7    59 ms    56 ms    59 ms  ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.74]
  8    72 ms    72 ms    78 ms  10.2.0.1
  9    71 ms    72 ms    77 ms  192.34.76.2
 10     *       71 ms    74 ms  199.91.189.234
 11    72 ms    74 ms    73 ms  199.91.189.26

Trace complete.

C:\>tracert 199.91.189.26

Tracing route to 199.91.189.26 over a maximum of 30 hops

  1     3 ms     2 ms     1 ms  10.0.0.1
  2    17 ms    17 ms    16 ms  96.120.13.13
  3    16 ms    15 ms    16 ms  xe-9-1-0-sur03.longmont.co.denver.comcast.net [68.85.220.69]
  4    15 ms    14 ms    12 ms  ae-32-ar01.denver.co.denver.comcast.net [68.85.89.189]
  5    16 ms    13 ms    10 ms  4.68.63.165
  6    66 ms    59 ms    59 ms  ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]
  7    59 ms    56 ms    56 ms  ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.74]
  8     *       70 ms    73 ms  10.2.0.1
  9    73 ms     *       71 ms  192.34.76.2
 10     *       78 ms    80 ms  199.91.189.234
 11     *       72 ms    77 ms  199.91.189.26

Trace complete.

Please look into this issue and acknowledge or deny whether there is a problem. Switching ISPs is unfortunately something that I cannot do where I live, as Comcast is my only option. Rarely is there a night where I can play without any packet loss to your servers, and enjoy my night playing FFXIV.

Thanks for your time.

[CaduceusDeus]

Name of your Internet Service Provider (ISP): Comcast
Ticket or reference number from your ISP: None.
State/Country: WA, USA
Date/Time: Occurring periodically since switching ISPs three months ago.
Symptoms: Constant, severe, unplayable spikes during expected Peak Times of Internet Traffic and player traffic to Canada. (6:00 P.M. PDT - 10:30 P.M. PDT typically)
Frequency: Weekday evenings. Severity varies. First time in a few weeks I've noticed really bad lag issues.
Content: All
Which in-game World were you playing on when the issue occurred? Adamantoise
Traceroute records: Run at approx. 10:00 P.M. PDT when issue appeared to be at its worst for me during this evening.

tracert 199.91.189.30

Tracing route to 199.91.189.30 over a maximum of 30 hops

1    <1 ms    <1 ms    <1 ms  192.168.2.1  (My Network)
2     *        *        *     Request timed out.  (My Network)
3    11 ms     8 ms     9 ms  te-0-1-0-8-sur02.everett.wa.seattle.comcast.net [68.85.241.77] (Comcast)
4    12 ms    15 ms    14 ms  be-29-ar01.burien.wa.seattle.comcast.net [69.139.164.213] (Comcast)
5    25 ms    12 ms    12 ms  4.68.71.77 (Level3)
6    91 ms    94 ms    85 ms  ae-10-10.car2.Montreal2.Level3.net [4.69.153.86] (Level3)
7    82 ms    85 ms    91 ms  ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.74] (Ormuco)
8    95 ms    95 ms     *     10.2.0.1 (Local Address so can't ping / Packet Loss past this point)
9     *       95 ms     *     192.34.76.2 (Ormuco)
10   94 ms    95 ms     *     199.91.189.234 (Ormuco / SE)
11   96 ms    99 ms   106 ms  199.91.189.30 (Ormuco / SE / Adamantoise!)
Trace complete.

It always seems like it's with Ormuco. (Also, it's funny that the SE IP address is still registered under EIDOS).

[JMendez01]

Name of your Internet Service Provider: Claro Dominicana
Ticket or reference number from your ISP.
State/Country: Dominican Republic
Date/Time: I dont remember the exact time, but occured after the last maintenance
Frequency: 3-5 times
Content: This happend when i'm playing on dungeon's and trial's

Aether Data Center-Sargatanas World

[Cleanse]

This issue has trouble me for seven months and there's been no relief. I'm unable to play progression content at times where a majority of groups run it, and that is the only activity that I haven't done. Prior to December 2015, gameplay was immaculate at all times of day.

Same here. Raiding or playing feast in the early evening (when it's peak time) is a no no.

[MrSinnyPants]

ISP: BT
Ticket: N/A
Country: England
Date: More or less the past several days, there were reports that powercuts did affect the service but they supposedly fixed the issue.
Frequency: Mostly mornings, still occurs in the afternoon. More often while trying to load my character or even connect to the data center.
Content: Trying to load the game itself.
World: Jenova

Traceroute Record -

Tracing route to 199.91.189.27 over a maximum of 30 hops

1 4 ms 4 ms 1 ms BThomehub.home [192.168.1.254]
2 * * * Request timed out.
3 * * * Request timed out.
4 9 ms 11 ms 9 ms 31.55.186.176
5 10 ms 20 ms 10 ms core3-hu0-1-0-1.faraday.ukcore.bt.net [195.99.127.34]
6 11 ms 10 ms 10 ms peer5-BE5.telehouse.ukcore.bt.net [213.121.193.171]
7 10 ms 10 ms 10 ms t2c4-et-3-1-0-0.uk-lon1.eu.bt.net [166.49.211.244]
8 11 ms 10 ms 10 ms hu0-1-0-0.ccr22.lon01.atlas.cogentco.com [130.117.14.229]
9 12 ms 12 ms 10 ms be2870.ccr41.lon13.atlas.cogentco.com [154.54.58.173]
10 78 ms 77 ms 78 ms be2982.ccr21.bos01.atlas.cogentco.com [154.54.1.117]
11 77 ms 78 ms 78 ms be2299.ccr21.alb02.atlas.cogentco.com [154.54.43.10]
12 84 ms 84 ms 84 ms be2088.ccr21.ymq01.atlas.cogentco.com [154.54.43.17]
13 84 ms 88 ms 83 ms hu0-4-0-0.ccr21.ymq02.atlas.cogentco.com [154.54.25.125]
14 83 ms 84 ms 83 ms 38.122.42.34
15 * * * Request timed out.
16 90 ms 90 ms 96 ms 192.34.76.2
17 90 ms 89 ms 89 ms 199.91.189.234
18 89 ms 89 ms 89 ms 199.91.189.27

Trace complete.

[FFXray]

Name of your Internet Service Provider (ISP): Time Warner Cable
Ticket or reference number from your ISP: N/A Verified with Timer Warner they are stating issue does not reside with them.
State/Country: Ohio/United States of America
Date/Time (When did the issue start happening, at what specific times does this issue arise, if any.): Post Patch 3.35
Frequency (How often does the issue occur?): Every 10 to 15 seconds while logged in
Content (Which content were you playing in-game when the issue occurred?): Happens with all game activity
Which in-game World were you playing on when the issue occurred: Hyperion

Tracing route to 199.91.189.38 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.0.1
2 18 ms 11 ms 9 ms 142.254.144.85
3 32 ms 30 ms 35 ms 24.29.0.153
4 14 ms 14 ms 21 ms be26.blasohdp01r.midwest.rr.com [65.29.37.236]
5 18 ms 24 ms 16 ms be28.clmkohpe01r.midwest.rr.com [65.29.1.44]
6 27 ms 32 ms 38 ms bu-ether45.chctilwc00w-bcr00.tbone.rr.com [107.14.19.36]
7 24 ms 25 ms 36 ms 0.ae1.pr0.chi30.tbone.rr.com [66.109.1.78]
8 * * 25 ms lag-12.ear2.Chicago2.Level3.net [4.68.111.17]
9 45 ms 46 ms 46 ms ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]
10 44 ms 44 ms 45 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.74]
11 * * * Request timed out.
12 48 ms 44 ms 46 ms 192.34.76.2
13 49 ms 42 ms 42 ms 199.91.189.234
14 43 ms 43 ms 52 ms 199.91.189.38

[akazulol]

Name of your Internet Service Provider (ISP) Net Virtua
State/Country Brazil
Date/Time (When did the issue start happening, at what specific times does this issue arise, if any.) Start around 2 weeks ago, happens all the time
Frequency (How often does the issue occur?) throughout the day
Content (Which content were you playing in-game when the issue occurred?) Any content
Which in-game World were you playing on when the issue occurred? Gilgamesh
Traceroute records (optional) (Learn how to generate traceroute record)

Tracing route to 199.91.189.30 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.0.1
2 27 ms 21 ms 43 ms b18e8001.virtua.com.br [177.142.128.1]
3 12 ms 12 ms 31 ms c9112102.virtua.com.br [201.17.33.2]
4 13 ms 10 ms 12 ms c91122c1.virtua.com.br [201.17.34.193]
5 14 ms 13 ms 14 ms c9110009.virtua.com.br [201.17.0.9]
6 14 ms 19 ms 14 ms embratel-T0-0-2-0-tacc01.rjo.embratel.net.br [200.209.203.33]
7 130 ms 130 ms 130 ms ebt-T0-8-0-12-tcore01.rjo.embratel.net.br [200.244.216.50]
8 129 ms 129 ms 131 ms ebt-BP1211-intl01.nyk.embratel.net.br [200.230.220.42]
9 * * * Request timed out.
10 141 ms 138 ms 152 ms ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]
11 137 ms 140 ms 137 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.74]
12 * * * Request timed out.
13 128 ms 128 ms 128 ms 192.34.76.2
14 128 ms 125 ms 125 ms 199.91.189.234
15 136 ms 138 ms 137 ms 199.91.189.30

Trace complete.

[pyra]

Name of your Internet Service Provider (ISP) - WaveG

Ticket or reference number from your ISP. - #495026

State/Country - Seattle, WA, USA

Date/Time (When did the issue start happening, at what specific times does this issue arise, if any.) - First noticed on July 19, but it would clear up in an hour. Now, it is constant, and I've seen the issue happen anywhere from 8am to 11pm PST

Frequency (How often does the issue occur?) - Dungeons are especially bad. This week I have not been able to run any instance w/o D/Cing. Also this week, it has started to affect me in the world.

Content (Which content were you playing in-game when the issue occurred?) - Beast Tribe Daily quests, Palace of the Dead, Hullbreaker (Hard)

Which in-game World were you playing on when the issue occurred? - Balmung
Traceroute records

  1     1 ms    <1 ms     1 ms  10.0.1.1
  2     1 ms     1 ms     2 ms  174.127.174.1
  3     1 ms     1 ms     3 ms  agg2-sea-a-t6-1-4000.bb.spectrumnet.us [216.243.28.205]
  4     2 ms     3 ms     3 ms  cr2-sea-b-te-0-0-0-20.bb.spectrumnet.us [174.127.140.137]
  5     2 ms     4 ms     5 ms  te0-7-0-32.ccr21.sea02.atlas.cogentco.com [38.104.126.57]
  6    22 ms    23 ms    23 ms  be2085.ccr21.slc01.atlas.cogentco.com [154.54.2.198]
  7    32 ms    33 ms    33 ms  be3037.ccr21.den01.atlas.cogentco.com [154.54.41.146]
  8    45 ms    43 ms    43 ms  be3035.ccr21.mci01.atlas.cogentco.com [154.54.5.90]
  9    57 ms    56 ms    56 ms  be2831.ccr41.ord01.atlas.cogentco.com [154.54.42.166]
 10    62 ms    63 ms    64 ms  be2717.ccr21.cle04.atlas.cogentco.com [154.54.6.222]
 11    70 ms    71 ms    71 ms  be2993.ccr21.yyz02.atlas.cogentco.com [154.54.31.226]
 12    78 ms    77 ms    78 ms  be2090.ccr21.ymq01.atlas.cogentco.com [154.54.30.206]
 13    78 ms    77 ms    78 ms  hu0-4-0-0.ccr21.ymq02.atlas.cogentco.com [154.54.25.125]
 14    78 ms    77 ms    77 ms  38.122.42.34
 15     *        *        *     Request timed out.
 16    71 ms    71 ms    70 ms  192.34.76.2
 17    71 ms    71 ms    71 ms  199.91.189.234
 18    72 ms    71 ms    71 ms  199.91.189.31

The issue seems to be with Congent. In general, I've found they suck. My ISP will reroute the traffic over a different backbone, but they said I have to prove that it would fix the problem.