Jump to content

Sim Locations - Moved from Washington to CA? Bad ping.


Nya Jules
 Share

You are about to reply to a thread that has been inactive for 4017 days.

Please take a moment to consider if this thread is worth bumping.

Recommended Posts

Hello,

according to my knowledge Linden Lab has been hosting part of the sims at Amazon in Washington, aside of those hosed in Texas.

Tracert taken from 3 years ago, I'm from Europe:

----------------

11 111 ms 114 ms 107 ms LINDEN-RESE.edge1.Washington12.Level3.net [4.26.4.2]
12 102 ms 111 ms 106 ms sw-core0-81.dca.lindenlab.com [216.82.7.206]
13 148 ms 100 ms 104 ms sim20595.agni.lindenlab.com [216.82.28.120]

--------------

My ping was around 120ms on those sims. Nowadays I noticed that those 120ms sims have gone, or do I just not find them? Instead I found several sims that are located in San Francisco.. where I didn't see any sims 3 years ago. I'm not overly fond of seeing sims move west. I mean, if I were using a text client I wouldn't mind a ping increase by 1/3 :smileyindifferent:

 

Does anyone know?

Link to comment
Share on other sites

There were 3 data centers. There are now only 2; Arizona and Dallas. Those are the asset servers and whatever else needs lots of silicon. 

One of the Lindens was saying there might be some in DC. I doubt it but the Lindens are not very informative when it comes to giving out details of the system... or all that well informed.

However the region servers seem to be in San Francisco (SF). Every time I pull a simulator's IP address and geo-locate it, it shows as being in SF. I've asked people on the east coast to check the IP addresses they are using. They are connecting to SF too.

I'm in SoCal. My PING runs from 40ms to 250ms with the average around 70ms.

The PING as measured by the Viewer is not the PING measured by your computer's ping commend. Try to ping a simulator address while your in the reagon using both the Viewer's ping and the computer's ping.

I don't have the delays you do when I reach across the states.

>tracert whitehouse.gov

Tracing route to whitehouse.gov [23.32.216.110]
over a maximum of 30 hops:

1 10 ms 1 ms 8 ms Dolphin2013.sd.cox.net [192.168.1.1]
2 17 ms 16 ms 10 ms 10.xxx.xx.1
3 18 ms 28 ms 21 ms escnaggc01-gex0314.sd.sd.cox.net [xxx.xx.x.130]
4 * * * Request timed out.
5 16 ms 20 ms 13 ms fed1dsrj02-xe120.0.rd.sd.cox.net [68.6.8.4]
6 56 ms 66 ms 27 ms 68.1.5.188
7 33 ms 43 ms 39 ms te0-7-0-1.ccr21.sjc04.atlas.cogentco.com [154.54.10.125]
8 36 ms 29 ms 29 ms be2014.ccr22.sjc03.atlas.cogentco.com [154.54.24.141]
9 36 ms 39 ms 42 ms qwest.sjc03.atlas.cogentco.com [154.54.12.190]
10 * * * Request timed out.
11 52 ms 63 ms 45 ms 65-113-36-2.dia.static.qwest.net [65.113.36.2]
12 46 ms 55 ms 49 ms a23-32-216-110.deploy.akamaitechnologies.com [23.32.216.110]

Trace complete.

Link to comment
Share on other sites

You are about to reply to a thread that has been inactive for 4017 days.

Please take a moment to consider if this thread is worth bumping.

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
 Share

×
×
  • Create New...