• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

New East Coast CS Server...please test and populate, 66.154.88.88:27015

M

marill999

Senior member
New East Coast CS server up and running...come test it out and see if you ping well


ELITE WARZONE OC48 FF ON - [D3a7h 1n eV3ry WaY]

IP: 66.154.88.88:27015
Location: Atlanta, GA - USA
Connection: OC48
Max Players: 20
Anticheats: CSGuard 8.00, Cheating Death Optional v1.2.3 (Updated Frequently) - NO CHEATING
Plugins: AdminMod, StatsMe, Ultrakill, LastMan, PsychoStats, etc.
Stats: http://www.diewclan.com
FF ON, Custom Maps Votable
Friendly players of all skill levels welcomed!
Hosted by LightSpeed Gaming


I'm looking to fill the server up with clans, skilled and dedicated players as well as European players to keep the server busy 24/7.
FF is ON to be more in line with league play.

My clan [DiEw] who recently finished the CAL-O season @ 6-2 play here very often.
 


<< anyone wanna share their tracert on our server ip? or their ping? >>



Reply from 66.154.88.88: bytes=32 time=110ms TTL=109
Reply from 66.154.88.88: bytes=32 time=101ms TTL=109
Reply from 66.154.88.88: bytes=32 time=100ms TTL=109
Reply from 66.154.88.88: bytes=32 time=110ms TTL=109


Tracing route to 66.154.88.88 over a maximum of 30 hops

1 20 ms 10 ms 10 ms 10.87.88.1
2 10 ms 10 ms 20 ms 12.244.100.129
3 41 ms 20 ms 10 ms 12.244.67.14
4 30 ms 30 ms 30 ms 12.244.72.206
5 30 ms 40 ms 60 ms gbr1-p70.sffca.ip.att.net [12.123.13.58]
6 30 ms 30 ms 30 ms gbr4-p00.sffca.ip.att.net [12.122.5.250]
7 30 ms 70 ms 40 ms gbr3-p20.la2ca.ip.att.net [12.122.2.70]
8 120 ms 70 ms 120 ms gbr3-p30.dlstx.ip.att.net [12.122.3.69]
9 80 ms 130 ms 90 ms gbr4-p40.attga.ip.att.net [12.122.3.38]
10 90 ms 90 ms 90 ms gbr2-p100.attga.ip.att.net [12.122.1.198]
11 90 ms 80 ms 90 ms ar14-a3120s2.attga.ip.att.net [12.123.21.37]
12 * * * Request timed out.
13 120 ms 100 ms 130 ms border4.ge2-0-bbnet1.acs.pnap.net [64.94.0.9]
14 90 ms 110 ms 110 ms mariet-2.border4.acs.pnap.net [64.94.3.98]
15 150 ms 100 ms 100 ms 216.235.146.254
16 100 ms 100 ms 100 ms core1-atl1-ag2.globalcompass.com [66.154.95.196]
17 100 ms 120 ms 100 ms 66.154.88.88

from fremont, ca

edit: opps.. im on AT&T Broadband cable... 🙂
 
that's not bad being that ur in california, and im guessing u have broadband?

Here's mine:

  • Microsoft(R) Windows DOS
    (C)Copyright Microsoft Corp 1990-2001.

    C:\DOCUME~1\MATTHE~1>tracert 66.154.88.88

    Tracing route to 66.154.88.88 over a maximum of 30 hops

    1 160 ms 174 ms 154 ms tnt2.nyc9.da.uu.net [67.192.184.1]
    2 180 ms 435 ms 173 ms 67.192.184.130
    3 280 ms 155 ms 164 ms 266.at-2-0-0.HR2.NYC9.ALTER.NET [152.63.26.78]
    4 142 ms 163 ms 165 ms 0.so-2-3-0.XL2.NYC9.ALTER.NET [152.63.15.198]
    5 144 ms 163 ms 164 ms 0.so-4-0-0.TL2.NYC9.ALTER.NET [152.63.23.129]
    6 180 ms 174 ms 194 ms 0.so-4-0-0.TL2.ATL1.ALTER.NET [152.63.101.49]
    7 184 ms 174 ms 173 ms 0.so-7-0-0.XL4.ATL1.ALTER.NET [152.63.86.102]
    8 180 ms 183 ms 155 ms 194.ATM4-0.GW4.ATL3.ALTER.NET [152.63.81.53]
    9 190 ms 164 ms 174 ms meagpower-gw.customer.alter.net [157.130.82.226]

    10 171 ms 174 ms 193 ms 63.251.78.194
    11 172 ms 174 ms 184 ms 216.235.146.254
    12 182 ms 174 ms 174 ms core1-atl1-ag2.globalcompass.com [66.154.95.196]

    13 712 ms 950 ms 1036 ms 66.154.88.88

    Trace complete.

