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

[Hestzhyen]

Congratz on trying to insult someone who knows what they are talking about.
http://whatismyipaddress.com/ip/204.2.229.9

The IP is now showing Michigan, where before the hop before tracert timed out was California. On top of the fact that I am a network engineer. So everyone can keep crying about California, or they can figure out it's not actually California.

I believe you, it's just that it's still going all the way out to Sacramento when I do a tracert. I know enough about networking to be dangerous in the advice I give and assumptions I make- not enough to grasp the full reason why. If the geolocation is Michigan, why am I getting routed out to Sacramento before it resolves?

[SeraphicRadiance]

I think them not disclosing it has to do with some legal mumbo jumbo, but I wouldn't know, really.

That makes a little more sense.

On the other hand, Frankfurt is about as optimal as a location as it could have been to host the datacenter. Europe's infrastructure is much, MUCH better compared to the United States, in addition to it being in close to the most ideal location for the European playerbase as possible.

People are scared because the infrastructure in the United States is hot garbage in the first place, on top of the already notoriously unreliable routing that the majority of people have had side effects from in this game.

[Bjond]

While I love the CA choice for myself (12ms ping), it is obviously not a good choice for the health of ANY online game they intend to offer within north and south america. The physics of the situation pretty much dictates Texas -- mid-southern USA as the ideal place to offer the best potential latency to both continents. SE knows this.

Our new datacenter seems to be NTT/RagingWire's CA3 spot. Why didn't they choose the TX1 spot? My bet is that TX1 is not ready; they *just* opened it. I'd further speculate that there could easily be either another move planned to TX1 or future/other games planned for TX1 site if NTT does a good job with the CA3 site. Another move would depend greatly on how smooth this one goes for them. If they find it to be cheap and painless and SB really takes off, it could move again in 6~12 months. By then, the TX1 site will be ready.

[EdgeFayth]

I live in BC (Canadian West Coast).
On the previous server location (in the same country), I was getting ~120 ms ping with no packet loss. Not that nice (compared to the 15 ms i got when I was living in Japan and playing on a JP server), but playable.
I pinged the server from work (business line), and I was happy to see a constant 35 ms ping! Great !
Then I went back home (non business line). And I am crying...

--- 204.2.229.9 ping statistics ---
429 packets transmitted, 419 received, 2% packet loss, time 428552ms
rtt min/avg/max/mdev = 28.498/106.945/956.069/89.694 ms

same "average" ping as before (even if the new server location is 2000 miles closer to before), and packet losses. I know this will make the game unplayable...

[technole]

I believe you, it's just that it's still going all the way out to Sacramento when I do a tracert. I know enough about networking to be dangerous in the advice I give and assumptions I make- not enough to grasp the full reason why. If the geolocation is Michigan, why am I getting routed out to Sacramento before it resolves?

The person is wrong, the trace route to NTT's CA2 Sacramento data center is correct.


Going to post this again.


Many people who don't know what they are talking about confusing WHOIS vs a trace route. I'll try to explain it in simple terms.

WHOIS is like the internet phonebook "white pages". Like when you buy a .com name, you have the choice to publish who administers and pays for that domain. The address information is published for anyone to see. This has no bearing where the server(s) for that domain lives. You can protect your assets by just putting a corporate address of your company as the white listing. But your server might actually be in another country.

Traceroute is basically sending a heartbeat from your PC and internet connection to see the actual pipelines it has to go through to get the end connection. This method reports every pipeline hop you have to go through including the end of the tunnel. This is how you actually discover the server(s) you end at because internet backbones and data centers generally use some city codes as part of their pipeline addresses because they have a lot of them.

[Jaxelyn]

I believe you, it's just that it's still going all the way out to Sacramento when I do a tracert. I know enough about networking to be dangerous in the advice I give and assumptions I make- not enough to grasp the full reason why. If the geolocation is Michigan, why am I getting routed out to Sacramento before it resolves?

I will give Raikki some knowledge in that I am looking at stuff provided online as much as everyone else is. But if the two updates I've seen today with the IP being claimed in Cali and then being claimed in Michigan, those routing changes need to be updated across all ISPs. If the backbone you connect to through your ISP knew the path to Cali from earlier in the day, until it receives an updated path, it's keeps going to Cali first and then is forwarded to Michigan. When I first started working for a local internet company, we told people DNS updates could take 24 hours and moving IP addresses don't happen instantaneously either.

[Coratanni]

Has anyone considered just waiting to see if it has any real impact on you before FREAKING OUT?

You make too much common sense. Please stop with that, it is not wanted here. People want to jump to conclusions and call it the end of the world before seeing if it is or not.

[Kethic]

I live in BC (Canadian West Coast).
--- 204.2.229.9 ping statistics ---
429 packets transmitted, 419 received, 2% packet loss, time 428552ms
rtt min/avg/max/mdev = 28.498/106.945/956.069/89.694 ms

same "average" ping as before (even if the new server location is 2000 miles closer to before), and packet losses. I know this will make the game unplayable...

That sounds like you need to upgrade your equipment at home. :-(

[Bourne_Endeavor]

WTFast / Battleping cannot magically improve latency generated by sheer distance. The only advantage these services provide is helping avoid 'bottlenecked' routing points. That can help to reduce problems when, say, Level 3 is the culprit, but it can't resolve the distance-added latency someone in Britain will be facing with this data centre move. It's incredibly disingenuous to suggest these paid VPN services designed for gaming can work miracles; they can't.

I didn't? I merely suggested either has a potential alternative. Both have a free trial service for you to test out. So please don't put words in my mouth.

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

Yeah... that's definitely her Internet provider or connection. I live in Montreal and got 103 with Bell Media.

[Kethic]

I think their first step is to get the server up and running, after which they can let the routing tables update their paths and costs. Even after the servers come up tonight, it could be hours, or days until we get a firm location indication.

Based on the ping test results I'm seeing, I suspect california is correct. We'll see.