• 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.

Help me Ping

S

splice

Golden Member
Hey guys,

I'm looking at setting up a colocated game server in Colorado at Level3's datacenter and I was wondering if you could help me out.

If you could: ping ns1.Denver1.Level3.net a couple times and report the ping average, your city/state, and ISP.

Thanks for the help! 😀
 
Pinging ns1.Denver1.Level3.net [209.244.4.104] with 32 bytes of data:

Reply from 209.244.4.104: bytes=32 time=60ms TTL=237
Reply from 209.244.4.104: bytes=32 time=120ms TTL=237
Reply from 209.244.4.104: bytes=32 time=70ms TTL=237
Reply from 209.244.4.104: bytes=32 time=50ms TTL=237

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

sanfrancisco, CA. Pacbell/SBC DSL.
 
Reply from 209.244.4.104: bytes=32 time=108ms TTL=239
Reply from 209.244.4.104: bytes=32 time=88ms TTL=239
Reply from 209.244.4.104: bytes=32 time=73ms TTL=239
Reply from 209.244.4.104: bytes=32 time=86ms TTL=239


Hanford, CA over a 1.5 mb/sec Frame Relay connection
 
Reply from 209.244.4.104: bytes=32 time=72ms TTL=241
Reply from 209.244.4.104: bytes=32 time=71ms TTL=241
Reply from 209.244.4.104: bytes=32 time=72ms TTL=241
Reply from 209.244.4.104: bytes=32 time=70ms TTL=241

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

Grand Forks, ND UND Campus connection.
 
Pinging ns1.Denver1.Level3.net [209.244.4.104] with 32 bytes of data:

Reply from 209.244.4.104: bytes=32 time=64ms TTL=244
Reply from 209.244.4.104: bytes=32 time=66ms TTL=244
Reply from 209.244.4.104: bytes=32 time=64ms TTL=244
Reply from 209.244.4.104: bytes=32 time=65ms TTL=244

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

NY,NY TWC RR Cable.
 
Pinging ns1.Denver1.Level3.net [209.244.4.104] with 32 bytes of data:

Reply from 209.244.4.104: bytes=32 time=80ms TTL=243
Reply from 209.244.4.104: bytes=32 time=84ms TTL=243
Reply from 209.244.4.104: bytes=32 time=56ms TTL=243
Reply from 209.244.4.104: bytes=32 time=71ms TTL=243

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

Columbia, MO, Mediacom
 
ping from my server:
root@server [~]# ping ns1.Denver1.Level3.net
PING ns1.Denver1.Level3.net (209.244.4.104) 56(84) bytes of data.
64 bytes from ns1.Denver1.Level3.net (209.244.4.104): icmp_seq=1 ttl=249 time=15.3 ms
64 bytes from ns1.Denver1.Level3.net (209.244.4.104): icmp_seq=2 ttl=249 time=15.4 ms
64 bytes from ns1.Denver1.Level3.net (209.244.4.104): icmp_seq=3 ttl=249 time=15.3 ms
64 bytes from ns1.Denver1.Level3.net (209.244.4.104): icmp_seq=4 ttl=249 time=15.8 ms
64 bytes from ns1.Denver1.Level3.net (209.244.4.104): icmp_seq=5 ttl=249 time=15.4 ms
64 bytes from ns1.Denver1.Level3.net (209.244.4.104): icmp_seq=6 ttl=249 time=15.4 ms
64 bytes from ns1.Denver1.Level3.net (209.244.4.104): icmp_seq=7 ttl=249 time=15.2 ms
64 bytes from ns1.Denver1.Level3.net (209.244.4.104): icmp_seq=8 ttl=249 time=15.1 ms
64 bytes from ns1.Denver1.Level3.net (209.244.4.104): icmp_seq=9 ttl=249 time=15.3 ms
64 bytes from ns1.Denver1.Level3.net (209.244.4.104): icmp_seq=10 ttl=249 time=15.1 ms
64 bytes from ns1.Denver1.Level3.net (209.244.4.104): icmp_seq=11 ttl=249 time=15.2 ms
64 bytes from ns1.Denver1.Level3.net (209.244.4.104): icmp_seq=12 ttl=249 time=15.0 ms
64 bytes from ns1.Denver1.Level3.net (209.244.4.104): icmp_seq=13 ttl=249 time=15.2 ms

--- ns1.Denver1.Level3.net ping statistics ---
13 packets transmitted, 13 received, 0% packet loss, time 12164ms
rtt min/avg/max/mdev = 15.050/15.328/15.877/0.263 ms
Click to expand...

ping from my computer:
Pinging ns1.Denver1.Level3.net [209.244.4.104] with 32 bytes of data:

Reply from 209.244.4.104: bytes=32 time=97ms TTL=242
Reply from 209.244.4.104: bytes=32 time=101ms TTL=242
Reply from 209.244.4.104: bytes=32 time=97ms TTL=242
Reply from 209.244.4.104: bytes=32 time=99ms TTL=242

