High ping only on FFXIV

[Veritas1980]

I recently started getting high ping 1500-3000 receiving. below is some MTR data that I have collected:

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 10.21.55.1 - 0 | 95 | 95 | 0 | 0 | 1 | 0 |
| 50.220.234.105 - 0 | 95 | 95 | 0 | 0 | 5 | 0 |
| 68.85.244.25 - 0 | 95 | 95 | 1 | 4 | 23 | 1 |
|be-501-arsc1.bisbee.tx.houston.comcast.net - 0 | 95 | 95 | 2 | 5 | 171 | 2 |
|be-35421-cs02.houston.tx.ibone.comcast.net - 0 | 95 | 95 | 2 | 3 | 17 | 3 |
|be-1211-cr11.houston.tx.ibone.comcast.net - 0 | 95 | 95 | 2 | 2 | 4 | 3 |
| be-302-cr11.dallas.tx.ibone.comcast.net - 0 | 95 | 95 | 7 | 7 | 8 | 7 |
|be-1211-cs02.dallas.tx.ibone.comcast.net - 0 | 95 | 95 | 7 | 7 | 9 | 7 |
|be-3212-pe12.1950stemmons.tx.ibone.comcast.net - 0 | 95 | 95 | 7 | 7 | 9 | 7 |
| 50.248.117.186 - 0 | 95 | 95 | 7 | 9 | 37 | 15 |
| ae-2.r20.dllstx14.us.bb.gin.ntt.net - 40 | 35 | 21 | 18 | 21 | 33 | 25 |
| ae-2.r24.lsanca07.us.bb.gin.ntt.net - 4 | 83 | 80 | 0 | 42 | 69 | 41 |
| ae-5.r01.scrmca02.us.bb.gin.ntt.net - 0 | 95 | 95 | 44 | 44 | 46 | 44 |
| ae-1.r00.scrmca02.us.bb.gin.ntt.net - 0 | 95 | 95 | 44 | 44 | 46 | 44 |
|xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net - 0 | 95 | 95 | 44 | 44 | 47 | 44 |
| 204.2.229.230 - 74 | 23 | 6 | 44 | 44 | 44 | 44 |
| 204.2.229.9 - 0 | 95 | 95 | 44 | 44 | 46 | 44 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider


that is some pretty severe packet loss. I am on a gigabit connection. this appears to be a routing issue.

NOTE: I have notified my ISP also, as the issue appears to start where the comcast network meets NTT.

[Myric]

I live just outside Sacramento, so I'm like 30 minutes away from the servers. I'm usually at 12 to 15 ping, but today I'm at 70 to 98 with packet loss.

Tracing route to 204.2.229.9 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.0.1
2 10 ms 11 ms 8 ms 76-14-128-1.rk.wavecable.com [76.14.128.1]
3 13 ms 9 ms 8 ms cr1-rhe-a-be153.bb.as11404.net [174.127.183.14]
4 8 ms 7 ms 16 ms be20.cr3-rhe.bb.as11404.net [192.175.29.238]
5 8 ms 9 ms 9 ms be1.cr4-rhe.bb.as11404.net [192.175.29.229]
6 12 ms 7 ms 10 ms be11.cr3-wsache.bb.as11404.net [192.175.30.202]
7 10 ms 9 ms 13 ms be1.cr4-wsache.bb.as11404.net [192.175.30.127]
8 10 ms 9 ms 9 ms be13.cr1-1075triangle.bb.as11404.net [192.175.30.209]
9 * 16 ms 14 ms lag-101.bear2.Sacramento1.Level3.net [4.53.204.29]
10 * * * Request timed out.
11 14 ms 12 ms 14 ms NTT-level3-SanJose1.Level3.net [4.68.63.114]
12 98 ms 100 ms 100 ms ae-11.r24.snjsca04.us.bb.gin.ntt.net [129.250.3.120]
13 101 ms 97 ms 100 ms ae-4.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.57]
14 104 ms * 116 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [192.80.16.2]
15 * * 101 ms 204.2.229.230
16 90 ms 98 ms 90 ms 204.2.229.9

Trace complete.