Reporting Issues Resulting from the North American Data Center Relocation

[Bariaus]

...

Dude. You're having 2x ms avg., what are you talking about. Also, Windows Network Monitor is bs. Been using a VPN which shows me the real ms tracking, while the thing you're using is showing a completely different thing.

[NinuSkeith]

Type of Issue/Feedback: Lag, disconnects (90006)
Name of your Internet Service Provider (ISP): Spectrum (Formerly Oceanic Time Warner Cable)
State/Country: Honolulu, Hawaii
Date/Time: For the last ten days
World Name: Sargantanas
Frequency: Varies, but generally hits in the evening (8:30-10pm HST)
Traceroute:

Tracing route to 204.2.229.9 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms READYSHARE [192.168.1.1]
2 9 ms 8 ms 8 ms 142.254.190.133
3 31 ms 21 ms 22 ms xe-0-0-8.hnllhikm01h.hawaii.rr.com [24.25.229.49]
4 10 ms 11 ms 11 ms agg32.milnhixd01r.hawaii.rr.com [72.129.46.54]
5 62 ms 62 ms 63 ms agg31.lsancarc01r.socal.rr.com [72.129.45.0]
6 63 ms 69 ms 63 ms bu-ether26.lsancarc0yw-bcr00.tbone.rr.com [66.109.3.230]
7 57 ms 57 ms 57 ms ae2.lsancarc0yw-bpr01.tbone.rr.com [66.109.1.41]

8 59 ms 58 ms 59 ms ix-ae-24-0.tcore1.LVW-Los-Angeles.as6453.net [66.110.59.81]
9 60 ms 57 ms 57 ms if-ae-2-2.tcore2.LVW-Los-Angeles.as6453.net [66.110.59.2]
10 97 ms 74 ms 78 ms 64.86.252.134
11 84 ms * 82 ms ae-19.r00.lsanca07.us.bb.gin.ntt.net [129.250.3.235]
12 73 ms 66 ms 64 ms ae-2.r23.lsanca07.us.bb.gin.ntt.net [129.250.3.237]
13 * 76 ms * ae-12.r22.snjsca04.us.bb.gin.ntt.net [129.250.4.150]
14 78 ms * * ae-19.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.27]
15 186 ms 175 ms 175 ms ae-1.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.31]
16 * 92 ms * xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
17 80 ms * * 204.2.229.234
18 * 77 ms 78 ms 204.2.229.9

Trace complete.

It's pretty clear that the issue is on the ISP. Maybe Square can start making angry phone calls to whoever owns the network infrastructure around there?

[Monkey404error]

Type of Issue/Feedback: Lag, disconnects (90006)
Name of your Internet Service Provider (ISP): Spectrum (Formerly Oceanic Time Warner Cable)
State/Country: San Antonio,TX
Date/Time: Just noticed Oct. 13
World Name: Jenova
Frequency: unknown, but happening constantly since 03:00 (currently 04:30 local)
Traceroute:

1 router.asus.com (192.168.1.1) 2.264 ms 1.971 ms 2.032 ms
2 * * *
3 tge0-0-0.snaxtxfq02h.texas.rr.com (24.28.132.105) 25.967 ms 29.823 ms 33.007 ms
4 agg31.snaptxwm02r.texas.rr.com (24.175.33.124) 20.018 ms 11.638 ms 20.412 ms
5 agg23.snantxvy01r.texas.rr.com (24.175.32.184) 15.629 ms 11.110 ms 20.102 ms
6 agg23.dllatxl301r.texas.rr.com (24.175.32.146) 23.237 ms 22.704 ms 20.081 ms
7 66.109.1.216 (66.109.1.216) 30.658 ms
bu-ether14.dllstx976iw-bcr00.tbone.rr.com (66.109.6.88) 25.981 ms
66.109.1.216 (66.109.1.216) 30.567 ms
8 0.ae2.pr1.dfw10.tbone.rr.com (107.14.17.236) 24.661 ms
0.ae4.pr1.dfw10.tbone.rr.com (107.14.19.97) 28.292 ms
0.ae1.pr1.dfw10.tbone.rr.com (107.14.17.234) 25.639 ms
9 ix-ae-23-0.tcore2.dt8-dallas.as6453.net (66.110.57.97) 18.928 ms 22.071 ms 20.618 ms
10 if-ae-2-2.tcore1.dt8-dallas.as6453.net (66.110.56.5) 55.656 ms 57.224 ms 64.032 ms
11 if-ae-23-2.tcore2.ct8-chicago.as6453.net (64.86.79.120) 63.036 ms 59.966 ms 59.549 ms
12 if-ae-3-2.tcore1.w6c-montreal.as6453.net (66.198.96.45) 64.120 ms 56.623 ms 55.726 ms
13 66.198.96.58 (66.198.96.58) 58.603 ms 57.517 ms 59.592 ms
14 te7-3.dr9.mtl.iweb.com (67.205.127.214) 65.097 ms 55.760 ms 55.667 ms
15 174.142.115.218 (174.142.115.218) 59.934 ms 64.071 ms 60.080 ms
16 * * *
17 * * *
18 * * *
19 * * *


