Impressive ADSL performance!

M

MaD

Expert Member
Joined
Nov 5, 2003
Messages
4,929
Reaction score
16
I am truly impressed with Telkom.. only 35% packet loss to Germany.. not bad.

Code: 
Pinging www.hellkom.co.za [213.133.104.101] with 32 bytes of data:

Reply from 213.133.104.101: bytes=32 time=455ms TTL=236
Request timed out.
Request timed out.
Reply from 213.133.104.101: bytes=32 time=455ms TTL=236
Reply from 213.133.104.101: bytes=32 time=457ms TTL=236
Reply from 213.133.104.101: bytes=32 time=456ms TTL=236
Reply from 213.133.104.101: bytes=32 time=457ms TTL=236
Reply from 213.133.104.101: bytes=32 time=456ms TTL=236
Reply from 213.133.104.101: bytes=32 time=457ms TTL=236
Reply from 213.133.104.101: bytes=32 time=458ms TTL=236
Reply from 213.133.104.101: bytes=32 time=458ms TTL=236
Reply from 213.133.104.101: bytes=32 time=456ms TTL=236
Reply from 213.133.104.101: bytes=32 time=458ms TTL=236
Reply from 213.133.104.101: bytes=32 time=457ms TTL=236
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 213.133.104.101: bytes=32 time=457ms TTL=236
Reply from 213.133.104.101: bytes=32 time=458ms TTL=236
Reply from 213.133.104.101: bytes=32 time=458ms TTL=236
Reply from 213.133.104.101: bytes=32 time=457ms TTL=236
Reply from 213.133.104.101: bytes=32 time=456ms TTL=236
Reply from 213.133.104.101: bytes=32 time=457ms TTL=236
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 213.133.104.101: bytes=32 time=458ms TTL=236
Request timed out.
Reply from 213.133.104.101: bytes=32 time=456ms TTL=236
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 213.133.104.101: bytes=32 time=458ms TTL=236
Reply from 213.133.104.101: bytes=32 time=462ms TTL=236
Reply from 213.133.104.101: bytes=32 time=457ms TTL=236
Reply from 213.133.104.101: bytes=32 time=455ms TTL=236
Reply from 213.133.104.101: bytes=32 time=457ms TTL=236
Reply from 213.133.104.101: bytes=32 time=522ms TTL=236
Reply from 213.133.104.101: bytes=32 time=458ms TTL=236
Reply from 213.133.104.101: bytes=32 time=456ms TTL=236
Request timed out.
Reply from 213.133.104.101: bytes=32 time=456ms TTL=236
Request timed out.
Reply from 213.133.104.101: bytes=32 time=457ms TTL=236
Reply from 213.133.104.101: bytes=32 time=456ms TTL=236
Request timed out.
Reply from 213.133.104.101: bytes=32 time=463ms TTL=236
Reply from 213.133.104.101: bytes=32 time=457ms TTL=236
Reply from 213.133.104.101: bytes=32 time=455ms TTL=236
Reply from 213.133.104.101: bytes=32 time=456ms TTL=236
Reply from 213.133.104.101: bytes=32 time=456ms TTL=236
Reply from 213.133.104.101: bytes=32 time=459ms TTL=236
Reply from 213.133.104.101: bytes=32 time=458ms TTL=236
Reply from 213.133.104.101: bytes=32 time=456ms TTL=236
Reply from 213.133.104.101: bytes=32 time=456ms TTL=236
Reply from 213.133.104.101: bytes=32 time=456ms TTL=236
Reply from 213.133.104.101: bytes=32 time=456ms TTL=236
Request timed out.
Request timed out.
Request timed out.
Reply from 213.133.104.101: bytes=32 time=456ms TTL=236
Request timed out.
Reply from 213.133.104.101: bytes=32 time=457ms TTL=236

Ping statistics for 213.133.104.101:
    Packets: Sent = 68, Received = 44, Lost = 24 (35% loss),
Approximate round trip times in milli-seconds:
    Minimum = 455ms, Maximum = 522ms, Average = 458ms
Control-C
 
Pinging www.hellkom.co.za [213.133.104.101] with 32 bytes of data:

