Recent lag issues and the tech-support incompetence

[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.

[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