Reporting Issues Resulting from the North American Data Center Relocation

[Danblognivalodi]

Type of Issue/Feedback: Getting packet loss
Name of your Internet Service Provider (ISP): Claro
State/Country: Bogota, Colombia
Date/Time: 1/12/2017
World Name: Hyperion
Frequency: Mostly all the at nigth between 7-11 pm EST
Traceroute records

Traza a 204.2.229.10 sobre caminos de 30 saltos como máximo.

1 <1 ms <1 ms <1 ms 192.168.0.1
2 20 ms 22 ms 17 ms 100.64.30.1
3 17 ms 24 ms 20 ms 172.21.18.58
4 * * 20 ms 10.14.20.78
5 22 ms 18 ms 31 ms 10.14.16.129
6 * * * Tiempo de espera agotado para esta solicitud.
7 39 ms 33 ms 28 ms 10.14.18.25
8 102 ms 87 ms 92 ms ix-et-10-0-5-0.tcore1.MLN-Miami.as6453.net [66.110.9.197]
9 88 ms 59 ms 59 ms ae-6.a00.miamfl02.us.bb.gin.ntt.net [129.250.9.33]
10 145 ms 136 ms 148 ms ae-4.r05.miamfl02.us.bb.gin.ntt.net [129.250.3.40]
11 61 ms 60 ms 85 ms ae-4.r20.miamfl02.us.bb.gin.ntt.net [129.250.2.184]
12 111 ms * 106 ms ae-4.r23.asbnva02.us.bb.gin.ntt.net [129.250.2.86]
13 * 153 ms 153 ms ae-10.r22.snjsca04.us.bb.gin.ntt.net [129.250.6.237]
14 144 ms 143 ms 140 ms ae-19.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.27]
15 142 ms 165 ms 144 ms ae-1.a00.snjsca04.us.bb.gin.ntt.net [129.250.2.228]
16 150 ms 147 ms 144 ms xe-0-0-42-1.a00.snjsca04.us.ce.gin.ntt.net [129.250.195.42]
17 * 151 ms 158 ms 204.2.229.242
18 144 ms 139 ms 145 ms 204.2.229.10

Traza completa.


Traza a 204.2.229.10 sobre caminos de 30 saltos como máximo.

1 <1 ms <1 ms <1 ms 192.168.0.1
2 25 ms 23 ms 31 ms 100.64.30.1
3 43 ms 20 ms 23 ms 172.21.18.58
4 * 24 ms 15 ms 10.14.20.78
5 18 ms 15 ms 22 ms 10.14.16.129
6 * * * Tiempo de espera agotado para esta solicitud.
7 27 ms 29 ms 31 ms 10.14.18.25
8 85 ms 111 ms 90 ms ix-et-10-0-5-0.tcore1.MLN-Miami.as6453.net [66.110.9.197]
9 73 ms 82 ms 80 ms ae-6.a00.miamfl02.us.bb.gin.ntt.net [129.250.9.33]
10 142 ms 139 ms 155 ms ae-4.r05.miamfl02.us.bb.gin.ntt.net [129.250.3.40]
11 60 ms * 108 ms ae-4.r20.miamfl02.us.bb.gin.ntt.net [129.250.2.184]
12 105 ms 104 ms * ae-4.r23.asbnva02.us.bb.gin.ntt.net [129.250.2.86]
13 224 ms 148 ms 166 ms ae-10.r22.snjsca04.us.bb.gin.ntt.net [129.250.6.237]
14 154 ms 143 ms 146 ms ae-19.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.27]
15 173 ms 153 ms 148 ms ae-1.a00.snjsca04.us.bb.gin.ntt.net [129.250.2.228]
16 143 ms 150 ms 149 ms xe-0-0-42-1.a00.snjsca04.us.ce.gin.ntt.net [129.250.195.42]
17 * 144 ms * 204.2.229.242
18 156 ms 142 ms 151 ms 204.2.229.10

Traza completa.


Traza a 204.2.229.10 sobre caminos de 30 saltos como máximo.

