Ping tests

NIM · December 31, 2007

Hi guys,

I need a favor from you all who'll read this topic. We have to test ping response times on two servers and I need your help on this.

So here's what you should do..

Open a command prompt (Start-->Run-->CMD+Enter)

Type ping 208.73.33.194, write down this info: Minimum = xx ms, Maximum = xx ms, Average = xx ms

Repeat the action for the second address

Type ping 74.52.38.226, write down this info: Minimum = xx ms, Maximum = xx ms, Average = xx ms

Check and paste your results here.

If anyone wants to know, we're testing the new server. This is the first step and better ping will not guarantee us faster access, it depends on the server hardware too. That's something will test out later on..

Thank you all.

Server 208.73.33.194

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

Server 74.52.38.226

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

ricktendo · December 31, 2007

208.73.33.194

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

74.52.38.226

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

LUZR4LIFE · December 31, 2007

TEST 1on 208.73.33.194

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

TEST 2 on 208.73.33.194

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

TEST 1 on 74.52.38.226

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

TEST 2 on 74.52.38.226

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

Edited December 31, 2007 by LUZR4LIFE

Tarun · December 31, 2007

From the OS:

208.73.33.194:

Pinging 208.73.33.194 with 32 bytes of data:

Reply from 208.73.33.194: bytes=32 time=17ms TTL=52
Reply from 208.73.33.194: bytes=32 time=20ms TTL=52
Reply from 208.73.33.194: bytes=32 time=18ms TTL=52
Reply from 208.73.33.194: bytes=32 time=17ms TTL=52

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

74.52.38.226:

Pinging 74.52.38.226 with 32 bytes of data:

Reply from 74.52.38.226: bytes=32 time=53ms TTL=45
Reply from 74.52.38.226: bytes=32 time=53ms TTL=45
Reply from 74.52.38.226: bytes=32 time=54ms TTL=45
Reply from 74.52.38.226: bytes=32 time=51ms TTL=45

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

-----

With Tomato firmware (from my WRT54GL router):

208.73.33.194:

Seq	Address					RX Bytes	TTL	RTT (ms)	+/- (ms)
0	208.73.33.194 (208.73.33.194)	64	53	24.60	
1	208.73.33.194 (208.73.33.194)	64	53	20.80	-3.80
2	208.73.33.194 (208.73.33.194)	64	53	18.90	-1.90
3	208.73.33.194 (208.73.33.194)	64	53	19.00	0.10
4	208.73.33.194 (208.73.33.194)	64	53	17.20	-1.80

Round-Trip: 17.2 min, 20.1 avg, 24.6 max (ms)
   Packets: 5 transmitted, 5 received, 0% lost

74.52.38.226:

Seq	Address	RX Bytes	TTL	RTT (ms)	+/- (ms)
0	74.52.38.226 (74.52.38.226)	64	46	51.30	
1	74.52.38.226 (74.52.38.226)	64	46	52.20	0.90
2	74.52.38.226 (74.52.38.226)	64	46	52.10	-0.10
3	74.52.38.226 (74.52.38.226)	64	46	51.50	-0.60
4	74.52.38.226 (74.52.38.226)	64	46	51.20	-0.30

Round-Trip: 51.2 min, 51.6 avg, 52.2 max (ms)
   Packets: 5 transmitted, 5 received, 0% lost

Edited December 31, 2007 by Tarun

cro-man · December 31, 2007

Test 1

Test 2

Test 3

Scrat · December 31, 2007

With Ping-Test-Easy

Host:
IP:   208.73.33.194  

Sent:   10
Received:   10
Lost:   0
Loss Rate:   0,00 %

Min Time:   20 ms
Max Time:   23 ms
Avg Time:   20 ms
Avg TTL:   55
--------------------------
Host:
IP:   74.52.38.226   

Sent:   10
Received:   10
Lost:   0
Loss Rate:   0,00 %

Min Time:   58 ms
Max Time:   59 ms
Avg Time:   58 ms
Avg TTL:   49