Also, should be noted, when running a constant ping, I get spikes north of 100ms+ when average is 60:

64 bytes from 184.107.107.176: icmp_seq=61 ttl=49 time=61.037 ms
64 bytes from 184.107.107.176: icmp_seq=62 ttl=49 time=58.395 ms
64 bytes from 184.107.107.176: icmp_seq=63 ttl=49 time=167.572 ms
64 bytes from 184.107.107.176: icmp_seq=64 ttl=49 time=104.449 ms
64 bytes from 184.107.107.176: icmp_seq=65 ttl=49 time=139.766 ms
64 bytes from 184.107.107.176: icmp_seq=66 ttl=49 time=64.244 ms
64 bytes from 184.107.107.176: icmp_seq=67 ttl=49 time=106.503 ms
64 bytes from 184.107.107.176: icmp_seq=68 ttl=49 time=63.385 ms
64 bytes from 184.107.107.176: icmp_seq=69 ttl=49 time=62.567 ms
64 bytes from 184.107.107.176: icmp_seq=70 ttl=49 time=130.218 ms
64 bytes from 184.107.107.176: icmp_seq=71 ttl=49 time=65.500 ms
64 bytes from 184.107.107.176: icmp_seq=72 ttl=49 time=62.509 ms
64 bytes from 184.107.107.176: icmp_seq=73 ttl=49 time=118.963 ms
64 bytes from 184.107.107.176: icmp_seq=74 ttl=49 time=61.354 ms
--- 184.107.107.176 ping statistics ---
97 packets transmitted, 97 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 54.003/63.685/167.572/17.864 ms

Edit: Errors being received include 90006, 90002, and 10105

[Riko_Futatabi]

Things that I've previously tried and had no effect are: Reducing MTU size, port forwarding, changing DNS servers, disabling UPnP in FFXIV config and even resetting my game settings to default along with lowering my graphic settings. All this was the advice given to me via E-Mail with SE customer support. My ISP noticed no faults with my line, everything outside FFXIV is working fine. They even sent me a new router to see if that would have helped, but unfortunately it did not.

Type of Issue/Feedback: Lag spikes are constant in all locations in game. Also known as "rubber-banding". Everything will stop for a few seconds and then fast-forward to the current moment. Occasionally lasting up to 10~15 seconds and if it's longer I usually get booted to the login screen with error 90006.
Name of your Internet Service Provider (ISP): Sky
State/Country: Scotland, UK.
Date/Time: After patch 4.06a this started happening and has been constant throughout the day. Especially noticeable at the weekends, due to the increased traffic I'd assume.
World Name: Excalibur
Frequency: It's something I have to deal with constantly now.

This is my route to the Primal Data Center(Ignore hop #2, it's normal). The issue seems to be with nodes #6, #7, #8. Also since 4.1 I've noticed that the SE Lobby server is now experiencing packet loss.

This was monitored at 21:30 GMT on Saturday. During or approaching peak time on my server.

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                          SkyRouter.Home -    0 |  123 |  123 |    0 |    0 |    3 |    2 |
|                   No response from host -  100 |   25 |    0 |    0 |    0 |    0 |    0 |
|             be365.pr2.hobir.isp.sky.com -    0 |  123 |  123 |   16 |   17 |   20 |   18 |
|     ae-3.r02.londen03.uk.bb.gin.ntt.net -    0 |  123 |  123 |   16 |   17 |   21 |   17 |
|     ae-3.r24.londen12.uk.bb.gin.ntt.net -    0 |  123 |  123 |   16 |   17 |   24 |   19 |
|     ae-5.r24.nycmny01.us.bb.gin.ntt.net -   31 |   55 |   38 |   82 |   82 |   96 |   82 |
|     ae-2.r20.sttlwa01.us.bb.gin.ntt.net -   30 |   58 |   41 |    0 |  156 |  198 |  153 |
|     ae-0.r21.sttlwa01.us.bb.gin.ntt.net -   30 |   58 |   41 |    0 |  142 |  156 |  142 |
|     ae-3.r23.snjsca04.us.bb.gin.ntt.net -    0 |  123 |  123 |  163 |  164 |  197 |  163 |
|    ae-45.r01.snjsca04.us.bb.gin.ntt.net -    0 |  123 |  123 |  163 |  164 |  169 |  164 |
|     ae-1.r00.scrmca02.us.bb.gin.ntt.net -    0 |  123 |  123 |  167 |  167 |  170 |  167 |
|xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net -    0 |  123 |  123 |  170 |  170 |  175 |  170 |
|                           204.2.229.234 -   26 |   63 |   47 |  169 |  169 |  173 |  170 |
|                            204.2.229.10 -    0 |  123 |  123 |  167 |  168 |  173 |  168 |
|________________________________________________|______|______|______|______|______|______|

I've had this issue for around 45 days now. The game is becoming less and less fun due to it. The new content you add means little to me if I cannot reliably participate in it. I've been incredibly patient the past few weeks, I hope you can resolve this. Thanks.