Reply from 213.133.104.101: bytes=32 time=455ms TTL=241
Reply from 213.133.104.101: bytes=32 time=450ms TTL=241
Reply from 213.133.104.101: bytes=32 time=456ms TTL=241
Reply from 213.133.104.101: bytes=32 time=462ms TTL=241
Reply from 213.133.104.101: bytes=32 time=470ms TTL=241
Reply from 213.133.104.101: bytes=32 time=471ms TTL=241
Reply from 213.133.104.101: bytes=32 time=480ms TTL=241
Reply from 213.133.104.101: bytes=32 time=470ms TTL=241
Reply from 213.133.104.101: bytes=32 time=472ms TTL=241
Reply from 213.133.104.101: bytes=32 time=458ms TTL=241
Reply from 213.133.104.101: bytes=32 time=490ms TTL=241
Reply from 213.133.104.101: bytes=32 time=476ms TTL=241
Reply from 213.133.104.101: bytes=32 time=468ms TTL=241
Reply from 213.133.104.101: bytes=32 time=481ms TTL=241
Reply from 213.133.104.101: bytes=32 time=471ms TTL=241
Reply from 213.133.104.101: bytes=32 time=476ms TTL=241
Reply from 213.133.104.101: bytes=32 time=462ms TTL=241
Reply from 213.133.104.101: bytes=32 time=483ms TTL=241
Reply from 213.133.104.101: bytes=32 time=491ms TTL=241
Reply from 213.133.104.101: bytes=32 time=502ms TTL=241
Reply from 213.133.104.101: bytes=32 time=525ms TTL=241
Reply from 213.133.104.101: bytes=32 time=527ms TTL=241
Reply from 213.133.104.101: bytes=32 time=532ms TTL=241
Reply from 213.133.104.101: bytes=32 time=518ms TTL=241
Reply from 213.133.104.101: bytes=32 time=519ms TTL=241
Reply from 213.133.104.101: bytes=32 time=523ms TTL=241
Reply from 213.133.104.101: bytes=32 time=517ms TTL=241
Reply from 213.133.104.101: bytes=32 time=498ms TTL=241
Reply from 213.133.104.101: bytes=32 time=503ms TTL=241
Reply from 213.133.104.101: bytes=32 time=499ms TTL=241
Reply from 213.133.104.101: bytes=32 time=488ms TTL=241
Reply from 213.133.104.101: bytes=32 time=488ms TTL=241
Reply from 213.133.104.101: bytes=32 time=493ms TTL=241
Reply from 213.133.104.101: bytes=32 time=488ms TTL=241
Reply from 213.133.104.101: bytes=32 time=492ms TTL=241
Reply from 213.133.104.101: bytes=32 time=566ms TTL=241
Reply from 213.133.104.101: bytes=32 time=496ms TTL=241
Reply from 213.133.104.101: bytes=32 time=492ms TTL=241
Reply from 213.133.104.101: bytes=32 time=503ms TTL=241
Reply from 213.133.104.101: bytes=32 time=488ms TTL=241
Reply from 213.133.104.101: bytes=32 time=507ms TTL=241
Reply from 213.133.104.101: bytes=32 time=517ms TTL=241
Reply from 213.133.104.101: bytes=32 time=539ms TTL=241
Reply from 213.133.104.101: bytes=32 time=522ms TTL=241
Reply from 213.133.104.101: bytes=32 time=525ms TTL=241
Reply from 213.133.104.101: bytes=32 time=514ms TTL=241
Reply from 213.133.104.101: bytes=32 time=518ms TTL=241
Reply from 213.133.104.101: bytes=32 time=521ms TTL=241
Reply from 213.133.104.101: bytes=32 time=523ms TTL=241
Reply from 213.133.104.101: bytes=32 time=580ms TTL=241

Ping statistics for 213.133.104.101:
Packets: Sent = 50, Received = 50, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 450ms, Maximum = 580ms, Average = 497ms
 
During the day its fine, but that happened at 12:46 AM.. probably some drunk dude falling around and couldn't get the network port into the hole :rolleyes:
 
Seems to happen every night and late at night too.

I have noticed it while playing WoW. All of a sudden I start getting packet loss andit usually between 11pm and 1am
 
bekdik said:
Probably running a backup.
Click to expand...

I usually check pings to various places to see how the network is performing at this time. There is between 5% and 35% packet loss (In case you're wondering.... no I'm not running a backup locally at the time)
 
Anybody got a good ping prog?

I need something that'll ping several destinations at the same time and have a history feature so that i can compare the packet loss/speed for a few weeks.

Pls pls pretty pls
 
armitage said:
Anybody got a good ping prog?

I need something that'll ping several destinations at the same time and have a history feature so that i can compare the packet loss/speed for a few weeks.

Pls pls pretty pls
Click to expand...
I've been lookin for something like that as well.. one solution I have found, albeit somewhat unrefined, is to type the following into the command prompt:

ping -t -l 1 -w 25000 www.domainnamehere.com > c:\filename.txt

Then the ping writes everything to a text file.. as I said, not the most eloquent example and surely won't win any prizes :) some people have recommend PingPlotter..
 
Gangrel said:
Seems to happen every night and late at night too.

I have noticed it while playing WoW. All of a sudden I start getting packet loss andit usually between 11pm and 1am
Click to expand...

Ive had numerous people complaining about performance between 11pm-1am, this is just to coincidental, which ESR do you connect to, in case you know?
 
Clipse said:
Ive had numerous people complaining about performance between 11pm-1am, this is just to coincidental, which ESR do you connect to, in case you know?
Click to expand...
Not sure, but I'm in Midrand if that helps any.
 
Interesting. I connect from Centurion and my 'downtime' is from 9pm-11pm. Maybe they using a 'Rolling bad service' scheme, like Escom is using in the Cape with their 'rolling blackouts'...
 
armitage said:
Anybody got a good ping prog?

I need something that'll ping several destinations at the same time and have a history feature so that i can compare the packet loss/speed for a few weeks.

Pls pls pretty pls
Click to expand...

*nix. ;)
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X