Look, I don't know who to contact or who to complain to but there's a problem on the route to the server, it's been on/off since before endwalker release and I didn't mind that much cause I didn't have a lot going on but tonight I had my first savage day with static and I get hit with a disconnection error because of that hop, I'm absolutely furious.
https://i.imgur.com/MpHUaMZ.png
Can we have a fix on snjsca04
Printable View
-
01-06-2022, 11:45 AMAnnabellechuCan we have a fix on snjsca04
-
01-06-2022, 12:46 PMLiralara
Guys, it's been a week and a half since this started. Please address whatever is happening in your network or your provider's (NTT) network.
6 9 ms 11 ms 9 ms gar25.dlstx.ip.att.net [12.122.85.233]
7 10 ms 12 ms 12 ms ae-5.a00.dllstx14.us.bb.gin.ntt.net [129.250.8.237]
8 12 ms 9 ms 15 ms ae-2.r21.dllstx14.us.bb.gin.ntt.net [129.250.4.19]
9 * 46 ms 45 ms ae-2.r25.snjsca04.us.bb.gin.ntt.net [129.250.4.154]
10 196 ms * 148 ms ae-5.r24.snjsca04.us.bb.gin.ntt.net [129.250.3.146]
11 155 ms 140 ms 134 ms ae-4.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.57]
12 194 ms 209 ms 202 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [192.80.16.2]
13 * * * Request timed out.
14 169 ms 186 ms 200 ms 204.2.229.10
Trace complete. -
01-06-2022, 01:02 PMEmerain
Two from tonight, right after it started.
Code:8 22 ms 21 ms * 192.205.36.158
9 26 ms 21 ms 21 ms ae-16.r22.atlnga05.us.bb.gin.ntt.net [129.250.5.57]
10 32 ms 33 ms * ae-6.r21.dllstx14.us.bb.gin.ntt.net [129.250.4.116]
11 * * * Request timed out.
12 198 ms * 151 ms ae-5.r24.snjsca04.us.bb.gin.ntt.net [129.250.3.146]
13 212 ms 209 ms 207 ms ae-4.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.57]
14 195 ms 190 ms 166 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [192.80.16.2]
15 * * 115 ms 204.2.229.230
16 72 ms 79 ms 75 ms 204.2.229.107
Code:8 * 21 ms 20 ms 192.205.36.158
9 23 ms 21 ms 21 ms ae-16.r22.atlnga05.us.bb.gin.ntt.net [129.250.5.57]
10 32 ms 32 ms 32 ms ae-6.r21.dllstx14.us.bb.gin.ntt.net [129.250.4.116]
11 70 ms * 70 ms ae-2.r25.snjsca04.us.bb.gin.ntt.net [129.250.4.154]
12 224 ms 225 ms 213 ms ae-5.r24.snjsca04.us.bb.gin.ntt.net [129.250.3.146]
13 131 ms * 230 ms ae-4.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.57]
14 * 201 ms 214 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [192.80.16.2]
15 * * * Request timed out.
16 110 ms 103 ms 95 ms 204.2.229.107
-
01-06-2022, 01:09 PMJconix
This is mine from tonight, the spike began 30 minutes after the usual ramp up at 7pm pst. Please, Square, look into this. This issue never happened as consistent as it's been since last week.
4 20 ms 24 ms 21 ms 12.242.117.22
5 * 178 ms 176 ms 192.205.37.58
6 160 ms 157 ms 178 ms ae-9.r24.snjsca04.us.bb.gin.ntt.net [129.250.2.2]
7 182 ms 153 ms 144 ms ae-4.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.57]
8 189 ms 192 ms 177 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [192.80.16.2]
9 185 ms * * 204.2.229.230
10 * 181 ms * 204.2.229.10
11 169 ms 148 ms 179 ms 204.2.229.10 -
01-06-2022, 01:23 PMjoolzy
I've had the same issue for at least a week. Consistent 65ms all day between 10AM to around 9PM Central Time. Then right around 9PM, every night for a week, my connection spikes to 220ms and stays there the rest of the night. Please fix this, it's making raiding impossible.
5 10 ms 7 ms 7 ms 32.130.16.195
6 13 ms 6 ms 6 ms 192.205.36.158
7 5 ms 6 ms 6 ms ae-16.r22.atlnga05.us.bb.gin.ntt.net [129.250.5.57]
8 25 ms 24 ms 29 ms ae-6.r21.dllstx14.us.bb.gin.ntt.net [129.250.4.116]
9 63 ms 63 ms 64 ms ae-2.r25.snjsca04.us.bb.gin.ntt.net [129.250.4.154]
10 179 ms 226 ms 217 ms ae-5.r24.snjsca04.us.bb.gin.ntt.net [129.250.3.146]
11 194 ms 177 ms 213 ms ae-4.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.57]
12 169 ms 199 ms 211 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [192.80.16.2]
13 * * * Request timed out.
14 206 ms 205 ms 212 ms 204.2.229.96 -
01-06-2022, 01:24 PMLiralara
Yea...not a good look.
Reply from 204.2.229.10: bytes=32 time=199ms TTL=48
Reply from 204.2.229.10: bytes=32 time=165ms TTL=48
Reply from 204.2.229.10: bytes=32 time=200ms TTL=48
Request timed out.
Reply from 204.2.229.10: bytes=32 time=197ms TTL=48
Reply from 204.2.229.10: bytes=32 time=198ms TTL=48
Reply from 204.2.229.10: bytes=32 time=201ms TTL=48
Reply from 204.2.229.10: bytes=32 time=211ms TTL=48
Reply from 204.2.229.10: bytes=32 time=203ms TTL=48
Reply from 204.2.229.10: bytes=32 time=171ms TTL=48
Request timed out.
Reply from 204.2.229.10: bytes=32 time=209ms TTL=48
Reply from 204.2.229.10: bytes=32 time=169ms TTL=48
Reply from 204.2.229.10: bytes=32 time=200ms TTL=48
Reply from 204.2.229.10: bytes=32 time=202ms TTL=48
Reply from 204.2.229.10: bytes=32 time=200ms TTL=48
Reply from 204.2.229.10: bytes=32 time=203ms TTL=48
Reply from 204.2.229.10: bytes=32 time=179ms TTL=48
Reply from 204.2.229.10: bytes=32 time=190ms TTL=48
Request timed out.
Reply from 204.2.229.10: bytes=32 time=204ms TTL=48
Reply from 204.2.229.10: bytes=32 time=172ms TTL=48
Reply from 204.2.229.10: bytes=32 time=202ms TTL=48
Reply from 204.2.229.10: bytes=32 time=185ms TTL=48
Reply from 204.2.229.10: bytes=32 time=206ms TTL=48
Reply from 204.2.229.10: bytes=32 time=199ms TTL=48
Reply from 204.2.229.10: bytes=32 time=204ms TTL=48
Request timed out.
Reply from 204.2.229.10: bytes=32 time=193ms TTL=48
Reply from 204.2.229.10: bytes=32 time=189ms TTL=48
Request timed out.
Reply from 204.2.229.10: bytes=32 time=195ms TTL=48
Reply from 204.2.229.10: bytes=32 time=206ms TTL=48
Reply from 204.2.229.10: bytes=32 time=200ms TTL=48
Reply from 204.2.229.10: bytes=32 time=195ms TTL=48
Reply from 204.2.229.10: bytes=32 time=208ms TTL=48
Reply from 204.2.229.10: bytes=32 time=183ms TTL=48
Reply from 204.2.229.10: bytes=32 time=206ms TTL=48
Reply from 204.2.229.10: bytes=32 time=204ms TTL=48
Reply from 204.2.229.10: bytes=32 time=206ms TTL=48
Reply from 204.2.229.10: bytes=32 time=206ms TTL=48
Reply from 204.2.229.10: bytes=32 time=195ms TTL=48
Request timed out.
Reply from 204.2.229.10: bytes=32 time=206ms TTL=48
Reply from 204.2.229.10: bytes=32 time=198ms TTL=48
6 11 ms 10 ms 9 ms gar25.dlstx.ip.att.net [12.122.85.233]
7 9 ms 8 ms 9 ms ae-5.a00.dllstx14.us.bb.gin.ntt.net [129.250.8.237]
8 9 ms 9 ms 9 ms ae-2.r21.dllstx14.us.bb.gin.ntt.net [129.250.4.19]
9 * 49 ms 45 ms ae-2.r25.snjsca04.us.bb.gin.ntt.net [129.250.4.154]
10 188 ms * 201 ms ae-5.r24.snjsca04.us.bb.gin.ntt.net [129.250.3.146]
11 129 ms 135 ms 150 ms ae-4.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.57]
12 206 ms 175 ms 205 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [192.80.16.2]
13 * * 195 ms 204.2.229.230
14 203 ms 191 ms 188 ms 204.2.229.10
Trace complete. -
01-06-2022, 02:50 PMLiralara
I submitted a ticket to their support this evening and was given the typical copy\paste template from a 1st tier support rep telling me that I need to reboot my PC, check my ports and antivirus, etc...
I'm not sure if this is standard 1st response to meet an SLA or not, but it's definitely annoyed the hell out of me. Applications, port configurations, etc may affect my game client, but it's not going to affect a damn ping response between a very specific time window.
I recommend that people with this issue start opening tickets with their support if they want to have any actual attention bought regarding this problem. Otherwise, it's too easy for them to just blow us off and say it's not their problem or responsibility to fix. -
01-06-2022, 05:29 PMFreki42here is the information about that node of the internet: https://www.whois.com/whois/192.250.5.17Quote:
Originally Posted by Annabellechu
It is owned and operated by OTIS Elevator Company (OTISEL). this is not something you can get Square Enix to do anything about.
you could try a vpn to avoid that node... -
01-06-2022, 06:36 PMNevaehQuest
I dont know what is all this technical things means but the lag is real and its painful. I just want to play the game in peace. dev plz help
-
01-07-2022, 12:04 AMFreki42Lag can happen anywhere from you to the destination (the game). what is being talked about here, is one of the nodes the communications go through. The internet isn't magical i wish it were, it's like a highway for you there are places between you and the destination and if one of those places have high traffic you have to deal with it or find a way around it. sometimes a VPN can help with that. IF the lag is happening somewhere outside of the control of you, your ISP or the game, there generally isn't much you can do about it other than reroute around the problems.Quote:
Originally Posted by NevaehQuest
-
01-07-2022, 10:36 AMMenriq
At this point, I'm having to give up my spot in the static because of this issue right during primetime. It would be nice if someone were to raise the issue, but it doesn't seem like it's either a priority or we are a small minority that the cost benefit isn't worth fixing.
-
01-07-2022, 12:20 PMFlarestar
Same. This starts at 10 PM Eastern and continues until roughly 1 AM every night - like literally we were mid-pull tonight and at 10 PM on the dot everyone started iceskating on my screen.
This is clearly a traffic shaping behavior NTT is engaging in on that node during west coast primetime. Square, you guys have gotta get in touch with them to get it resolved. -
01-07-2022, 01:42 PMLiralara
Bump. Same issue again tonight. Started around 9pm CST. Same node within NTT's network in San Jose.
The support ticket I have they stated that they have numerous reports of this and they are working on it. Take that as you will. -
01-08-2022, 02:50 PMFreki42have you been told by SE they are not looking into the issue? I know it has affected a good many people here on the forums, but only a few of the tracert's and other track information doesn't show just those NTT nodes having an issue, heck the one that is posted about here is in NJ and owned by an elevator company. I don't know what to tell you.Quote:
Originally Posted by Flarestar
-
01-08-2022, 07:24 PMNevaehQuest
every freaking night 7pm -11pm
-
01-08-2022, 09:12 PMZinzuPlease double check your post.Quote:
Originally Posted by Freki42
The whois data you posted is for 192.250.5.17. This node that we're referencing is 129.250.5.17
https://www.whois.com/whois/129.250.5.17
This is an NTT node. -
01-09-2022, 07:00 AMFreki42you are correct i apparently transposed the 2 and the 9. and you are correct it is NTT, but still SE has no hold over them. they can talk and it has been commented that they are in talks with them. this node however as shown is in CO. this makes it even more interesting as I am an East coast player and it would stand to reason that I would be affected by this, however I am not. I am genuinely curious as to why I am not affected (no I am not using a VPN, but connected directly to verizon fios. good catch of my mistake. My apologies.Quote:
Originally Posted by Zinzu
-
01-09-2022, 10:10 AMNevaehQuest
thanks you guys are doing gods work, please keep it up~!
-
01-10-2022, 02:31 PMLeviathan1usa
Freki42, if they pay NTT as their host then yes they would have a hold over them to get it fixed and they have done this before as NTT is the host for their servers, not just some random intermediate IP host. Your thought process as far as it stands to reason that you would be affected by it would not be exactly accurate. The reason for this is your routing table for Verizon is more than likely routed differently from those that are experiencing the issue. Not every internet provider routes the same way through to that server so that would probably be why you are seeing a different affect from others.
-
01-10-2022, 03:36 PMZerea
My stuff is still borked. Every night from 9:45 PM ET to 12:15 AM. Same issue as everybody else here is reporting.
220ms all throughout prog was a ton of fun. -
01-10-2022, 05:51 PMFreki42then i guess from the midatlantic coast i don't go throguh those nodes what so ever then because i never get any of the delay you all are talking about. and I am on a good bit of the day... no disconnects and no lag to speak of, nothing game breaking as talked about here. Yet it makes me wonder why when i am on the complete opposite end.Quote:
Originally Posted by Leviathan1usa
-
01-10-2022, 06:05 PMLemuel81
I don't know if this could or will be fixed sadly. From the beginning a handful of people have experienced this issue. When I was Verizon I fell prey to this and was forced to use WTFast until I moved years later and did not have that issue no more. I guess back then WTFast was free so it didn't bother me. Let's hope there is something that they can do. Dealing with ISP on these types of issues have always been unhelpful.
-
01-17-2022, 12:57 PM_right
Another night, another bump... Same exact thing on snjsca04. Does SE support even look in these threads? This lack of communication not encouraging.
-
01-17-2022, 01:44 PMNevaehQuest
They think we are just a bunch of jokes.
-
01-18-2022, 12:26 AMKolsykol
Stuff like this makes me regret buying stuff like all of the artbooks and other merch and spending so much in the mogstation...
I love this game but holy hell this problem is infuriating and makes the game unplayable and the lack of support other than copy pasted answers that aren't helpful at all makes it worse.
We pay a monthly sub the game should be playable and if there's a node that is a consistent problem they should be called up and get an earfull. -
01-18-2022, 02:48 AMVahlnir
The last few days I haven't noticed any lag, but my ISP went through a change of hands apparently and rebranded. Based on their speed test it looks like their source and route is now different, so I must be on a different "lane". Hopefully they address this issue soon though. There's no good reason that they couldn't be hounding those in charge of the node to get their act together.
-
01-18-2022, 02:53 AMWilford111
I'm noticing this too. However I can't really use a VPN to help the problem - last time I tried, SE thought my account was being used suspiciously and I had to change my password. So that option is kind of out for me.