Seems like no one cares about the lag

[joolzy]

for anyone else connecting through the san jose node, did you have lag last night? for once, i didnt get the lag spike at 7pm pacific

[Emerain]

Tracing route to 204.2.229.107 over a maximum of 30 hops

 [...]
  7    24 ms    22 ms    25 ms  12.122.141.233
  8    22 ms     *       29 ms  192.205.36.158
  9    58 ms    47 ms    34 ms  ae-16.r22.atlnga05.us.bb.gin.ntt.net [129.250.5.57]
 10    33 ms     *       36 ms  ae-6.r21.dllstx14.us.bb.gin.ntt.net [129.250.4.116]
 11    75 ms    77 ms    76 ms  ae-2.r25.snjsca04.us.bb.gin.ntt.net [129.250.4.154]
 12   216 ms   234 ms     *     ae-5.r24.snjsca04.us.bb.gin.ntt.net [129.250.3.146]
 13   214 ms   230 ms   234 ms  ae-4.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.57]
 14   230 ms   196 ms     *     xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [192.80.16.2]
 15     *        *      212 ms  204.2.229.230
 16   203 ms   214 ms   202 ms  204.2.229.107

Trace complete.

It's baaaaack.

[Jconix]

for anyone else connecting through the san jose node, did you have lag last night? for once, i didnt get the lag spike at 7pm pacific

I had very short spikes but not a consistent one yesterday. For once in a long while, it felt good.

Tonight however... it was back but 20 minutes before the usual 7pm ramp up.

[joolzy]

yea it's AWFUL again tonight. like the worst it's ever been

[_Chupakabra_]

well so far I've disconnected twice from the game tonight and SE doesn't read the tickets my disconnect didn't' happen during a teleport and the email i got back said that they automatically disconnect you after 30 mins.

my complaint said nothing about that,,, so I'm starting to think they only care about the money they made and not their customer base

[NevaehQuest]

I am freaking lagging right freaking now, I can't have fun so I am here.

[Rainydayz]

So far today, I have been disconnected 4 times today alone. This wouldn't be an issue so much, except it keeps putting me in the back of the line so I get to wait another 2 hours to get back on. This is no fun. Was doing maps last night and got disconnected right in the middle of them. Took me an hour and a half to get back on. So I listened to my FC on discord doing the treasure maps, while I watched the numbers creep down slowly. Then today, I have been dc'd 4 times today, one time firmly having me take a ticket number in the 2800s. I actually left the house and drove to the store to get some stuff, only to come back and find another server error had again knocked me out of the queue. What is going on Square?? This seems to be getting worse, not better.

[NevaehQuest]

same here still lagging tonight, like right now at this moment. I am on mch and i cant even weave during hypercharge. and i cant use wildfire and hypercharge together. Its UPLAYABLE.
Jesus Christ

[Valgora]

Since it's clear that we're not going to get a legitimate response for this, let's brainstorm some workarounds.

As we've discovered in our trace routes, the culprit is a collection of NTT nodes in San Jose. Impact appears to occur under peak load that starts at roughly 9:30P EST through 1:00A EST. Performing a lookup of 204.2.229.107 tells us that NTT isn't just a hop along the way to a destination, but the actual owner of the host we're ultimately connecting to (204.2.229.107). Given this information it appears our only recourse would be to avoid that host completely.

Would we be able to use a VPN to connect to a far away location in hopes the routing takes you elsewhere? Or are we destined to connect to that host regardless of where our connection originates from?

[joolzy]

Would we be able to use a VPN to connect to a far away location in hopes the routing takes you elsewhere? Or are we destined to connect to that host regardless of where our connection originates from?

I tried this. Configured my VPN to try routing through Seattle, LA, SF, Denver, and a bunch of other servers in cities between me and San Jose. They ALL route through the NTT nodes in SJ eventually, so they all suffer the lag. And if I try using nodes going the opposite direction, I'm lagging anyway so that's no good.