Atlanta

Post by **Edge100x** » Sat Feb 07, 2004 12:46 am

I haven't made an official news post about Atlanta and I really should, so here it is.

We're in Atlanta!

We've gone with Atlanta because it is a decently central area on the East coast with good pings to both East and Central US and because it is a major metropolitan area in its own right. We've gone with InterNAP there because they have served us so well in Seattle, and because we know the bandwidth will be outstanding since it is where they have moved their corporate headquarters and primary NOC (which were in Seattle when we first started).

Our test server in Atlanta is called "http://rentals.nuclearfallout.net Atlanta test (accelerated)" and as the name suggests it is accelerated. The test server is running on a dual Opteron 244 machine with 2gb of RAM, part of a new crop of machines we have started investing in to replace our aging (though still very fast) fleet of existing boxes. Please give it a shot and tell us how it does for you -- with this combination of hardware and bandwidth, we're sure you will be amazed.

aBstracT · Post by **aBstracT** » Sat Feb 07, 2004 2:14 pm

I ping 50 from la to atlanta.

Post by **Edge100x** » Sat Feb 07, 2004 3:17 pm

I ping 90 from Seattle.

bOoya · Post by **bOoya** » Sun Feb 08, 2004 1:45 pm

i ping better to atlanta than i do to seattle.
from socal....
50 vs 70

aBstracT · Post by **aBstracT** » Sun Feb 08, 2004 3:26 pm

bOoya · Post by **bOoya** » Sun Feb 08, 2004 4:16 pm

ya id love to get some tracerts but for some reason i cant run them.

erax0r · Post by **erax0r** » Sun Feb 08, 2004 8:58 pm

I'm in mid easter washington state, wasnt expecting much. Heres my trace and ping.

[andrewg@techs andrewg]$ traceroute 64.94.238.5
traceroute to 64.94.238.5 (64.94.238.5), 30 hops max, 38 byte packets
1 pasco-core** (207.254.*.*) 12.933 ms 2.107 ms 2.284 ms
2 sea-noanet.*.net (207.254.*.*) 19.822 ms 15.756 ms 16.025 ms
3 *-gw.fa6-6.167.col-cor0.noanet.net (66.119.207.253) 27.047 ms 26.704
ms 26.913 ms
4 srp2-0.ros-cor0.noanet.net (66.119.192.18) 35.444 ms 32.790 ms 36.137 ms
5 ge-4-2.a01.ptldor04.us.ra.verio.net (157.238.24.133) 35.442 ms 35.253 ms
36.570 ms
6 ge-1-0-0.a00.ptldor04.us.ra.verio.net (129.250.55.121) 36.741 ms 36.590 ms
34.232 ms
7 p4-1-1-0.r01.ptldor01.us.ra.verio.net (129.250.55.95) 35.961 ms 38.706 ms
35.715 ms
8 ge-1-0-0.r01.ptldor01.us.bb.verio.net (129.250.30.145) 36.206 ms 36.598 ms
36.500 ms
9 p4-6-1-0.r04.sttlwa01.us.bb.verio.net (129.250.3.37) 41.972 ms 39.656 ms
41.386 ms
10 p16-0-1-0.r21.sttlwa01.us.bb.verio.net (129.250.2.236) 38.359 ms 39.743 ms
39.658 ms
11 p16-0-0-0.r00.chcgil06.us.bb.verio.net (129.250.2.7) 79.748 ms 80.916 ms
80.622 ms
12 p16-1-0-0.r01.chcgil06.us.bb.verio.net (129.250.5.77) 79.506 ms 76.481 ms
76.731 ms
13 p16-1-1-0.r21.dllstx09.us.bb.verio.net (129.250.5.85) 101.373 ms 100.693 m
s 103.153 ms
14 xe-0-0-0.r20.dllstx09.us.bb.verio.net (129.250.2.222) 106.711 ms 103.846 m
s 102.339 ms
15 p16-1-1-2.r20.dllstx01.us.bb.verio.net (129.250.2.150) 102.869 ms 132.241
ms 105.856 ms
16 p16-0-0-0.r01.atlnga03.us.bb.verio.net (129.250.4.195) 127.855 ms 126.130
ms 127.805 ms
17 ge-1-0-0.a01.atlnga03.us.ra.verio.net (129.250.25.67) 128.272 ms 128.807 m
s 127.563 ms
18 pos4-2-0-0.a01.atlnga01.us.ce.verio.net (157.238.161.170) 127.702 ms 128.2
73 ms 127.181 ms
19 border6.ge3-1-bbnet1.acs.pnap.net (64.94.0.11) 125.861 ms 126.099 ms 125.
943 ms
20 64.94.238.5 (64.94.238.5) 127.381 ms 127.442 ms 129.401 ms

[andrewg@techs andrewg]$ ping 64.94.238.5
PING 64.94.238.5 (64.94.238.5) from 207.254.*.* : 56(84) bytes of data.
64 bytes from 64.94.238.5: icmp_seq=1 ttl=108 time=130 ms
64 bytes from 64.94.238.5: icmp_seq=2 ttl=108 time=126 ms
64 bytes from 64.94.238.5: icmp_seq=3 ttl=108 time=128 ms
64 bytes from 64.94.238.5: icmp_seq=4 ttl=108 time=125 ms
64 bytes from 64.94.238.5: icmp_seq=5 ttl=108 time=127 ms
64 bytes from 64.94.238.5: icmp_seq=6 ttl=108 time=126 ms
64 bytes from 64.94.238.5: icmp_seq=7 ttl=108 time=126 ms

--- 64.94.238.5 ping statistics ---
7 packets transmitted, 7 received, 0% loss, time 6059ms

Post by **Edge100x** » Sun Feb 08, 2004 9:03 pm

That's probably pretty standard from the Northwest area, actually. In the continental US, Seattle is about the furthest you can get from Atlanta, and distance is a big part of latency. Of course, Verio isn't too awesome either.

erax0r · Post by **erax0r** » Sun Feb 08, 2004 9:12 pm

Definately not a bad ping from a west coaster to an east coaster. I was actually surprised to see it below 200. Considering most east servers I've played on range from 200-300 ping.

aBstracT · Post by **aBstracT** » Sun Feb 08, 2004 9:15 pm

I'm suprised im getting 50 - 60 -_-

crab · Post by **crab** » Mon Feb 09, 2004 2:54 pm

I ping around 95 from Lynden, WA (north of Bellingham right on the canadian border). What i'm most suprised about though is how smooth it ran. It was better than other servers i've played on with a 50 ping.

The biggest problem is the number of hackers in there. In the half hour I played I had 2 hackers banned and when the 3 showed up I decided I had enough.

aBstracT · Post by **aBstracT** » Mon Feb 09, 2004 4:21 pm

Really? I havn't seen a hacker there yet. :/

bOoya · Post by **bOoya** » Mon Feb 09, 2004 9:56 pm

heheh if we ever catch a hacker in there... they shall be 'dealt' with

|dC|2bit · Post by **|dC|2bit** » Wed Feb 11, 2004 12:45 pm

To get the word out about NFo:Alanta we could rent a van(fill it with NFo groupies), put NFo ads on each side. Then drive from LA or Seattle to Atlanta. The "route" we take must follow the hops from one of west coast servers to the Atlanta servers.

crab · Post by **crab** » Wed Feb 11, 2004 1:43 pm

I think the word is getting out. The server is always busy, busier than gz sometimes. I've been playing there quite a bit and I hear a lot of the players raving about how much they love the server.

Server rentals :: NFOservers.com

Atlanta

Atlanta

not bad