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