Reporting Latency Related Issue (NA Data Center)

[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.

[BlueHokage]

Name of your Internet Service Provider (ISP): Comcast

Ticket or reference number from your ISP: N/A. Issue is with the Network Transport (Level-3) that Comcast's Network Architect decided to use.

State/Country: CA, USA (Bay Area, Internet capital of the world)

Date/Time: Every day, 5:30pm-ish until approx 10:00pm (peak hours of Netflix and chill)

Frequency (How often does the issue occur?): Every day. I want to say the issue began around late November (around the time of the Ninja mudra "fix")

Content (Which content were you playing in-game when the issue occurred?): All content, but most noticeable in instances across the Duty Finder (Raid, PVP, Dungeons).

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

Traceroute record (during problem hours):

Tracing route to 199.91.189.23 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 10.0.0.1
2 9 ms 8 ms 8 ms 96.120.89.109
3 10 ms 8 ms 8 ms be-20006-sur04.rohnertpr.ca.sfba.comcast.net [162.151.31.73]
4 10 ms 10 ms 11 ms be-306-rar01.fairfield.ca.sfba.comcast.net [162.151.79.65]
5 12 ms 12 ms 12 ms hu-0-18-0-3-ar01.hayward.ca.sfba.comcast.net [68.85.154.181]
6 27 ms 13 ms 12 ms lag-14.ear2.SanJose1.Level3.net [4.68.72.101]
7 153 ms 113 ms 202 ms ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]
8 81 ms 81 ms 81 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.74]
9 79 ms 79 ms 79 ms 10.2.0.1
10 80 ms 80 ms 80 ms 192.34.76.2
11 79 ms 79 ms 79 ms 199.91.189.234
12 80 ms 80 ms 79 ms 199.91.189.23

Trace complete.

Multiple Traceroutes bring up similar results.
It's obvious that the transport that Level 3 is using between San Jose to Montreal is where the problem seems to appear (and looking at other FFXIV-users TR results, show very similar results to one of the various Montreal hops).

Comcast's NOC refuses to open a Trouble Ticket to their Transport provider, and there is no way for me to open a Ticket with Level-3, as I am not their direct customer (this is something I frequently was able to do on an instance-per-instance basis, back when I was previously employed with a certain Network Provider).

And here are some ping responses to that IP in Montreal:

Pinging 4.69.153.86 with 32 bytes of data:
Reply from 4.69.153.86: bytes=32 time=81ms TTL=243
Reply from 4.69.153.86: bytes=32 time=94ms TTL=243
Reply from 4.69.153.86: bytes=32 time=83ms TTL=243
Reply from 4.69.153.86: bytes=32 time=156ms TTL=243
Reply from 4.69.153.86: bytes=32 time=267ms TTL=243
Reply from 4.69.153.86: bytes=32 time=184ms TTL=243
Reply from 4.69.153.86: bytes=32 time=203ms TTL=243
Reply from 4.69.153.86: bytes=32 time=140ms TTL=243
Reply from 4.69.153.86: bytes=32 time=303ms TTL=243
Reply from 4.69.153.86: bytes=32 time=341ms TTL=243
Reply from 4.69.153.86: bytes=32 time=217ms TTL=243
Reply from 4.69.153.86: bytes=32 time=253ms TTL=243
Reply from 4.69.153.86: bytes=32 time=88ms TTL=243
Reply from 4.69.153.86: bytes=32 time=112ms TTL=243
Reply from 4.69.153.86: bytes=32 time=88ms TTL=243
Reply from 4.69.153.86: bytes=32 time=126ms TTL=243
Reply from 4.69.153.86: bytes=32 time=149ms TTL=243
Reply from 4.69.153.86: bytes=32 time=81ms TTL=243
Reply from 4.69.153.86: bytes=32 time=81ms TTL=243
Reply from 4.69.153.86: bytes=32 time=81ms TTL=243
Reply from 4.69.153.86: bytes=32 time=81ms TTL=243

Ping statistics for 4.69.153.86:
Packets: Sent = 21, Received = 21, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 81ms, Maximum = 341ms, Average = 152ms