Recent lag issues and the tech-support incompetence

[Hustensaft]

Call your ISP, send a report so the ISPs can fight it out. I am sure this is causing problems to thousands of people and businesses.

What responsibility has my ISP? Their service ends past the KDDI network. The issue is very likely in an IP-range SE has ownership off. What exactly should my ISP fight here for? "Hey guys, you might have some issues in your network, my customer, which is also your customer is complaining about it"? Why should i go to my ISP for an issue, when the ownership of the problem lies within SE? d

WoW tech support vastly outperform this (aka make sure the connecitivity issues are not part of their network). There has never been any talk about "their side" from SE whenever connectivity issues are discussed....
(here for some example how connectivity issues are treated by WoW CS... https://us.forums.blizzard.com/en/wo...ently/459392/9 - there are miles in the quality of support provided.)

literally this! I too at first accused SE servers being messed up but after investigating and being educated SE really cant do anything. The router issues can only be resolve so many ways and the one that is currently with me is to hard reset my router and clear the addresses from storage and voila my connection was great until it filled up again.

There are more then one reason for connection issues, some are resolved locally, some by your ISP, and some are at the other end (where your ISP can't do anything)

[dotsforlife]

NTT and one of their particular nodes on the west coast has been trash for years. It's usually that 9/10 times. Not something your ISP or SE can do about as they don't have control over that.

[Xtrasweettea]

What responsibility has my ISP? Their service ends past the KDDI network. The issue is very likely in an IP-range SE has ownership off. What exactly should my ISP fight here for? "Hey guys, you might have some issues in your network, my customer, which is also your customer is complaining about it"? Why should i go to my ISP for an issue, when the ownership of the problem lies within SE?

Your ISP will be able to determine if it is truly SE's end or a router on the path to the CPE that contains the IP address range SE "owns."

If it is a router within the path that goes from your CPE to SE's CPE, your ISP can have a case against the other service providers as your service provider's traffic must be able to transmit across other carrier's devices. Some companies have even special contracts and routing paths between the two carriers to hold them accountable (I have helped sign a few of those). Also, counting on the law within the region, the ISP causing the problem could be in violation of the law.

That is why you should reach out to your ISP. It is to hold ISPs accountable.

If it is truly SE's fault, and your ISP can provide proof, then you can send a report ticket to SE via customer service or tech support with that proof. Not to the forums. The forums are not going to really help you.

Again, I am an ISP shill, I work for one, I am telling you what you can do to possibly fix the issue.

[Macleod]

Again, I am an ISP shill, I work for one, I am telling you what you can do to possibly fix the issue.

I appreciate your posts in this thread, as I said before, I don't know much about this kind of stuff and am finding your posts very insightful and informative...and also making me glad I have a good ISP and never really had any issues!

[Packetdancer]

KDDI is the carrier and owner of that particular router along the backbone. 195.82.50.234, in particular is the one causing the lag spike. IP address 195.82.50.60 is to be the assumed CPE for SE. I am going to assume KDDI owns the transport for that IP address.

Similarly—at least for my FC-mates—the lag they're seeing to Primal is on the Comcast/NTT border... but apparently it's the router one hop before the Comcast side of the border with NTT that's choking on a hairball right now. Which would put the problem within Comcast's network (albeit only just). If what they've said about their traceroutes is accurate, SquareEnix can sure ask NTT to try to fix it, but even then all NTT can do is go ask Comcast to fix it.

Mind you, I am just going on what others have said about their traceroute experimentation; I cannot provide a traceroute for that because I'm on CenturyLink rather than Comcast. (Which also means I haven't experienced any lag like my FC mates on Comcast, save for a brief hiccup of latency last week when something happened in the Qwest network that sits between my CenturyLink service and NTT.)

[Wolwosh]

Me and a lot of my friends had a lot of lag issues lately. I normally never notice it, but lately I do. Nothing changed on our end

[technole]

NTT and one of their particular nodes on the west coast has been trash for years. It's usually that 9/10 times. Not something your ISP or SE can do about as they don't have control over that.

Probably that San Jose hop, seems to have some issues at-times on the way to the NTT data center in Sacremento. Lag Tuesdays is becoming a joke now with that hop, everything else is great.

If it is truly SE's fault, and your ISP can provide proof, then you can send a report ticket to SE via customer service or tech support with that proof. Not to the forums. The forums are not going to really help you.

Again, I am an ISP shill, I work for one, I am telling you what you can do to possibly fix the issue.

Actually they can, cause SE just submits the issue over to NTT to investigate if it's in their data center routing.