Possible explaination for the high latency (after doing a tracert)

[Flarestar]

1 <1 ms <1 ms <1 ms USG [192.168.1.1]
2 1 ms <1 ms <1 ms 192.168.41.1
3 2 ms 1 ms 2 ms 104-50-196-1.lightspeed.knvltn.sbcglobal.net [104.50.196.1]
4 3 ms 2 ms 2 ms 99.17.140.246
5 * * * Request timed out.
6 3 ms 3 ms 3 ms 12.83.114.137
7 19 ms 22 ms 15 ms attga402igs.ip.att.net [12.122.117.121]
8 20 ms 46 ms 16 ms 192.205.36.158
9 29 ms 26 ms 22 ms ae-16.r22.atlnga05.us.bb.gin.ntt.net [129.250.5.57]
10 33 ms 33 ms 33 ms ae-6.r21.dllstx14.us.bb.gin.ntt.net [129.250.4.116]
11 75 ms 73 ms 75 ms ae-2.r25.snjsca04.us.bb.gin.ntt.net [129.250.4.154]
12 215 ms 229 ms 227 ms ae-5.r24.snjsca04.us.bb.gin.ntt.net [129.250.3.146]
13 190 ms 193 ms 214 ms ae-4.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.57]
14 230 ms 214 ms 230 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [192.80.16.2]
15 * 208 ms * 204.2.229.230
16 181 ms 193 ms 234 ms 204.2.229.10

That 204.2.229.230 address constantly shows dropped packets for me in the evening when I do a tracert to Primal. I'm in Eastern TN. This has happened every evening since Patch 6.01 went live.

[Brunas]

1 <1 ms <1 ms <1 ms USG [192.168.1.1]
2 1 ms <1 ms <1 ms 192.168.41.1
3 2 ms 1 ms 2 ms 104-50-196-1.lightspeed.knvltn.sbcglobal.net [104.50.196.1]
4 3 ms 2 ms 2 ms 99.17.140.246
5 * * * Request timed out.
6 3 ms 3 ms 3 ms 12.83.114.137
7 19 ms 22 ms 15 ms attga402igs.ip.att.net [12.122.117.121]
8 20 ms 46 ms 16 ms 192.205.36.158
9 29 ms 26 ms 22 ms ae-16.r22.atlnga05.us.bb.gin.ntt.net [129.250.5.57]
10 33 ms 33 ms 33 ms ae-6.r21.dllstx14.us.bb.gin.ntt.net [129.250.4.116]
11 75 ms 73 ms 75 ms ae-2.r25.snjsca04.us.bb.gin.ntt.net [129.250.4.154]
12 215 ms 229 ms 227 ms ae-5.r24.snjsca04.us.bb.gin.ntt.net [129.250.3.146]
13 190 ms 193 ms 214 ms ae-4.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.57]
14 230 ms 214 ms 230 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [192.80.16.2]
15 * 208 ms * 204.2.229.230
16 181 ms 193 ms 234 ms 204.2.229.10

That 204.2.229.230 address constantly shows dropped packets for me in the evening when I do a tracert to Primal. I'm in Eastern TN. This has happened every evening since Patch 6.01 went live.

Similar story for me in Central NC. Family in Eastern NC reporting similar issues. Very consistent either high latency or packet loss - haven't had a chance to sort out which yet, but the symptom is very consistent 1-2 second spikes where no players/mobs do anything, then quickly catch up. Makes extreme trials extremely frustrating.

My connection, if it helps:

Tracing route to 204.2.229.10 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms R7800 [10.0.0.1]
2 3 ms <1 ms <1 ms 192.168.1.254
3 1 ms 1 ms 1 ms 162-229-180-1.lightspeed.rlghnc.sbcglobal.net [162.229.180.1]
4 3 ms 3 ms 3 ms 99.173.76.178
5 13 ms 15 ms 15 ms rlgnc22crs.ip.att.net [12.123.138.150]
6 17 ms 15 ms 14 ms wswdc21crs.ip.att.net [12.122.2.190]
7 13 ms 11 ms 12 ms wswdc401igs.ip.att.net [12.122.113.37]
8 37 ms 33 ms 25 ms 192.205.37.54
9 13 ms 11 ms 12 ms ae-6.r24.asbnva02.us.bb.gin.ntt.net [129.250.5.155]
10 174 ms 171 ms 199 ms ae-2.r24.snjsca04.us.bb.gin.ntt.net [129.250.6.237]
11 195 ms 191 ms 208 ms ae-4.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.57]
12 224 ms 216 ms 181 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [192.80.16.2]
13 * * * Request timed out.
14 172 ms 186 ms 188 ms 204.2.229.1

Our problem IP (129.250.5.155) is in Kansas, owned by NTT America. Might be an issue with a higher level ISP in the way to the west coast servers. Will try a VPN and report back.