Ping statistics for 209.244.4.104:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 97ms, Maximum = 101ms, Average = 98ms
Click to expand...
 
U:\>ping ns1.Denver1.Level3.net

Pinging ns1.Denver1.Level3.net [209.244.4.104] with 32 bytes of data:

Reply from 209.244.4.104: bytes=32 time=47ms TTL=241
Reply from 209.244.4.104: bytes=32 time=47ms TTL=241
Reply from 209.244.4.104: bytes=32 time=47ms TTL=241
Reply from 209.244.4.104: bytes=32 time=47ms TTL=241

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

U:\>

Lake charles LA 70601
Cox Communications
 
TextMicrosoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

C:\Documents and Settings\>ping ns1.Denver1.Level3.net a
Bad parameter a.

C:\Documents and Settings\>ping ns1.Denver1.Level3.net

Pinging ns1.Denver1.Level3.net [209.244.4.104] with 32 bytes of data:

Reply from 209.244.4.104: bytes=32 time=39ms TTL=243
Reply from 209.244.4.104: bytes=32 time=41ms TTL=243
Reply from 209.244.4.104: bytes=32 time=39ms TTL=243
Reply from 209.244.4.104: bytes=32 time=40ms TTL=243

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

C:\Documents and Settings\>
Click to expand...
Text
 
Originally posted by: CobraBubbles
hey cpal, where those machines located and what type of connections are they on?
Click to expand...

apparently someplace where you need root to run something like ping.



Reply from 209.244.4.104: bytes=32 time=87ms TTL=239
Reply from 209.244.4.104: bytes=32 time=97ms TTL=239
Reply from 209.244.4.104: bytes=32 time=71ms TTL=239
Reply from 209.244.4.104: bytes=32 time=90ms TTL=239
 
Reply from 209.244.4.104: bytes=32 time=53ms TTL=239
Reply from 209.244.4.104: bytes=32 time=53ms TTL=239
Reply from 209.244.4.104: bytes=32 time=53ms TTL=239
Reply from 209.244.4.104: bytes=32 time=54ms TTL=239

Conyers, GA
BellSouth DSL
 
Pinging ns1.denver1.level3.net [209.244.4.104] with 32 bytes of data:

Reply from 209.244.4.104: bytes=32 time=59ms TTL=246
Reply from 209.244.4.104: bytes=32 time=61ms TTL=246
Reply from 209.244.4.104: bytes=32 time=59ms TTL=246
Reply from 209.244.4.104: bytes=32 time=60ms TTL=246

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


greenville, sc ---> earthlink dsl
 
C:\>ping ns1.denver1.level3.net

Pinging ns1.denver1.level3.net [209.244.4.104] with 32 bytes of data:

Reply from 209.244.4.104: bytes=32 time=52ms TTL=245
Reply from 209.244.4.104: bytes=32 time=47ms TTL=245
Reply from 209.244.4.104: bytes=32 time=46ms TTL=245
Reply from 209.244.4.104: bytes=32 time=46ms TTL=245

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

Cox cable, Kansas.
 
Pinging ns1.Denver1.Level3.net [209.244.4.104] with 32 bytes of data:

Reply from 209.244.4.104: bytes=32 time=55ms TTL=242
Reply from 209.244.4.104: bytes=32 time=56ms TTL=242
Reply from 209.244.4.104: bytes=32 time=55ms TTL=242
Reply from 209.244.4.104: bytes=32 time=54ms TTL=242

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

Earthlink Cable (through Time Warner) Raleigh NC
 
Originally posted by: splice
overall pretty good results so far, except for cpals :| cPals, is your server in Florida?
Click to expand...

What do you mean?

My server had the best pings of all the ones posted here. Make sure you look at the "time".

CobraBubbles:
My server is located in Texas (ThePlanet) with 8 GigE connections. 😉
My personal computer is located in Florida... just on a 512/128 DSL line.
 
Originally posted by: Pepsi90919

apparently someplace where you need root to run something like ping.
Click to expand...

I was already logged into the server already and decided to help the guy out. Is that so wrong? I've used root for as long as I can remember and haven't had any problems. I know I should probably setup different user accounts, but I don't feel like it right now.

If the remark wasn't meant how I took it, then disregard the message above...
 

Pinging ns1.Denver1.Level3.net [209.244.4.104] with 32 bytes of data:
Reply from 209.244.4.104: bytes=32 time=67ms TTL=241
Reply from 209.244.4.104: bytes=32 time=35ms TTL=241
Reply from 209.244.4.104: bytes=32 time=36ms TTL=241
Reply from 209.244.4.104: bytes=32 time=46ms TTL=241

Ping statistics for 209.244.4.104:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:
Minimum = 35ms, Maximum = 67ms, Average = 46ms

Austin,TX RoadRunner
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top