Huge packet-loss lately(pls read).

hmmm....Download wont go above 10KB/s....:mad: tried many sites with different downloads.....
 
----83.138.189.100 PING Statistics----
66 packets transmitted, 49 packets received, 25% packet loss
round-trip (ms) min/avg/max = 240/268/420

----196.4.160.2 PING Statistics----
66 packets transmitted, 66 packets received, 0% packet loss
round-trip (ms) min/avg/max = 50/86/390

----196.30.31.120 PING Statistics----
66 packets transmitted, 66 packets received, 0% packet loss
round-trip (ms) min/avg/max = 40/72/240

----216.239.38.10 PING Statistics----
66 packets transmitted, 57 packets received, 13% packet loss
round-trip (ms) min/avg/max = 320/341/490

Now, does the packet loss and the retries generated have an impact on metered bandwidth usage?

----83.138.189.100 PING Statistics----
66 packets transmitted, 66 packets received, 0% packet loss
round-trip (ms) min/avg/max = 240/268/380

----196.4.160.2 PING Statistics----
66 packets transmitted, 66 packets received, 0% packet loss
round-trip (ms) min/avg/max = 40/74/180

----196.30.31.120 PING Statistics----
66 packets transmitted, 66 packets received, 0% packet loss
round-trip (ms) min/avg/max = 40/77/200

----216.239.38.10 PING Statistics----
66 packets transmitted, 66 packets received, 0% packet loss
round-trip (ms) min/avg/max = 320/347/460

Getting back to where it should be...
 
Here it is with iburst @ home:

Pinging 216.239.38.10 with 32 bytes of data:

Reply from 216.239.38.10: bytes=32 time=414ms TTL=237
Reply from 216.239.38.10: bytes=32 time=374ms TTL=237
Reply from 216.239.38.10: bytes=32 time=359ms TTL=237
Reply from 216.239.38.10: bytes=32 time=343ms TTL=237
Reply from 216.239.38.10: bytes=32 time=343ms TTL=237
Reply from 216.239.38.10: bytes=32 time=359ms TTL=237
Reply from 216.239.38.10: bytes=32 time=359ms TTL=237
Reply from 216.239.38.10: bytes=32 time=343ms TTL=237
Reply from 216.239.38.10: bytes=32 time=328ms TTL=237
Reply from 216.239.38.10: bytes=32 time=421ms TTL=237
Reply from 216.239.38.10: bytes=32 time=359ms TTL=237
Reply from 216.239.38.10: bytes=32 time=343ms TTL=237
Reply from 216.239.38.10: bytes=32 time=375ms TTL=237
Reply from 216.239.38.10: bytes=32 time=359ms TTL=237
Reply from 216.239.38.10: bytes=32 time=359ms TTL=237
Reply from 216.239.38.10: bytes=32 time=343ms TTL=237
Reply from 216.239.38.10: bytes=32 time=359ms TTL=237
Reply from 216.239.38.10: bytes=32 time=343ms TTL=237
Reply from 216.239.38.10: bytes=32 time=359ms TTL=237
Reply from 216.239.38.10: bytes=32 time=328ms TTL=237
Reply from 216.239.38.10: bytes=32 time=359ms TTL=237
Reply from 216.239.38.10: bytes=32 time=374ms TTL=237
Reply from 216.239.38.10: bytes=32 time=343ms TTL=237
Reply from 216.239.38.10: bytes=32 time=375ms TTL=237
Reply from 216.239.38.10: bytes=32 time=390ms TTL=237
Reply from 216.239.38.10: bytes=32 time=343ms TTL=237
Reply from 216.239.38.10: bytes=32 time=468ms TTL=237
Reply from 216.239.38.10: bytes=32 time=375ms TTL=237
Reply from 216.239.38.10: bytes=32 time=500ms TTL=237
Reply from 216.239.38.10: bytes=32 time=343ms TTL=237

Ping statistics for 216.239.38.10:
Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 328ms, Maximum = 500ms, Average = 368ms
 
Ping statistics for 216.239.38.10:
Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 326ms, Maximum = 464ms, Average = 361ms


Looks like there is an improvement indeed! :D
 
Contacted Gamco...

Anybody else find your results get better the more times you do the test? Surely it shouldn't be caching the data your benchmarking?

