This feels like it will just devolve intol a blame game until they see us just give up. Sorry for the downer but seeing both SE and ATTs responses gives me no hope at all.
Bad lag again with NTT's NA server network
Printable View
-
05-26-2023, 10:09 PMDante505
-
05-26-2023, 10:10 PMEtternaDon't play on console but I used to route my ps4s traffic thru my pc using a local proxy/vpn server. Assuming this can still be done it should allow consoles to use a pc based vpn connection. In theory, I've never had the need to vpn for my ps4.Quote:
Originally Posted by brnslpy
-
05-26-2023, 11:04 PMgeekers
Adding my voice to the choir. ATT here, and having the issue, too. I finally decided to try a VPN yesterday, and it worked for the packet loss/rubber banding. Using the free tier of Proton VPN (they only ask for an email address, so low bar), so the speed/latency was still a little slower than before the ATT/NTT issue. Made the game playable (even PvP was decent) rather than me quitting because playing felt like pulling teeth.
-
05-26-2023, 11:12 PMMerricat
Sigh. Here for my morning check-in to see if there is any change. Apparently we're still deep in the round robin of "not my equipment, not my problem"!
I'm using 1.1.1.1 and it's decent. I had a few flaky days, but it was fine during primetime hours (Eastern time zone) last night. I'm hoping it stays stable. It is NOT as good as my connection was before all this, but it's noticeably better than playing without it. -
05-26-2023, 11:31 PMMerricat
Aaaaaaand now I'm getting a better connection without the VPN. Nevermind. I give up trying to figure this out.
-
05-26-2023, 11:43 PMniftyqt
Hello fellow Warriors of Light!
I just spoke to AT&T (as recommended by Yoshi's team: https://na.finalfantasyxiv.com/lodes...6a07e92f6a0f29
Here was AT&T's response:
Quote:
I have checked in over the network lines, and the team has indeed reported a know issue for which the case is being worked upon. To assist you best upon the issue being cleared over the backend server, I would also like to help open a dedicated port over your router as well, so that the game can indeed function smoothly over the intended device. Would that be okay with you?
For the tech savvy: Go to your modem's Firewall setup page in your browser, and open the port range: 2031-2032 with the base port at 2031.
Non-tech savvy: Go to https://www.att.com/support/internet/ and scroll to the bottom to chat with a rep or call 800-288-2020. Tell them about the issue with the lag while playing Final Fantasy XIV, and ask them to open the port range: 2031-2032 with the base port at 2031 on your router for you.
My original post: https://www.reddit.com/r/ffxiv/comme...rk_lag_issues/ -
05-26-2023, 11:49 PMIllyrian94Interesting. I'll give that a shot after work tonight and see what happens. My knowledge of networking is pretty limited so I'm not exactly sure how opening a port on our routers will get us around those problem nodes, but it's worth a try at the very least.Quote:
Originally Posted by niftyqt
-
05-26-2023, 11:54 PMXellos2099
what setting do i use if i use 1.1.1.1?
-
05-26-2023, 11:59 PMAhumayaOpening a port or series of ports will not resolve a network routing issue caused by a faulty device within NTTs network stack. The solution listed will not help with anything, but the AT&T tech can't simply say "Well we can't do anything, good luck!".Quote:
Originally Posted by Illyrian94
Also, as noted in previous pages of this now 73 page long thread, the high latency and packet loss is on a (very regular) schedule, and we still have another 2.5 hours before things get bad, and then another 2 hours or so after that before packet loss begins.
I am very happy to see a lodestone post however, as that is a significant improvement over just 2 tweets, but the post fails to actually identify the issue or a timeline on restoration. Alas.
Much love, things will get better. -
05-27-2023, 12:00 AMJanyd
I can't speak for everyone but I was able to open those ports in my browser.
Once I accessed my gateway, I went to Firewall, then the NAT/Gaming section, and created a new "custom service" with those ports open. t helps to name it, as well.
If it doesn't work, you can delete the custom service you made there. -
05-27-2023, 12:10 AMbrnslpyYep, can also use "Internet Sharing" on PC/Mac to connect PS5 -> ethernet -> USB ethernet dongle -> Mac/PC Internet Sharing -> VPN App -> InternetQuote:
Originally Posted by Etterna
It worked ok but still had some lag for me, probably cause of the USB connection. The Dedicated VPN gateway (RaspberryPi/GL.INET device) let me get my Mac desktop out of the loop and have a dedicated VPN device for the PS5 -
05-27-2023, 12:25 AMLahtori
As others have said, opening the ports will not solve the issues. That is something the SE rep told me to do as well and while I went ahead and opened up the ports, it did absolutely nothing. It's not going to solve the NTT connection.
For those interested in which ports SE told me to open, it's somewhere in this thread, maybe like 20 or so pages back at this point. Solidarity everyone! -
05-27-2023, 12:29 AMIllyrian94
Yeah, it's a pretty nonsensical "solution". It's not going to magically change where our traffic gets routed to.
Gotta love being caught up in an apparent corporate pissing match! -
05-27-2023, 12:40 AMAnida
So, still no progress? SE's Lodestone post is fairly generic, at best. Basically, still telling everyone to hassel AT&T for an issue that isn't theirs. Maybe SE needs to look into switching to a different service to handle their traffic. I'm sure there are others.
-
05-27-2023, 12:50 AMAnidaOr, instead of going through a lot of rigamarole or pay extra for a VPN, unsub and just play something else until this is resolved. I'm currently back in GW2 and actually enjoying the change of scenery, so to speak. Still want to play FFXIV, but I'm just not going to be victim of corporate stupidity and squabbling.Quote:
Originally Posted by brnslpy
-
05-27-2023, 01:02 AMKrojackHaving worked in a NOC before which also paid for backbone connections from ATT, ATT is NOT a friendly company to work with. They are EXTREMELY pushy and demanding. They know that they control the vast majority of backbone connections in the USA and they use this to control and others.Quote:
Originally Posted by Merricat
If I had to guess, NTT and ATT have an agreement where ATT puts their own equipment in NTT's datacenter for the peer connection. ATT connects their network to this and now something within that equipment is overload during peek times. ATT might be trying to say NTT needs to pay something to upgrade the equipment. The NDA will prevent NTT from telling others about this which makes it look like an NTT problem.
Because ATT will default to routing all their users though their network, we ATT customers get forced though this connection and screwed over. -
05-27-2023, 01:07 AMArcadiaP
How much more money do these people need. Greed is so bad to society, eff. It really sucks it's been like 2 weeks of absolutely nothing.
-
05-27-2023, 01:37 AMRekts
So realistically what's our recourse here? Just keep harassing both ATT and NTT with calls and support tickets and hope that either of them get tired of it and fix it?
-
05-27-2023, 01:59 AMIllyrian94That's really about it, yeah. Keep being a pain (respectfully) and push their support KPIs up high enough and maybe eventually the business-types will decide that it's worth doing something about. That's about the only thing that gets the attention of the higher-ups at the company I work at--once us devs get pulled onto support work enough they eventually decide to actually give us the time to work on fixing long-running issues. It sucks, but that's how the corporate world works in quite a few places.Quote:
Originally Posted by Rekts
Other than that... I guess try and get visibility in games media? Same sort of a deal there--increased visibility won't solve our problem, but the pressure of it being discussed a bit more widely outside the Square Enix forums might move the needle at least somewhat.
Edit: And just to be clear--the tier 1 support folks we're dealing with have no real power to change things, investigate things, or even really deviate from their scripts all that much if experience says anything. Be kind to them, but be persistent in getting things escalated and pushed higher up. Yeah, having to go through basic troubleshooting steps repeatedly sucks... but at least in some places tier 1 support folks can and will be penalized for deviating from their initial scripts too much. -
05-27-2023, 01:59 AMbrnslpySorry that I want to play FFXIV /shrugQuote:
Originally Posted by Anida
-
05-27-2023, 02:05 AMniftyqtCorrect. Chat and phone support costs a lot for the company, so the more people that call reporting the same issue, the likelier it'll be bumped up in priority to resolve.Quote:
Originally Posted by Illyrian94
-
05-27-2023, 02:19 AMAnidaSo do I, but that's not my point.Quote:
Originally Posted by brnslpy
As long as people are willing to do work-arounds, even at extra cost to themselves, this issue will never truly be a priority. -
05-27-2023, 02:23 AMDeceptusAll that post says is:Quote:
Originally Posted by Janyd
"It's not us, it's them." Basically, "sucks to be an AT&T subscriber right now" -
05-27-2023, 02:36 AMRekts
I was reading over the comments on Twitter for the lodestone announcement, and more people with different ISPs are complaining about the same issue.
So it's not just ATT confirmed. Correct me if I'm wrong(I am not technical savvy), but doesn't that prove that it's NTT's responsibility and not an NDA between ATT and NTT about who's responsible for paying for upgrades? -
05-27-2023, 03:40 AMIllyrian94
Hello yes this is your friendly neighborhood Hrothgar stopping in for the daily "still broke" screenshot ritual. Start time has shifted slightly the past few days from what we were seeing before, but the overall result is still the same. Just a bit more buildup and suspense now before it starts in earnest. The network can do a little pregaming, as a treat.
Ping and packet loss go brrr.
https://i.imgur.com/yI77O3G.png -
05-27-2023, 04:04 AMLinaGiggles
Yeah I just feel like we're hitting walls over and over.... and either one wants to take fault or part but want us to voice to other said company about the issue. *sigh* Savages start next week.
-
05-27-2023, 04:29 AMMerricatYeah. It's depressing. I feel ya.Quote:
Originally Posted by LinaGiggles
-
05-27-2023, 04:31 AMn_nI'm still playing only because I just bought 30 days game time just as this BS started. If the issue is still a thing 20 days from now, I'll gladly "boycott" the game until this is fixed, even though I have a "free" workaround that works perfectly.Quote:
Originally Posted by Anida
-
05-27-2023, 05:20 AMradhaz
I'm having the issue on both my NA and JP char.
https://live.staticflickr.com/65535/...bdafb8d337.jpg
https://live.staticflickr.com/65535/...6d097d4ebb.jpg -
05-27-2023, 05:21 AMDante505
Even though I knew it wasn't going to work, I opened up the ports they asked and here is a screen shot with the trace routes after they are opened
https://i.imgur.com/Rqf7db8.png -
05-27-2023, 05:21 AMDarthKamen
Sorry if this has been said before, but this is a large thread, and searching it shows nothing. I have T-Mobile internet, not AT&T. Since yesterday morning I have had horrible lag followed by disconnection, rendering it unplayable (I am on console). Traceroute shows NTT as being the issue, as many seem to point out. So it is affecting more than just AT&T users.
I just wanted to put this out there somewhere official. -
05-27-2023, 05:59 AMIntegroT-Mobile at some point likely hops into ATT fiber. I have Dish, they utilize ATT fiber network, my tracer routes show ATT in the hop chain. My ping and packet loss begin on the 8th hop to the NTT Sacramento node.Quote:
Originally Posted by DarthKamen
-
05-27-2023, 06:03 AMDarthKamenAh that makes sense, thank you. I'm not very versed in how this stuff works.Quote:
Originally Posted by Integro
-
05-27-2023, 06:04 AMGymoz
Replying here for extra traction.
I have ATT Fiber with ExitLag set to San Jose(1). Early morning, ping is 70s. Noon to Evening, ping is 115-125.
SE please get in contact with NTT so we can actually play the game, thanks.
Here is the contact form for NTT. -
05-27-2023, 06:15 AMsynthrian
Getting this issue on Mediacom as well. I can mostly stay connected during the day but I noticed the past couple nights around 8pm Central it's literally unplayable and I can barely stay connected for 5 mins. Too bad that's when my static plays :( Have tried various nodes on Mudfish, Nord and Exitlag, as well as CF. Going to give PIA a shot tonight but I'm not optimistic.
-
05-27-2023, 06:27 AMMonochii
Hey still having the same issues as everyone else. No difference with connection with nearly 100% packet loss on the NTT servers end. Having no issues outside of FFXIV....
This maybe the hopium speaking but I feel positive about the latest update from Square yesterday.
"the teams did find that connection quality was degrading at certain points on the Internet, depending on the connection used to reach the servers."
"we are working with the network carriers that are directly connected to our servers to resolve the issue,".
From what I'm understanding this means they at least see what we've all been seeing with the issues on NTT servers end and are speaking to them to resolve it. It is always a good idea to double check with your ISP to make sure that your connection to the internet is as solid as possible, even though that is clearly not what is wrong here.
Really all we can do at this point is keep submitting the Tracert reports and honestly keep pressure Square on this forum and any other social media platform to keep them aware that this is still a major problem that needs to be fixed.
If you really have to play you can use a VPN as a workaround. Don't stop keeping the pressure on Square though. This is NOT a fix from Square and we shouldn't have to ourselves find ways to fix the issue. We as the consumer should only have to consume the product we pay for. -
05-27-2023, 07:55 AMJanydExactly this. Also, nothing wrong with "Hopium" in my book. It beats hopeless cynicism and the "we are nothing" bull going around.Quote:
Originally Posted by Monochii
Despair is for cowards, and that is not my style.
Use a VPN as a workaround if you must, or 1.1.1.1 (Cloudflare Warp) if you can get it to work, but keep the pressure on 'em.
Lest we forget, keep sending your Traceroutes and Pings to this form: https://secure.square-enix.com/enqt3...NETWORK_N/html -
05-27-2023, 08:02 AMRekts
I don't mean to jinx it, but for whatever reason my connection seems fine atm?
-
05-27-2023, 08:16 AMArcadiaP
Doing a trace route through my router as I'm currently on with Mudfish, yes, the ping is 60ms which is what I expect from my connection and distance to California. Looks like a solid 58-60ms Ping to XIV currently.
Hrothgar, where art thou to share your neat graphs with us. -
05-27-2023, 08:19 AMbrnslpy
Traceroute at 19:14 EDT:
MTR at 19:17 EDT:Code:6 32.130.17.77 (32.130.17.77) 7.822 ms 7.141 ms 8.617 ms
7 cgcil402igs.ip.att.net (12.122.132.197) 9.774 ms 15.007 ms 7.826 ms
8 192.205.32.194 (192.205.32.194) 9.523 ms 7.111 ms 7.090 ms
9 ae-4.r23.chcgil09.us.bb.gin.ntt.net (129.250.4.239) 9.029 ms 9.135 ms 7.508 ms
10 ae-1.r24.snjsca04.us.bb.gin.ntt.net (129.250.5.17) 54.301 ms 54.236 ms 54.171 ms
11 * * *
12 xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net (128.241.2.18) 57.854 ms 57.579 ms 57.414 ms
13 * 204.2.29.241 (204.2.29.241) 57.276 ms *
14 204.2.29.96 (204.2.29.96) 57.456 ms 56.810 ms 56.713 ms
EDIT: Added an MTR coming from same physical location but going through a VPN and same routes as above:Code:6. 32.130.17.77 0.0% 9 10.1 10.5 7.8 13.6 2.2
7. cgcil402igs.ip.att.net 0.0% 9 7.7 11.0 7.7 14.2 2.2
8. 192.205.32.194 0.0% 9 12.6 12.3 7.8 23.4 4.7
9. ae-4.r23.chcgil09.us.bb.gin.ntt.net 0.0% 9 8.1 13.9 7.7 59.3 17.1
10. ae-1.r24.snjsca04.us.bb.gin.ntt.net 77.8% 9 54.4 54.3 54.2 54.4 0.1
11. ae-4.a00.scrmca03.us.bb.gin.ntt.net 11.1% 9 57.0 63.6 57.0 93.4 13.3
12. xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net 0.0% 9 57.5 57.5 57.3 57.7 0.1
13. 204.2.29.241 87.5% 8 57.1 57.1 57.1 57.1 0.0
14. 204.2.29.96 0.0% 8 57.0 56.9 56.6 57.2 0.2
Yeah these numbers are a lot different than what we've been seeing. Fingers crossed maybe they fixed it before they go away for holiday weekend.Code:6. be2124.ccr41.ord01.atlas.cogentco.com 0.0% 15 7.9 7.3 7.0 7.9 0.3
7. be2765.ccr41.ord03.atlas.cogentco.com 0.0% 15 7.5 7.8 7.2 13.1 1.5
8. ae-11.a06.chcgil09.us.bb.gin.ntt.net 0.0% 15 8.9 10.2 6.9 16.4 2.8
9. ae-10.r23.chcgil09.us.bb.gin.ntt.net 0.0% 15 16.8 9.0 6.7 16.8 3.0
10. ae-1.r24.snjsca04.us.bb.gin.ntt.net 50.0% 14 54.3 57.3 53.8 69.5 6.0
11. ae-4.a00.scrmca03.us.bb.gin.ntt.net 30.8% 14 57.2 58.5 57.2 63.0 1.9
12. xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net 0.0% 14 57.7 57.9 57.5 58.2 0.2
13. 204.2.29.241 92.3% 14 57.3 57.3 57.3 57.3 0.0
14. 204.2.29.96 0.0% 14 57.2 58.1 56.8 67.3 2.9