1 <1 ms <1 ms <1 ms 192.168.0.1
2 49 ms 56 ms 21 ms 100.64.30.1
3 23 ms 21 ms 18 ms 172.21.18.58
4 23 ms 43 ms 27 ms 10.14.20.78
5 22 ms 20 ms 19 ms 10.14.16.129
6 * * * Tiempo de espera agotado para esta solicitud.
7 44 ms 63 ms 48 ms 10.14.18.25
8 90 ms 89 ms 121 ms ix-et-10-0-5-0.tcore1.MLN-Miami.as6453.net [66.110.9.197]
9 * 58 ms 63 ms ae-6.a00.miamfl02.us.bb.gin.ntt.net [129.250.9.33]
10 * 140 ms 154 ms ae-4.r05.miamfl02.us.bb.gin.ntt.net [129.250.3.40]
11 64 ms 55 ms 78 ms ae-4.r20.miamfl02.us.bb.gin.ntt.net [129.250.2.184]
12 106 ms 110 ms 111 ms ae-4.r23.asbnva02.us.bb.gin.ntt.net [129.250.2.86]
13 146 ms 142 ms 143 ms ae-10.r22.snjsca04.us.bb.gin.ntt.net [129.250.6.237]
14 172 ms 144 ms 143 ms ae-19.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.27]
15 145 ms 169 ms 148 ms ae-1.a00.snjsca04.us.bb.gin.ntt.net [129.250.2.228]
16 154 ms 146 ms 160 ms xe-0-0-42-1.a00.snjsca04.us.ce.gin.ntt.net [129.250.195.42]
17 162 ms * 189 ms 204.2.229.242
18 143 ms 148 ms 153 ms 204.2.229.10

Traza completa.

Notes: Pretty common packet loss at router 204.2.229.242, I'm aware of the other packet loss from my ISP, but also that destination router has a problem, please fix that router, I'm not the only one with packet loss from that one. Is that what we pay sub for? I'm seriously thinking into quiting this game, since it's getting literally unplayable from south america.

[Kazgrel]

Only two routes ever see * is 204.2.229.242 and 204.2.229.234. They need to fix these two spots that constantly having time outs or not use them.

I am also observing the same thing starting about 2 weeks ago. I'll red line in game and eventually 90k anywhere from 30 seconds to 3 mins after the red line initially shows next to my character. It's been like this every day since, and I'm starting to contemplate cancelling my sub until 4.2 at least. I can't do anything in game outside of check retainers and gardens without having this happen. Heck, it happened at 2 AM my time in the Gold Saucer when I went to play mini cactpot, so it's not a server stress issue.

[Qephire]

Connection to this game has been crap since the move I've been patient but a +300% boost in ping is not "an ever-improving game experience". And don't get me started on the lag spikes.

Apparently you guys have service agreement with NTT since it's their network that is causing the issues how about leveraging that.



Type of Issue/Feedback: Ping increased by 311% not kidding
Name of your Internet Service Provider (ISP): Comcast
State/Country: Maryland/USA
Date/Time: Since the server move that provided "an ever-improving game experience"
World Name: Midgardsormr
Frequency: Always
Traceroute:

Tracing route to 204.2.229.89 over a maximum of 30 hops

1 3 ms 5 ms 3 ms 10.0.0.1
2 24 ms 14 ms 13 ms 96.120.105.157
3 19 ms 18 ms 19 ms xe-4-3-0-sur01.salisbury.md.bad.comcast.net [68.85.147.73]
4 17 ms 18 ms 25 ms ae-41-ar01.capitolhghts.md.bad.comcast.net [68.87.136.185]
5 22 ms 27 ms 24 ms be-33657-cr02.ashburn.va.ibone.comcast.net [68.86.90.57]
6 21 ms 22 ms 22 ms hu-0-10-0-7-pe07.ashburn.va.ibone.comcast.net [68.86.86.54]
7 126 ms 118 ms 102 ms ae-16.a02.asbnva02.us.bb.gin.ntt.net [129.250.66.49]
8 208 ms 209 ms 195 ms ae-69.r06.asbnva02.us.bb.gin.ntt.net [129.250.5.193]
9 82 ms 98 ms 63 ms ae-2.r23.asbnva02.us.bb.gin.ntt.net [129.250.2.132]
10 * 212 ms * ae-10.r22.snjsca04.us.bb.gin.ntt.net [129.250.6.237]
11 172 ms 180 ms 174 ms ae-19.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.27]
12 189 ms 200 ms 198 ms ae-1.a00.snjsca04.us.bb.gin.ntt.net [129.250.2.228]
13 172 ms 172 ms 185 ms xe-0-0-42-1.a00.snjsca04.us.ce.gin.ntt.net [129.250.195.42]
14 * 176 ms 188 ms 204.2.229.242
15 164 ms 173 ms 174 ms 204.2.229.89

