.: ShaolinTiger - Kung-Fu Geekery :.

Seems like some people don't know what a Ping is, which is fair enough really..

Some know what it is, sort of, but don't know how to intepret the results.

So here's a quick run-down.

Good Ping

Here's what my work ping to google.com looks like now:

As you can see, it's pretty constant around the 300ms mark, with no "Request timed out".

Bad Ping

When I was in Brunei and people were using Peer to Peer software in the hotel, my connection looked like this:

As you can see there are many "Request timed out" and high ping times.

Ok so how do I interpret this?

As you can see in the first either picture there are multiple similar lines in the format:

Reply from 64.233.187.99: bytes=32 time=300ms TTL=241

Reply from THE SERVER YOU PINGED bytes=SIZE OF PING time=PING TIME TTL=IGNORE

A ping is basically a packet containing a bunch of junk (1-10 and a-z) or something like that, a packet is just a small peice of data sent over the Internet.

When another machine receives your ping packet, it will send back a reply, the purpose of the ping is to time this whole process.

That's the time= part shown above, the time taken for the packet you sent to get a reply.

So it's a basic metric for the quality of service your Internet connection is giving you.

Request Timed Out

If you see the "Request timed out" shown in the Bad Ping section above, it means you got no reply at all, which is called a dropped packet. This is bad, and means there is a failure somewhere, and either your packet isn't reaching the destination, or you aren't getting a reply.

Ping Times

500ms = 1/5 second (1000ms = 1 second).

• A normal time for streamyx would be 250-300ms
• At peak times it seems to be around 500-600ms
• When it's really bad its 800-1200ms
• If it's above 1000ms trying restarting your connection

Ok, so how do I Ping?

Ok to ping something, go to the Start - Run menu option and type cmd:

Then press enter, you'll see a DOS prompt come up.

In the prompt type:

ping google.com -t

And press enter.

You'll see the ping running, the -t argument tells it to ping constantly, so it won't stop untill you press CTRL+C.

It'll then give you a summary of the Ping statistics for that session.

You can also try pinging yahoo.com, I usually get slightly better times for Yahoo! than Google.

If you ping streamyx.com you should get something like 20-50ms.

If you want to read more about Ping and some of the options, check Wikepedia - Ping.

Still the lack of quality of service surprises me with Streamyx. I think I'll just call it Streamyx Shitband.

They still keep selling it, still keep advertising it, still keep pushing it...but their infrastructure can't even support the current userbase.

At peak times it goes to shit, if I want decent latency (decent in terms of Streamyx btw, not decent generally) I have to surf at 3am.

The rest of the time, I am paying for this:

It's partially to do with their new capping method, they don't cap any more, they use bandwidth shaping..

And the lines aren't high enough quality to actually support 3MB, so the Signal Noise Ratio is horrendous..

So I get horrible quality of service, especially at peak times.

I want my 330ms ping back, even if that is pretty lousy, at work I get 250ms, UK I got 60ms..

I'm spoilt I guess.

It seems like since they introducted the new capping method, I have to reset the connection every few hours aswell or it turns to complete shit.

It wasn't like that before, I remember when it used to be decent-ish, when everyone had 512k, it really was 512k pretty much...now everyone has 1mb, everyone has about 250k ARGH.