From: GamCo (Pty) Ltd - - Support [mailto:[email protected]]
Sent: 09 February 2007 09:10 AM
To: michael
Subject: [GamCo Support #RMD-592925]: Bandwidth meter delivering incorrect results....

Hi Michael

Thanks for you mail!

I believe the bandwidth meter is accurate but you can test your speeds at the following link, to see if they give the same info:

http://speedtest-rba.isdsl.net/


Kind Regards
Paulus


Ticket Details Ticket ID: RMD-592925
Department: Support - PW
Priority: Low
Status: Closed

If not try... http://www.interexcel-iburst.co.za/speed_test.asp
 
Lol, I also found that test increases with refreshes. Maybe its just somthing to account for. Then again, speedtest.net doesn't go up the more times I do the test, it goes down actually.
 
It's Monday packet loss has returned...

Anyone else?


Ping statistics for 196.7.147.165:
Packets: Sent = 240, Received = 236, Lost = 4 (1% loss),
Approximate round trip times in milli-seconds:
Minimum = 42ms, Maximum = 275ms, Average = 82ms

Ping statistics for 196.30.31.120:
Packets: Sent = 24, Received = 23, Lost = 1 (4% loss),
Approximate round trip times in milli-seconds:
Minimum = 63ms, Maximum = 178ms, Average = 104ms

Ping statistics for 196.35.70.120:
Packets: Sent = 31, Received = 29, Lost = 2 (6% loss),
Approximate round trip times in milli-seconds:
Minimum = 213ms, Maximum = 305ms, Average = 240ms

Ping statistics for 64.233.161.104:
Packets: Sent = 11, Received = 10, Lost = 1 (9% loss),
Approximate round trip times in milli-seconds:
Minimum = 523ms, Maximum = 626ms, Average = 557ms

Ping statistics for 196.35.164.204:
Packets: Sent = 11, Received = 8, Lost = 3 (27% loss),
Approximate round trip times in milli-seconds:
Minimum = 232ms, Maximum = 262ms, Average = 244ms
 
Could only respond now as I just walked in:

Pinging 196.7.147.165 with 1 bytes of data:

Reply from 196.7.147.165: bytes=1 time=66ms TTL=247
Reply from 196.7.147.165: bytes=1 time=65ms TTL=247
Reply from 196.7.147.165: bytes=1 time=59ms TTL=247
Reply from 196.7.147.165: bytes=1 time=63ms TTL=247
Reply from 196.7.147.165: bytes=1 time=82ms TTL=247
Reply from 196.7.147.165: bytes=1 time=160ms TTL=247
Reply from 196.7.147.165: bytes=1 time=85ms TTL=247
Reply from 196.7.147.165: bytes=1 time=69ms TTL=247
Reply from 196.7.147.165: bytes=1 time=58ms TTL=247
Reply from 196.7.147.165: bytes=1 time=72ms TTL=247

Ping statistics for 196.7.147.165:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 58ms, Maximum = 160ms, Average = 77ms
 
Michael I will try that during the morning around the same time you did and see what happens.
 
I did actually try a few pings around the time that was posted, and mine didn't seem to have any loss. Out of 10 pings to MyADSL, and there were spikes, but no timeouts..

I'll check again properly tomorrow morning..
 
9:05am test

Pinging 196.7.147.165 with 32 bytes of data:

Reply from 196.7.147.165: bytes=32 time=72ms TTL=247
Reply from 196.7.147.165: bytes=32 time=61ms TTL=247
Reply from 196.7.147.165: bytes=32 time=60ms TTL=247
Reply from 196.7.147.165: bytes=32 time=59ms TTL=247
Reply from 196.7.147.165: bytes=32 time=73ms TTL=247
Reply from 196.7.147.165: bytes=32 time=57ms TTL=247
Reply from 196.7.147.165: bytes=32 time=61ms TTL=247
Reply from 196.7.147.165: bytes=32 time=70ms TTL=247
Reply from 196.7.147.165: bytes=32 time=58ms TTL=247
Reply from 196.7.147.165: bytes=32 time=67ms TTL=247
Reply from 196.7.147.165: bytes=32 time=62ms TTL=247
Reply from 196.7.147.165: bytes=32 time=66ms TTL=247

Ping statistics for 196.7.147.165:
Packets: Sent = 12, Received = 12, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 57ms, Maximum = 73ms, Average = 63ms

EDIT: I'll gather some more ping tests over the next few hours and post the whole lot later today.

10:02am test

Pinging 196.7.147.165 with 32 bytes of data:

Reply from 196.7.147.165: bytes=32 time=60ms TTL=247
Reply from 196.7.147.165: bytes=32 time=58ms TTL=247
Reply from 196.7.147.165: bytes=32 time=63ms TTL=247
Reply from 196.7.147.165: bytes=32 time=58ms TTL=247
Reply from 196.7.147.165: bytes=32 time=64ms TTL=247
Reply from 196.7.147.165: bytes=32 time=64ms TTL=247
Reply from 196.7.147.165: bytes=32 time=60ms TTL=247
Reply from 196.7.147.165: bytes=32 time=64ms TTL=247
Reply from 196.7.147.165: bytes=32 time=65ms TTL=247
Reply from 196.7.147.165: bytes=32 time=60ms TTL=247
Reply from 196.7.147.165: bytes=32 time=65ms TTL=247
Reply from 196.7.147.165: bytes=32 time=65ms TTL=247

Ping statistics for 196.7.147.165:
Packets: Sent = 12, Received = 12, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 58ms, Maximum = 65ms, Average = 62ms
 
Last edited:
Your tower / connection does seem better...

Tx MrH

12:42 13/02/07

Ping statistics for 196.7.147.165:
Packets: Sent = 48, Received = 48, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 51ms, Maximum = 175ms, Average = 81ms

No loss today... Will check later, give me a time when you check so I can check from my side at the same time...
 
Adsl

are you sure it's iBurst? I'll be willing to bet if you tried the same thing on an ADSL line during office hours you'd also get a similar packet loss.

Ping statistics for 196.7.147.165:
Packets: Sent = 100, Received = 100, Lost = 0 (0% packet loss)
Approximate round trip times in milliseconds:
Minimum = 39ms, Maximum = 70ms, Average = 42ms

Packet loss? You'd lose your bet.
 
Here are the ping tests for today:

-------------------------------
11:04am

Pinging 196.7.147.165 with 1 bytes of data:

Reply from 196.7.147.165: bytes=1 time=65ms TTL=247
Reply from 196.7.147.165: bytes=1 time=62ms TTL=247
Reply from 196.7.147.165: bytes=1 time=63ms TTL=247
Reply from 196.7.147.165: bytes=1 time=68ms TTL=247
Reply from 196.7.147.165: bytes=1 time=63ms TTL=247
Reply from 196.7.147.165: bytes=1 time=58ms TTL=247
Reply from 196.7.147.165: bytes=1 time=64ms TTL=247
Reply from 196.7.147.165: bytes=1 time=59ms TTL=247
Reply from 196.7.147.165: bytes=1 time=159ms TTL=247
Reply from 196.7.147.165: bytes=1 time=60ms TTL=247
Reply from 196.7.147.165: bytes=1 time=65ms TTL=247
Reply from 196.7.147.165: bytes=1 time=75ms TTL=247

Ping statistics for 196.7.147.165:
Packets: Sent = 12, Received = 12, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 58ms, Maximum = 159ms, Average = 71ms
--------------------------
12:08

Pinging 196.7.147.165 with 1 bytes of data:

Reply from 196.7.147.165: bytes=1 time=65ms TTL=247
Reply from 196.7.147.165: bytes=1 time=158ms TTL=247
Reply from 196.7.147.165: bytes=1 time=63ms TTL=247
Reply from 196.7.147.165: bytes=1 time=73ms TTL=247
Reply from 196.7.147.165: bytes=1 time=69ms TTL=247
Reply from 196.7.147.165: bytes=1 time=61ms TTL=247
Reply from 196.7.147.165: bytes=1 time=76ms TTL=247
Reply from 196.7.147.165: bytes=1 time=65ms TTL=247
Reply from 196.7.147.165: bytes=1 time=65ms TTL=247
Reply from 196.7.147.165: bytes=1 time=65ms TTL=247
Reply from 196.7.147.165: bytes=1 time=61ms TTL=247
Reply from 196.7.147.165: bytes=1 time=60ms TTL=247

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

13:05

Pinging 196.7.147.165 with 1 bytes of data:

Reply from 196.7.147.165: bytes=1 time=160ms TTL=247
Reply from 196.7.147.165: bytes=1 time=83ms TTL=247
Reply from 196.7.147.165: bytes=1 time=78ms TTL=247
Reply from 196.7.147.165: bytes=1 time=64ms TTL=247
Reply from 196.7.147.165: bytes=1 time=59ms TTL=247
Reply from 196.7.147.165: bytes=1 time=63ms TTL=247
Reply from 196.7.147.165: bytes=1 time=59ms TTL=247
Reply from 196.7.147.165: bytes=1 time=59ms TTL=247
Reply from 196.7.147.165: bytes=1 time=64ms TTL=247
Reply from 196.7.147.165: bytes=1 time=64ms TTL=247
Reply from 196.7.147.165: bytes=1 time=104ms TTL=247
Reply from 196.7.147.165: bytes=1 time=59ms TTL=247

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

14:10

Pinging 196.7.147.165 with 32 bytes of data:

Reply from 196.7.147.165: bytes=32 time=61ms TTL=247
Reply from 196.7.147.165: bytes=32 time=64ms TTL=247
Reply from 196.7.147.165: bytes=32 time=59ms TTL=247
Reply from 196.7.147.165: bytes=32 time=64ms TTL=247
Reply from 196.7.147.165: bytes=32 time=64ms TTL=247
Reply from 196.7.147.165: bytes=32 time=59ms TTL=247
Reply from 196.7.147.165: bytes=32 time=70ms TTL=247
Reply from 196.7.147.165: bytes=32 time=176ms TTL=247
Reply from 196.7.147.165: bytes=32 time=65ms TTL=247
Reply from 196.7.147.165: bytes=32 time=57ms TTL=247
Reply from 196.7.147.165: bytes=32 time=57ms TTL=247
Reply from 196.7.147.165: bytes=32 time=62ms TTL=247

Ping statistics for 196.7.147.165:
Packets: Sent = 12, Received = 12, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 57ms, Maximum = 176ms, Average = 71ms
-------------------------

15:07

Pinging 196.7.147.165 with 32 bytes of data:

Reply from 196.7.147.165: bytes=32 time=64ms TTL=247
Reply from 196.7.147.165: bytes=32 time=58ms TTL=247
Reply from 196.7.147.165: bytes=32 time=64ms TTL=247
Reply from 196.7.147.165: bytes=32 time=59ms TTL=247
Reply from 196.7.147.165: bytes=32 time=59ms TTL=247
Reply from 196.7.147.165: bytes=32 time=64ms TTL=247
Reply from 196.7.147.165: bytes=32 time=64ms TTL=247
Reply from 196.7.147.165: bytes=32 time=79ms TTL=247
Reply from 196.7.147.165: bytes=32 time=64ms TTL=247
Reply from 196.7.147.165: bytes=32 time=59ms TTL=247
Reply from 196.7.147.165: bytes=32 time=64ms TTL=247
Reply from 196.7.147.165: bytes=32 time=59ms TTL=247

Ping statistics for 196.7.147.165:
Packets: Sent = 12, Received = 12, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 58ms, Maximum = 79ms, Average = 63ms
---------------------------------------

16:04

Pinging 196.7.147.165 with 32 bytes of data:

Reply from 196.7.147.165: bytes=32 time=62ms TTL=247
Reply from 196.7.147.165: bytes=32 time=60ms TTL=247
Reply from 196.7.147.165: bytes=32 time=69ms TTL=247
Reply from 196.7.147.165: bytes=32 time=65ms TTL=247
Reply from 196.7.147.165: bytes=32 time=57ms TTL=247
Reply from 196.7.147.165: bytes=32 time=82ms TTL=247
Reply from 196.7.147.165: bytes=32 time=59ms TTL=247
Reply from 196.7.147.165: bytes=32 time=58ms TTL=247
Reply from 196.7.147.165: bytes=32 time=60ms TTL=247
Reply from 196.7.147.165: bytes=32 time=84ms TTL=247
Reply from 196.7.147.165: bytes=32 time=64ms TTL=247
Reply from 196.7.147.165: bytes=32 time=64ms TTL=247

Ping statistics for 196.7.147.165:
Packets: Sent = 12, Received = 12, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 57ms, Maximum = 84ms, Average = 65ms
--------------------------------------

17:01

Pinging 196.7.147.165 with 1 bytes of data:

Reply from 196.7.147.165: bytes=1 time=63ms TTL=247
Reply from 196.7.147.165: bytes=1 time=58ms TTL=247
Reply from 196.7.147.165: bytes=1 time=59ms TTL=247
Reply from 196.7.147.165: bytes=1 time=59ms TTL=247
Reply from 196.7.147.165: bytes=1 time=59ms TTL=247
Reply from 196.7.147.165: bytes=1 time=59ms TTL=247
Reply from 196.7.147.165: bytes=1 time=64ms TTL=247
Reply from 196.7.147.165: bytes=1 time=60ms TTL=247
Reply from 196.7.147.165: bytes=1 time=64ms TTL=247
Reply from 196.7.147.165: bytes=1 time=64ms TTL=247
Reply from 196.7.147.165: bytes=1 time=64ms TTL=247
Reply from 196.7.147.165: bytes=1 time=64ms TTL=247
Reply from 196.7.147.165: bytes=1 time=59ms TTL=247
Reply from 196.7.147.165: bytes=1 time=64ms TTL=247

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

--------------------------------

No real difference thats worth worrying about as far as I can see.
 
Hi All

I have had some reports where packet loss is still a problem. I have the technical guys on this again to make sure everthing is OK. In the meantime, if there are others out there having high packet loss problems, please post your readings here and I can then feed this back to the technical team.

Thanks all
Ed
 
Top
Sign up to the MyBroadband newsletter
X