THis on 56k in NY!
 
im in ny... my ping is 31-41 laters i might show up later... but i currently play in NYC HOT GIRLS DUAL OC3... i get a 10-20 ping in there =] laters
 
From the major Rogers Hi-Speed cable backbone in the Toronto, Canada area:


Pinging 66.154.88.88 with 32 bytes of data:

Reply from 66.154.88.88: bytes=32 time=70ms TTL=114
Reply from 66.154.88.88: bytes=32 time=50ms TTL=114
Reply from 66.154.88.88: bytes=32 time=50ms TTL=114
Reply from 66.154.88.88: bytes=32 time=70ms TTL=114

Ping statistics for 66.154.88.88:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 50ms, Maximum = 70ms, Average = 60ms


I think you'll see a lot of happy Canadian gamers over there.
 
Pinging 66.154.88.88 with 32 bytes of data:

Reply from 66.154.88.88: bytes=32 time=54ms TTL=109
Reply from 66.154.88.88: bytes=32 time=52ms TTL=109
Reply from 66.154.88.88: bytes=32 time=59ms TTL=109
Reply from 66.154.88.88: bytes=32 time=54ms TTL=109

Ping statistics for 66.154.88.88:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 52ms, Maximum = 59ms, Average = 54ms

C:\tracert 66.154.88.88

Tracing route to 66.154.88.88 over a maximum of 30 hops

1 1 ms 1 ms 1 ms 192.168.1.1
2 16 ms 13 ms 12 ms 10.93.240.1
3 79 ms 11 ms 11 ms 12.244.107.1
4 11 ms 12 ms 11 ms 12.244.68.1
5 15 ms 61 ms 14 ms 12.244.72.226
6 37 ms 17 ms 13 ms gbr2-p100.cgcil.ip.att.net [12.123.5.78]
7 13 ms 13 ms 15 ms gbr3-p00.cgcil.ip.att.net [12.122.5.222]
8 44 ms 65 ms 31 ms gbr3-p10.n54ny.ip.att.net [12.122.2.1]
9 82 ms 35 ms 39 ms gbr3-p10.wswdc.ip.att.net [12.122.3.54]
10 113 ms 43 ms 130 ms gbr4-p60.wswdc.ip.att.net [12.122.1.130]
11 85 ms 50 ms 92 ms gbr4-p30.attga.ip.att.net [12.122.2.225]
12 50 ms 99 ms 107 ms gbr1-p60.attga.ip.att.net [12.122.5.209]
13 52 ms 61 ms 82 ms ar14-a3120s1.attga.ip.att.net [12.123.21.29]
14 * * * Request timed out.
15 66 ms 89 ms 53 ms border4.ge3-0-bbnet2.acs.pnap.net [64.94.0.73]
16 53 ms 50 ms 52 ms mariet-2.border4.acs.pnap.net [64.94.3.98]
17 111 ms 56 ms 79 ms 216.235.146.254
18 53 ms 54 ms 69 ms core1-atl1-ag2.globalcompass.com [66.154.95.196]

19 54 ms 55 ms 70 ms 66.154.88.88

Trace complete.
 
Tracing route to 66.154.88.88 over a maximum of 30 hops

1 <10 ms <10 ms <10 ms 192.168.200.1
2 27 ms 14 ms 27 ms cis200.navix.net [162.40.125.6]
3 14 ms 27 ms 14 ms 162.40.125.3
4 27 ms 14 ms 27 ms 162.40.115.21
5 27 ms 28 ms 27 ms 500.POS2-1.GW1.KCY4.ALTER.NET [65.206.176.25]
6 27 ms 28 ms 27 ms 156.at-6-0-0.XR1.STL3.ALTER.NET [152.63.92.198]

