Yeah, it's hovering around 100-109ms for me in the "Good" range again. Still no notable packet loss for the moment on my end, but that could change.
The fact that a VPN doesn't always get around it and that it seems to affect more than just AT&T this time (think I saw a Comcast report in the thread recently) gives me reason to believe this issue's different than last time.
That and the packet loss isn't as bad or noticeable for some people, but is very noticeable/bad for others. Hmm...
EDIT (1:55 PM CDT): Noticed a few small bits of packet loss during a Crystalline Conflict (Casual) match. Not that it affected the outcome that much, still won the game in overtime, but it was a bit disconcerting.
I ran a ping to the Aether datacenter and... 50% packet loss. No packet loss on my ping to the lobby server, though. The latest traceroute is enclosed and already submitted to SE via the form here:
https://support.na.square-enix.com/c...ss%20and%20lag
Seems to be that traffic heading into California from anywhere else is affected across multiple connections. I wonder if it's a localized infrastructure problem that seems to be spilling over.
1 <1 ms <1 ms <1 ms (REDACTED)
2 18 ms 17 ms 17 ms (REDACTED)
3 18 ms 18 ms 18 ms (REDACTED)
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 31 ms 31 ms 32 ms (REDACTED)
8 25 ms 25 ms 25 ms ae-5.a00.dllstx14.us.bb.gin.ntt.net [129.250.8.237]
9 27 ms 25 ms 26 ms ae-2.r20.dllstx14.us.bb.gin.ntt.net [129.250.4.9]
10 * 96 ms 101 ms ae-2.r24.lsanca07.us.bb.gin.ntt.net [129.250.7.69]
11 * 108 ms * ae-5.a01.scrmca03.us.bb.gin.ntt.net [129.250.2.7]
12 98 ms 101 ms 105 ms ae-1.a00.scrmca03.us.bb.gin.ntt.net [129.250.4.76]
13 110 ms 109 ms 110 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
14 * 99 ms * 204.2.29.241
15 109 ms 107 ms 110 ms 204.2.29.122

Reply With Quote

