OH WHAT A DAY! WHAT A LOVELY DAY!


OH WHAT A DAY! WHAT A LOVELY DAY!
The menacing aura of every Lalafell.
Adding to the pile. COMCAST east coast.
Cox east cost, was on Ultros, downstream seemed ok just judging by the numbers in the game UI, but upload kept crashing. Not doing any tracert because I've already done a ton.
Judging by the queue now from trying to log on (+1k in queue) seems the entire server crashed and it wasn't just me.
You weren't the only one to crash, though there's speculation we're being DDOS'd over and over again.


sorry someone tripped over the power cable
As of right now, latency is coming in erratic, unpredictable moments. Sometimes it'll be fine, but then suddenly it'll be like a three to five second delay on actions. This will last for a few seconds and then it will go back to normal.
Not to mention that it actually took about five full MINUTES for the forums to load after I tried to log in. It usually takes a while because it auto-redirects to the Japanese forums (and I'm in the US, so that's a long way for data to have to travel), but this time I actually had to leave the page open and just check on it later.
Last edited by DariRyusei; 09-01-2024 at 01:26 AM. Reason: Additional Info
Still a problem - got dropped and now it's throwing the HTTPS errors, and now it cannot validate the certificate for the login client. This has been a horrible experience for me since at least this expansion, and only gets worse. Also an ATT fiber customer here, so yeah...
I've been having the same latency issues as described by others for multiple weeks now, with a break last night, and it beginning again in full force earlier this evening. I've run tracerts on my PC (with wi-fi) and my wife's PC (with ethernet) and both computers have issues with particular nodes in California. I've submitted information to the support website linked to by Okieeomi but am beginning to feel rather bummed about the situation. Especially after all the steps I've taken in the last couple weeks to ensure the best possible connection I can get.
1 9 ms 17 ms 32 ms [redacted]
2 16 ms 19 ms 13 ms [redacted]
3 24 ms 138 ms 48 ms [redacted]
4 20 ms 18 ms 18 ms [redacted]
5 21 ms 21 ms 20 ms [redacted]
6 55 ms 32 ms 422 ms [redacted]
7 18 ms 44 ms 24 ms [redacted]
8 15 ms 14 ms 15 ms ae-9.a02.sttlwa01.us.bb.gin.ntt.net [129.250.66.105] <- beginning of NTT nodes
9 16 ms * * ae-2.r25.sttlwa01.us.bb.gin.ntt.net [129.250.2.94]
10 * 36 ms * ae-3.r25.snjsca04.us.bb.gin.ntt.net [129.250.3.124]
11 * * * Request timed out.
12 38 ms 47 ms 94 ms ae-4.a00.scrmca03.us.bb.gin.ntt.net [129.250.7.57]
13 59 ms 38 ms 38 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
14 37 ms * * 204.2.29.241
15 35 ms 35 ms 37 ms 204.2.29.8
I had the opportunity to do a video interview with an SE representative at PAX West. I wish I would have thought to bring this up during that interview, too.... the glowing review of the game I gave doesn't quite describe how it feels to play right now.
Last edited by mayanyamano; 09-04-2024 at 03:23 PM. Reason: Specifying latency issues, not just "same issues as others". I have not been kicked out of the game except during mass DCs.

Have you ever tried to talk to AT&T support?Greetings,
We are aware that some players have been experiencing network-related issues (such as a few seconds of network loss, lag, or disconnects) over the past few days when playing on the North American data centers.
<snip>
Additionally, as mentioned in the announcement, even if we are unable to request investigations from some of the ISPs from our end, the situation may be improved if players can contact their internet service provider and share their details and issues directly with them.
We appreciate your cooperation as we continue striving to address network-related issues that players may be experiencing.
It's like trying to pull your own teeth... with a pair of tweezers.

Bumping this because I've suddenly started having problems with this yesterday afternoon. According to tracert, everything seems normal until NTT's Sacramento 03 data center.
1 <1 ms <1 ms <1 ms RT-AX82U-EE18 [192.168.50.1]
2 6 ms 4 ms 3 ms 50-104-64-1.prtg.in.frontiernet.net [50.104.64.1]
3 2 ms 4 ms 4 ms 184.19.246.62
4 5 ms 6 ms 8 ms ae8---0.scr03.chcg.il.frontiernet.net [74.41.143.152]
5 6 ms 6 ms 6 ms ae0---0.cbr05.chcg.il.frontiernet.net [45.52.201.105]
6 7 ms 6 ms 6 ms lag-105.ear3.Chicago2.Level3.net [4.16.38.117]
7 6 ms 6 ms 13 ms ae2.2.edge1.Chicago10.net.lumen.tech [4.69.133.29]
8 8 ms 8 ms 8 ms ae-4.a05.chcgil09.us.bb.gin.ntt.net [129.250.8.173]
9 8 ms * 19 ms ae-4.r23.chcgil09.us.bb.gin.ntt.net [129.250.4.239]
10 * * * Request timed out.
11 118 ms 116 ms 116 ms ae-4.a00.scrmca03.us.bb.gin.ntt.net [129.250.7.57]
12 66 ms 64 ms 64 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
13 63 ms 62 ms * 204.2.29.241
14 64 ms 64 ms 64 ms 204.2.29.9
My ping is normally around 65ms, but this issue has doubled my ping. I've already submitted a report, but I'm just frustrated.
ETA: There were some issues with their San Jose data center as well. I forget which one exactly, as now it doesn't even respond in tracert and just goes straight to Sacramento 03.
Last edited by Zahbi; 09-09-2024 at 02:22 AM. Reason: Additional info.
|
|
![]() |
![]() |
![]() |
|
|
Cookie Policy
This website uses cookies. If you do not wish us to set cookies on your device, please do not use the website. Please read the Square Enix cookies policy for more information. Your use of the website is also subject to the terms in the Square Enix website terms of use and privacy policy and by using the website you are accepting those terms. The Square Enix terms of use, privacy policy and cookies policy can also be found through links at the bottom of the page.


Reply With Quote