7 28 ms 27 ms 28 ms 0.so-1-0-0.TL1.STL3.ALTER.NET [152.63.88.241]
8 69 ms 68 ms 69 ms 0.so-4-0-0.TL1.ATL1.ALTER.NET [146.188.136.173]

9 69 ms 68 ms 69 ms 0.so-7-0-0.XL3.ATL1.ALTER.NET [152.63.86.86]
10 68 ms 69 ms 69 ms 195.ATM5-0.GW4.ATL3.ALTER.NET [152.63.81.49]
11 69 ms 69 ms 68 ms meagpower-gw.customer.alter.net [157.130.82.226]

12 68 ms 69 ms 69 ms 63.251.78.194
13 69 ms 68 ms 69 ms 216.235.146.254
14 69 ms 69 ms 68 ms core1-atl1-ag2.globalcompass.com [66.154.95.196]

15 68 ms 69 ms 69 ms 66.154.88.88

Trace complete.

Not bad. 🙂 Maybe you will see me on sometimes. Have fun in caleague. 😀
 
Wow, what a coincidence. My roommate was playing on that server all night Friday night and we both played there on and off yesterday. I didn't know it was in Atlanta, but it certainly explains our low pings. Now our two favorite servers are both located in Atlanta, less than 2 hours from here.
 
It's great to know how good a ping everyone gets in our server and not mention that you guys actually played on it! Thanks alot for the support!
 
also i was hoping you people might consider remember the ip? especially since its such a simple and easy to remmeber one... 66.154.88.88 gotta love those 88's!
 

D:\Sounds>ping 66.154.88.88

Pinging 66.154.88.88 with 32 bytes of data:

Reply from 66.154.88.88: bytes=32 time=56ms TTL=109
Reply from 66.154.88.88: bytes=32 time=51ms TTL=109
Reply from 66.154.88.88: bytes=32 time=52ms TTL=109
Reply from 66.154.88.88: bytes=32 time=52ms TTL=109

Ping statistics for 66.154.88.88:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 51ms, Maximum = 56ms, Average = 52ms

D:\Sounds>ping 66.154.88.88

Pinging 66.154.88.88 with 32 bytes of data:

Reply from 66.154.88.88: bytes=32 time=51ms TTL=109
Reply from 66.154.88.88: bytes=32 time=52ms TTL=109
Request timed out.
Reply from 66.154.88.88: bytes=32 time=52ms TTL=109

Ping statistics for 66.154.88.88:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 51ms, Maximum = 52ms, Average = 51ms

D:\Sounds>
 

D:\Sounds>ping 66.154.88.88

Pinging 66.154.88.88 with 32 bytes of data:

Reply from 66.154.88.88: bytes=32 time=56ms TTL=109
Reply from 66.154.88.88: bytes=32 time=51ms TTL=109
Reply from 66.154.88.88: bytes=32 time=52ms TTL=109
Reply from 66.154.88.88: bytes=32 time=52ms TTL=109

Ping statistics for 66.154.88.88:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 51ms, Maximum = 56ms, Average = 52ms

D:\Sounds>ping 66.154.88.88

Pinging 66.154.88.88 with 32 bytes of data:

Reply from 66.154.88.88: bytes=32 time=51ms TTL=109
Reply from 66.154.88.88: bytes=32 time=52ms TTL=109
Request timed out.
Reply from 66.154.88.88: bytes=32 time=52ms TTL=109

Ping statistics for 66.154.88.88:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 51ms, Maximum = 52ms, Average = 51ms

D:\Sounds>ping 66.154.88.88

Pinging 66.154.88.88 with 32 bytes of data:

Reply from 66.154.88.88: bytes=32 time=52ms TTL=109
Reply from 66.154.88.88: bytes=32 time=49ms TTL=109
Reply from 66.154.88.88: bytes=32 time=57ms TTL=109
Reply from 66.154.88.88: bytes=32 time=48ms TTL=109

Ping statistics for 66.154.88.88:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 48ms, Maximum = 57ms, Average = 51ms

D:\Sounds>ping 66.154.88.88

Pinging 66.154.88.88 with 32 bytes of data:

Reply from 66.154.88.88: bytes=32 time=52ms TTL=109
Reply from 66.154.88.88: bytes=32 time=51ms TTL=109
Reply from 66.154.88.88: bytes=32 time=52ms TTL=109
Reply from 66.154.88.88: bytes=32 time=50ms TTL=109

