[Data Center USA] Ping increased. Report your changes here.

[RaijinSupreme]

good riddance

[Jaxelyn]

Yeah, but then you would have to thing about the fact that the internet needs a bit of time to learn about moved IPs and dns records being changed.

I also enjoy how much people believe they know about ping or the real location of the servers, since it no longer looks like Cali.... and really didn't earlier today either. Sadly I couldn't sign in before though *shrug*

[Raikki]

Earlier I was getting around 105ms... now it's 138ms. Route didn't change, but there's a massive latency increases between two points on NTT's backbone where there wasn't before (Seattle and San Jose). I guess this is the quality infrastructure I can expect from here on out unless I pay for a VPN to route around it. Thanks, SE.

Edit: oh joy, there's packet loss that starts at the same hop and carries through to the destination, too.

[Hestzhyen]

Why are so many folks who are chilling out in the 100-199 range freaking out?
I played on an NA server with a ping of around 210-240 for 3 years while I was in Japan. It didn't really affect me except in Titan.
If you are under 100ms like a good majority of the folks I see panicking you're more than fine.

We're used to playing with far less latency and it will take a long time to adjust- some moreso than others. I've played other games with servers out in California and my ISP does not often pick the best route to get my data from Point A to Point B. Heck my friend and I played LoL for a while with a ping that constantly hovered between 120~150 and it was awful (large part of why I quit despite playing since it was freshly out of beta). It just kind of sucks to not live on or near the West Coast if you play online games. I'm not gonna unsub or start failing in raids or anything like that, I'm just a little bummed.

[Jaxelyn]

Earlier I was getting around 105ms... now it's 138ms. Route didn't change, but there's a massive latency increases between two points on NTT's backbone where there wasn't before (Seattle and San Jose). I guess this is the quality infrastructure I can expect from here on out unless I pay for a VPN to route around it. Thanks, SE.

You do understand they are still setting up the equipment right? The whole reason everyone is hanging out on the forums.

[Kallistra]

My girlfriend lives in Canada and she just watched her ping go from 100 to 480.

[Lesan]

Playing from.EU, old DC meant around 140-170 ms for me, which often enough meant that oGCD use was wonky, and in case of playing Healer, caused issues with 'stance dance', or caused my DRG to do DRG things like drop BotD or die.

If my connection now drops to 200+ latency, I'm going to unsub, unless SE pays for the 'Gamer VPN' for me, or provides a no-restrictions chartransfer for free.

[Sida]

You do understand they are still setting up the equipment right? The whole reason everyone is hanging out on the forums.

Made me imagine some small car trying to navigate in some festival avenue beforehand to check the route, just to be stuck in the midds of the trucks that are taking the equipment there, and ending up cursing the congested traffic. Possibly totally unrelated ^^

[Hestzhyen]

Earlier I was getting around 105ms... now it's 138ms. Route didn't change, but there's a massive latency increases between two points on NTT's backbone where there wasn't before (Seattle and San Jose). I guess this is the quality infrastructure I can expect from here on out unless I pay for a VPN to route around it. Thanks, SE.

Edit: oh joy, there's packet loss that starts at the same hop and carries through to the destination, too.

SE can't control what quality of service those providers serve. All they can do is make sure the connection from their data center to the rest of the internet is as good as it can be. It's your ISP that decides how to get your information to SE's servers, not SE.

[Raikki]

You do understand they are still setting up the equipment right? The whole reason everyone is hanging out on the forums.

The issue on the network is in a different location unrelated what they're doing at the datacenter. It's an NTT infrastructure problem.

SE can't control what quality of service those providers serve. All they can do is make sure the connection from their data center to the rest of the internet is as good as it can be. It's your ISP that decides how to get your information to SE's servers, not SE.

This is incorrect. NTT's internal routing is responsible here. Your ISP just gets you onto their backbone, then their internal routing dictates how to get you to the server.