Quote Originally Posted by MilkieTea View Post
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)
Thanks!! I'll try that out.