Trace complete.

C:\Windows\system32>ping 204.2.229.89 -t

Pinging 204.2.229.89 with 32 bytes of data:
Reply from 204.2.229.89: bytes=32 time=173ms TTL=47
Reply from 204.2.229.89: bytes=32 time=179ms TTL=47
Reply from 204.2.229.89: bytes=32 time=173ms TTL=47
Reply from 204.2.229.89: bytes=32 time=179ms TTL=47
Reply from 204.2.229.89: bytes=32 time=170ms TTL=47
Reply from 204.2.229.89: bytes=32 time=177ms TTL=47
Reply from 204.2.229.89: bytes=32 time=201ms TTL=47
Reply from 204.2.229.89: bytes=32 time=178ms TTL=47
Reply from 204.2.229.89: bytes=32 time=160ms TTL=47
Reply from 204.2.229.89: bytes=32 time=157ms TTL=47
Reply from 204.2.229.89: bytes=32 time=181ms TTL=47
Reply from 204.2.229.89: bytes=32 time=197ms TTL=47
Reply from 204.2.229.89: bytes=32 time=178ms TTL=47
Reply from 204.2.229.89: bytes=32 time=190ms TTL=47
Reply from 204.2.229.89: bytes=32 time=173ms TTL=47
Reply from 204.2.229.89: bytes=32 time=194ms TTL=47
Reply from 204.2.229.89: bytes=32 time=181ms TTL=47
Reply from 204.2.229.89: bytes=32 time=213ms TTL=47
Reply from 204.2.229.89: bytes=32 time=191ms TTL=47
Reply from 204.2.229.89: bytes=32 time=190ms TTL=47
Reply from 204.2.229.89: bytes=32 time=195ms TTL=47
Reply from 204.2.229.89: bytes=32 time=213ms TTL=47
Reply from 204.2.229.89: bytes=32 time=196ms TTL=47
Reply from 204.2.229.89: bytes=32 time=191ms TTL=47
Reply from 204.2.229.89: bytes=32 time=196ms TTL=47
Reply from 204.2.229.89: bytes=32 time=176ms TTL=47
Reply from 204.2.229.89: bytes=32 time=191ms TTL=47
Reply from 204.2.229.89: bytes=32 time=179ms TTL=47
Reply from 204.2.229.89: bytes=32 time=173ms TTL=47
Reply from 204.2.229.89: bytes=32 time=181ms TTL=47
Reply from 204.2.229.89: bytes=32 time=178ms TTL=47
Reply from 204.2.229.89: bytes=32 time=196ms TTL=47
Reply from 204.2.229.89: bytes=32 time=183ms TTL=47
Reply from 204.2.229.89: bytes=32 time=200ms TTL=47
Reply from 204.2.229.89: bytes=32 time=187ms TTL=47
Reply from 204.2.229.89: bytes=32 time=181ms TTL=47
Reply from 204.2.229.89: bytes=32 time=183ms TTL=47
Reply from 204.2.229.89: bytes=32 time=195ms TTL=47
Reply from 204.2.229.89: bytes=32 time=187ms TTL=47
Reply from 204.2.229.89: bytes=32 time=185ms TTL=47
Reply from 204.2.229.89: bytes=32 time=190ms TTL=47
Reply from 204.2.229.89: bytes=32 time=198ms TTL=47
Reply from 204.2.229.89: bytes=32 time=186ms TTL=47
Reply from 204.2.229.89: bytes=32 time=192ms TTL=47

Ping statistics for 204.2.229.89:
Packets: Sent = 44, Received = 44, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 157ms, Maximum = 213ms, Average = 185ms