Sm0k3r · January 1, 2008

From PC

208.73.33.194

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

74.52.38.226

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

From Netgear DG834PN Wireless Router

208.73.33.194

PING 208.73.33.194 (208.73.33.194): 56 data bytes
64 bytes from 208.73.33.194: icmp_seq=0 ttl=52 time=100.0 ms
64 bytes from 208.73.33.194: icmp_seq=1 ttl=52 time=100.0 ms
64 bytes from 208.73.33.194: icmp_seq=2 ttl=52 time=105.0 ms
64 bytes from 208.73.33.194: icmp_seq=3 ttl=52 time=105.0 ms

--- 208.73.33.194 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 100.0/102.5/105.0 ms

74.52.38.226

PING 74.52.38.226 (74.52.38.226): 56 data bytes
64 bytes from 74.52.38.226: icmp_seq=0 ttl=46 time=140.0 ms
64 bytes from 74.52.38.226: icmp_seq=1 ttl=46 time=135.0 ms
64 bytes from 74.52.38.226: icmp_seq=2 ttl=46 time=135.0 ms
64 bytes from 74.52.38.226: icmp_seq=3 ttl=46 time=135.0 ms

--- 74.52.38.226 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 135.0/136.2/140.0 ms

NIM · January 1, 2008

Seems that the possible new server has better ping for all of us. Now, I should find out what hardware is on that machine.. :sweatingbullets:

PeaNut · January 6, 2008

Well, i hope i'm not too late with this, my measurements from Chello (UPC Broadband Cable Internet provider in Hungary):

Tested from Windows XP x64 SP2 ENU, with only MSN running in background, and cFosSpeed:

Pinging 208.73.33.194 with 32 bytes of data:

Reply from 208.73.33.194: bytes=32 time=115ms TTL=46

Reply from 208.73.33.194: bytes=32 time=117ms TTL=46

Reply from 208.73.33.194: bytes=32 time=116ms TTL=46

Reply from 208.73.33.194: bytes=32 time=129ms TTL=46

Reply from 208.73.33.194: bytes=32 time=134ms TTL=46

Reply from 208.73.33.194: bytes=32 time=135ms TTL=46

Reply from 208.73.33.194: bytes=32 time=117ms TTL=46

Reply from 208.73.33.194: bytes=32 time=130ms TTL=46

Reply from 208.73.33.194: bytes=32 time=128ms TTL=46

Reply from 208.73.33.194: bytes=32 time=127ms TTL=46

Ping statistics for 208.73.33.194:

Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 115ms, Maximum = 135ms, Average = 124ms

----

Pinging 74.52.38.226 with 32 bytes of data:

Reply from 74.52.38.226: bytes=32 time=144ms TTL=47

Reply from 74.52.38.226: bytes=32 time=157ms TTL=47

Reply from 74.52.38.226: bytes=32 time=172ms TTL=47

Reply from 74.52.38.226: bytes=32 time=144ms TTL=46

Reply from 74.52.38.226: bytes=32 time=141ms TTL=46

Reply from 74.52.38.226: bytes=32 time=143ms TTL=46

Reply from 74.52.38.226: bytes=32 time=145ms TTL=46

Reply from 74.52.38.226: bytes=32 time=147ms TTL=47

Reply from 74.52.38.226: bytes=32 time=145ms TTL=47

Reply from 74.52.38.226: bytes=32 time=147ms TTL=47

Ping statistics for 74.52.38.226:

Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 141ms, Maximum = 172ms, Average = 148ms

Edited January 6, 2008 by PeaNut

NIM · January 19, 2008

Well, it seems that the new server we're planning to move on has better ping. The question is now does it have good hardware as the one we're currently using has..

We're getting more and more visits daily and silver hosting package isn't sufficient for us now. We'll have to move for the gold package before we move on.

Sign In

Ping tests

Recommended Posts

NIM

ricktendo

LUZR4LIFE

Tarun

cro-man

Scrat

Sm0k3r

NIM

PeaNut

NIM

Join the conversation

Browse

Activity