I did not, I said more likelyIt can be a comcast issue even for people who dont have comcast as their ISP, if their ISP uses comcasts lines at some point. Not all ISPs own the full length of their connections, and even then, they have to connect outside the ISP at some point. This is likely where the bad node is, which is why it effects people not on comcast, and people who have comcast.
And yes, you did in fact say "its most likely an issue on SE's servers that didn't effect everyone"




I'm not sure if it's just ISP, or perhaps there's a bump in the tubes we are all going through. Doing alliance raids for the relic and have been watching alliance members get the red ring of death over the past two nights. Seen tanks dc and just did myself.
This is on primal




It's a problem with a node that SE and Comcast communicate thru. It's something Comcast can fix, and it's something NTT can fix, but there's no amount of work that can fix it on XIV's end other than someone from SE talking to someone from NTT. And considering the amount of cheaping-out that's been going on in the US lately in regards to ISPs (NTT being the middleman ISP SE uses for Comcast), it's highly likely they'll bandaid fix it and the problem will happen again one or two years down the line (this happened before a few years ago according to the forums. Like this very issue, with comcast users and users who's ISPs used Comcast's lanes.)I'm not sure if it's just ISP, or perhaps there's a bump in the tubes we are all going through. Doing alliance raids for the relic and have been watching alliance members get the red ring of death over the past two nights. Seen tanks dc and just did myself.
This is on primal
There's a bandaid fix userend that you can try, I'll link it. Otherwise stick with a VPN that can bypass the node that's having issues (eg using Mozilla VPN and routing it thru LA seems to work for a lot of people)
Thanks!! I'll try that out.It's a problem with a node that SE and Comcast communicate thru. It's something Comcast can fix, and it's something NTT can fix, but there's no amount of work that can fix it on XIV's end other than someone from SE talking to someone from NTT. And considering the amount of cheaping-out that's been going on in the US lately in regards to ISPs (NTT being the middleman ISP SE uses for Comcast), it's highly likely they'll bandaid fix it and the problem will happen again one or two years down the line (this happened before a few years ago according to the forums. Like this very issue, with comcast users and users who's ISPs used Comcast's lanes.)
There's a bandaid fix userend that you can try, I'll link it. Otherwise stick with a VPN that can bypass the node that's having issues (eg using Mozilla VPN and routing it thru LA seems to work for a lot of people)




https://www.reddit.com/r/ffxiv/comme...tfast_cheaper/
https://mudfish.net/
This is the solution I linked in another thread and it seemed to work for some people. Give that a try as well (may end up cheaper than the Mozilla VPN solution too! You only pay for what you use and a user indicated that for several hours of XIV gameplay they paid 12 cents out of the $5 they put in.)
Edit:
Another fix that worked for some other people. If the above two don't work then try this.I just wanted to post this here aside from general discussion. It's a bandaid and this still needs to be looked into; however, Cloudflare 1.1.1.1 fixed my lag and it's free. I feel like FFXIV has had issues with particular DNS services from various ISPs in the past. If you wanna download it, it's here: https://1.1.1.1/
Unfortunately I'm on PS4 using the Xfinity modem-router combo. I have a VPN already for my computer but in order for my PS4 to connect through that VPN I would need to install it on a separate router as the Xfinity one does not support VPNs.
I'm also on Comcast, gigabit but not like it matters with this company, these issues started occurring a few days ago for me. The game was honestly unplayable for me. It's worth changing your dns to cloudflare or google. If you're using a router do it there or if you have a straight connection to your modem then use the normal ip4 or ip6 settings. Just google how to change your dns if you're unsure of the process. It doesn't harm anything and you can always revert back to your normal dns later on by simply reverting the changes you've made.

I have Comcast and the lag seems to pop up after 10 PM EST time. Friday night it was just horrible doing Titan Unreal. It was fine till the later stages, then I would freeze for like 10-30 seconds, which of course killed me.
To fix it I got my company's cell phone and made a hot spot with it, then connected my computer wirelessly to it. Lag went bye-bye and I had no more issues that night.
Saturday I installed a free VPN on my computer and used it Saturday night with Titan Unreal again. No Lag at all and I played until Midnight EST time. So yeah, it's related to Comcast somehow, at least with my issue.
I really hope it goes away soon, then again I rarely play late anyway, so I can just not right now to avoid the current issues if need be.
|
|
![]() |
![]() |
![]() |
|
|
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




