Reporting Latency Related Issue (NA Data Center)

[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