Let's ping again!

[NIM]

Hi guys,

I need a favor from all of you who opened this topic. We'll 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 69.73.170.7, write down this info: Minimum = xx ms, Maximum = xx ms, Average = xx ms

Repeat the action for the second address

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

Check and paste your results here.

Please help us check the server latency in this way.

Thank you all.

Server 69.73.170.7

Ping statistics for 69.73.170.7:

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

Approximate round trip times in milli-seconds:

Minimum = 162ms, Maximum = 168ms, Average = 165ms

Server 209.172.60.147

Ping statistics for 209.172.60.147:

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

Approximate round trip times in milli-seconds:

Minimum = 170ms, Maximum = 173ms, Average = 171ms

[agli]

[Samkov]

69.73.170.7

min - 35

max - 38

average - 36

209.172.60.147

min - 40

max- 41

average - 40

[NIM]

@agli

Are you satisfied with the site overall speed? Did you notice any difference with this new host?

[agli]

@agli

Are you satisfied with the site overall speed? Did you notice any difference with this new host?

I have 768 kbit adsl and in the apartment powerline adapter on current network and directly to the router.

[NIM]

I have 768 kbit adsl and in the apartment powerline adapter on current network and directly to the router.

ok, but how are you satisfied with the site speed?

[agli]

Its ok.I am satisfied with the construction sites.

Edited August 28, 2008 by agli

[Mr.Thunderbird]

Ping statistics for 69.73.170.7:

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

Approximate round trip times in milli-seconds:

Minimum = 234ms, Maximum = 413ms, Average = 315ms

Ping statistics for 209.172.60.147:

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

Approximate round trip times in milli-seconds:

Minimum = 214ms, Maximum = 301ms, Average = 267ms

There ya go

Edited August 28, 2008 by Mr.Thunderbird

[Gorki]

Works fine and snappier for me

[Jonnyboy]

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

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

[NIM]

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

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

OMG, Jonnyboy, servers are probably next door to you

[Legolash2o]

69.73.170.7 Min:129ms Max: 136ms Average:132ms

209.172.60.147 Min:132ms Max: 170ms Average:143ms

Speed is great!

[Scrat]

[Guest]

N1K see this its not good? why

[ricktendo]

C:\Users\Ricardo>ping 69.73.170.7

Pinging 69.73.170.7 with 32 bytes of data:
Reply from 69.73.170.7: bytes=32 time=50ms TTL=57
Reply from 69.73.170.7: bytes=32 time=48ms TTL=57
Reply from 69.73.170.7: bytes=32 time=49ms TTL=57
Reply from 69.73.170.7: bytes=32 time=55ms TTL=57

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

C:\Users\Ricardo>ping 209.172.60.147

Pinging 209.172.60.147 with 32 bytes of data:
Reply from 209.172.60.147: bytes=32 time=84ms TTL=45
Reply from 209.172.60.147: bytes=32 time=75ms TTL=45
Reply from 209.172.60.147: bytes=32 time=80ms TTL=45
Reply from 209.172.60.147: bytes=32 time=82ms TTL=45

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

[NIM]

N1K see this its not good? why

Are you behind the proxy or maybe you have blocked ping command on the firewall. But don't worry, you wouldn't be able to access site if this is the reasl problem

[Sm0k3r]

N1K my results

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

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

[Sull]

Here is mine

[war59312]

Pretty good!

Ping statistics for 69.73.170.7:

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

Approximate round trip times in milli-seconds:

Minimum = 29ms, Maximum = 1200ms, Average = 75ms

Ping statistics for 209.172.60.147:

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

Approximate round trip times in milli-seconds:

Minimum = 46ms, Maximum = 277ms, Average = 90ms

No issues with speed at this time. Very quick.

Edited August 31, 2008 by war59312

[JurgenDoe]

[Jonnyboy]

OMG, Jonnyboy, servers are probably next door to you

I had to try several times before I got a non-negative number. I kept saying WTF, this can't be right!

Pinging 209.172.60.147 with 32 bytes of data:

Reply from 209.172.60.147: bytes=32 time=-91ms TTL=46
Reply from 209.172.60.147: bytes=32 time=-92ms TTL=46
Reply from 209.172.60.147: bytes=32 time=-83ms TTL=46
Reply from 209.172.60.147: bytes=32 time=-92ms TTL=46

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

Edited September 6, 2008 by Jonnyboy

[MrNxDmX]

Here's mine:

ping 209.172.60.147

209.172.60.147 yoklanıyor 32 bayt veri ile:

209.172.60.147 cevabı: bayt=32 s