Ping statistics for 66.154.88.88:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 50ms, Maximum = 52ms, Average = 51ms

D:\Sounds>ping 66.154.88.88

Pinging 66.154.88.88 with 32 bytes of data:

Reply from 66.154.88.88: bytes=32 time=49ms TTL=109
Reply from 66.154.88.88: bytes=32 time=51ms TTL=109
Reply from 66.154.88.88: bytes=32 time=49ms TTL=109
Reply from 66.154.88.88: bytes=32 time=46ms TTL=109

Ping statistics for 66.154.88.88:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 46ms, Maximum = 51ms, Average = 48ms

D:\Sounds>ping 66.154.88.88

Pinging 66.154.88.88 with 32 bytes of data:

Reply from 66.154.88.88: bytes=32 time=47ms TTL=109
Reply from 66.154.88.88: bytes=32 time=46ms TTL=109
Reply from 66.154.88.88: bytes=32 time=47ms TTL=109
Reply from 66.154.88.88: bytes=32 time=48ms TTL=109

Ping statistics for 66.154.88.88:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 46ms, Maximum = 48ms, Average = 47ms

D:\Sounds>ping 66.154.88.88

Pinging 66.154.88.88 with 32 bytes of data:

Reply from 66.154.88.88: bytes=32 time=47ms TTL=109
Reply from 66.154.88.88: bytes=32 time=51ms TTL=109
Reply from 66.154.88.88: bytes=32 time=48ms TTL=109
Reply from 66.154.88.88: bytes=32 time=51ms TTL=109

Ping statistics for 66.154.88.88:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 47ms, Maximum = 51ms, Average = 49ms

D:\Sounds>ping 66.154.88.88

Pinging 66.154.88.88 with 32 bytes of data:

Reply from 66.154.88.88: bytes=32 time=48ms TTL=109
Reply from 66.154.88.88: bytes=32 time=54ms TTL=109
Reply from 66.154.88.88: bytes=32 time=47ms TTL=109
Reply from 66.154.88.88: bytes=32 time=50ms TTL=109

Ping statistics for 66.154.88.88:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 47ms, Maximum = 54ms, Average = 49ms

D:\Sounds>
 

C:\>tracert 66.154.88.88

Tracing route to 66.154.88.88 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms esr001-resnet-wwads.tc.mtu.edu [141.219.72.1]
2 3 ms 1 ms 1 ms esr003-esr002.tc.mtu.edu [141.219.246.3]
3 4 ms 2 ms 3 ms fe0-0.mtu2.mich.net [198.110.131.61]
4 18 ms 16 ms 23 ms at-1-1-0x8.nl-chi3.mich.net [198.108.23.141]
5 18 ms 14 ms 14 ms aads.verio.net [206.220.243.34]
6 19 ms 19 ms 14 ms p4-6-0-0.r01.chcgil01.us.bb.verio.net [129.250.2
.254]
7 44 ms 40 ms 43 ms p16-2-0-0.r02.stngva01.us.bb.verio.net [129.250.
5.103]
8 48 ms 45 ms 39 ms p16-7-0-0.r02.mclnva02.us.bb.verio.net [129.250.
5.47]
9 44 ms 44 ms 39 ms p16-0-0-0.r01.mclnva02.us.bb.verio.net [129.250.
5.253]
10 58 ms 62 ms 58 ms p16-0-0-0.r00.atlnga03.us.bb.verio.net [129.250.
2.49]
11 66 ms 64 ms 58 ms ge-0-0-0.a01.atlnga03.us.ra.verio.net [129.250.2
6.228]
12 47 ms 48 ms 43 ms d3-0-1-1.a01.atlnga03.us.ce.verio.net [157.238.1
62.254]
13 45 ms 45 ms 43 ms border4.ge2-0-bbnet1.acs.pnap.net [64.94.0.9]
14 45 ms 50 ms 45 ms mariet-2.border4.acs.pnap.net [64.94.3.98]
15 55 ms 55 ms 57 ms 216.235.146.254
16 51 ms 52 ms 45 ms core1-atl1-ag2.globalcompass.com [66.154.95.196]

17 54 ms 53 ms 54 ms 66.154.88.88

Trace complete.

C:\>
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top