Huge packet-loss lately(pls read).

M

markos

Member
Joined
Feb 2, 2007
Messages
16
Reaction score
0
Hi all, ive been having huge packet-loss lately and so have 2 friends with iburst also. When i called helpdesk i asked them to test their connection - guess what, helpdesk also had packetloss as they use the iburst network(not wireless just the network). So please can anyone using iburst (also if u have a telkom line post the comparison results pls) of the ping command below (the ip is google.com). I will post my results as soon as i get back home from work. Also please post your location i wanna see if the problem is isolated to specific areas or the iburst network as a whole. Running this i had about 20% packetloss and so did the iburst helpdesk person and 2 other ppl i know with iburst, while on the modem and telkom line we all had 0% packetloss. Seems like one of thir routers is faulty or needs replacing, pls help me proove or diagnose it so we can have our lines back to normal ASAP.
Thanx all...

ping 216.239.38.10 -n30
 
Ping statistics for 216.239.38.10:
Packets: Sent = 30, Received = 24, Lost = 6 (20% l
Approximate round trip times in milli-seconds:
Minimum = 317ms, Maximum = 369ms, Average = 342ms
 
Just another ip for comparison.

Ping statistics for 216.239.59.99
Packets: Sent = 30, Received = 15, Lost = 15 (50% loss),
Approximate round trip times in milli-seconds:
Minimum = 263ms, Maximum = 284ms, Average = 271ms
 
Nothing new...

Pinging 216.239.38.10 with 32 bytes of data:

Reply from 216.239.38.10: bytes=32 time=545ms TTL=239
Request timed out.
Reply from 216.239.38.10: bytes=32 time=510ms TTL=239
Request timed out.

Ping statistics for 216.239.38.10:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
Minimum = 510ms, Maximum = 545ms, Average = 527ms


C:\>ping 208.67.222.222 -t -l 1

Pinging 208.67.222.222 with 1 bytes of data:

Reply from 208.67.222.222: bytes=1 time=648ms TTL=51
Reply from 208.67.222.222: bytes=1 time=506ms TTL=51
Reply from 208.67.222.222: bytes=1 time=502ms TTL=51
Reply from 208.67.222.222: bytes=1 time=600ms TTL=51
Reply from 208.67.222.222: bytes=1 time=508ms TTL=51
Reply from 208.67.222.222: bytes=1 time=561ms TTL=51
Reply from 208.67.222.222: bytes=1 time=524ms TTL=51
Request timed out.
Reply from 208.67.222.222: bytes=1 time=520ms TTL=51
Reply from 208.67.222.222: bytes=1 time=512ms TTL=51

Ping statistics for 208.67.222.222:
Packets: Sent = 21, Received = 20, Lost = 1 (4% loss),
Approximate round trip times in milli-seconds:
Minimum = 502ms, Maximum = 664ms, Average = 545ms
 
I have been complaining about the packet loss for several days now:

216.239.38.10
216.239.38.10
Location:United States
Packets Sent:32
Packets Received:18
Packets Lost:14(43% loss)
Response time Minimum:338ms
Response time Maximum:845ms
Response time Average:271ms
 
EVERYONE has been having crap performance on iBurst for a about a week now.

I'm really surprised a thread wasn't started about it sooner, and disappointed a resolution still hasn't been reached.

25% loss on my end :/
 
I have the same problem. Local is fine but Intl sucks. Here are my stats for google.com.....

Ping statistics for 64.233.183.104:
Packets: Sent = 10, Received = 6, Lost = 4 (40% loss),
Approximate round trip times in milli-seconds:
Minimum = 268ms, Maximum = 358ms, Average = 297ms
 
C:\>ping 216.239.38.10 -n 30

Pinging 216.239.38.10 with 32 bytes of data:

Request timed out.
Reply from 216.239.38.10: bytes=32 time=550ms TTL=238
Reply from 216.239.38.10: bytes=32 time=540ms TTL=238
Request timed out.
Reply from 216.239.38.10: bytes=32 time=480ms TTL=238
Reply from 216.239.38.10: bytes=32 time=350ms TTL=238
Reply from 216.239.38.10: bytes=32 time=640ms TTL=238
Reply from 216.239.38.10: bytes=32 time=450ms TTL=238
Reply from 216.239.38.10: bytes=32 time=440ms TTL=238
Reply from 216.239.38.10: bytes=32 time=650ms TTL=238
Reply from 216.239.38.10: bytes=32 time=460ms TTL=238
Reply from 216.239.38.10: bytes=32 time=480ms TTL=238
Reply from 216.239.38.10: bytes=32 time=380ms TTL=238
Reply from 216.239.38.10: bytes=32 time=570ms TTL=238
Reply from 216.239.38.10: bytes=32 time=470ms TTL=238
Reply from 216.239.38.10: bytes=32 time=450ms TTL=238
Reply from 216.239.38.10: bytes=32 time=410ms TTL=238
Request timed out.
Request timed out.
Reply from 216.239.38.10: bytes=32 time=429ms TTL=238
Reply from 216.239.38.10: bytes=32 time=450ms TTL=238
Reply from 216.239.38.10: bytes=32 time=390ms TTL=238
Reply from 216.239.38.10: bytes=32 time=480ms TTL=238
Reply from 216.239.38.10: bytes=32 time=350ms TTL=238
Reply from 216.239.38.10: bytes=32 time=460ms TTL=238
Reply from 216.239.38.10: bytes=32 time=450ms TTL=238
Reply from 216.239.38.10: bytes=32 time=417ms TTL=238
Reply from 216.239.38.10: bytes=32 time=390ms TTL=238
Reply from 216.239.38.10: bytes=32 time=689ms TTL=238
Reply from 216.239.38.10: bytes=32 time=480ms TTL=238

Ping statistics for 216.239.38.10:
Packets: Sent = 30, Received = 26, Lost = 4 (13% loss),
Approximate round trip times in milli-seconds:
Minimum = 350ms, Maximum = 689ms, Average = 473ms

C:\>ping 216.239.38.10 -n 30

Pinging 216.239.38.10 with 32 bytes of data:

Request timed out.
Reply from 216.239.38.10: bytes=32 time=941ms TTL=238
Reply from 216.239.38.10: bytes=32 time=390ms TTL=238
Request timed out.
Reply from 216.239.38.10: bytes=32 time=590ms TTL=238
Reply from 216.239.38.10: bytes=32 time=370ms TTL=238
Reply from 216.239.38.10: bytes=32 time=380ms TTL=238
Reply from 216.239.38.10: bytes=32 time=340ms TTL=238
Reply from 216.239.38.10: bytes=32 time=590ms TTL=238
Reply from 216.239.38.10: bytes=32 time=650ms TTL=238
Reply from 216.239.38.10: bytes=32 time=350ms TTL=238
Reply from 216.239.38.10: bytes=32 time=340ms TTL=238
Reply from 216.239.38.10: bytes=32 time=360ms TTL=238
Reply from 216.239.38.10: bytes=32 time=570ms TTL=238
Reply from 216.239.38.10: bytes=32 time=570ms TTL=238
Reply from 216.239.38.10: bytes=32 time=410ms TTL=238
Reply from 216.239.38.10: bytes=32 time=370ms TTL=238
Reply from 216.239.38.10: bytes=32 time=380ms TTL=238
Reply from 216.239.38.10: bytes=32 time=460ms TTL=238
Reply from 216.239.38.10: bytes=32 time=400ms TTL=238
Reply from 216.239.38.10: bytes=32 time=380ms TTL=238
Reply from 216.239.38.10: bytes=32 time=530ms TTL=238
Reply from 216.239.38.10: bytes=32 time=650ms TTL=238
Reply from 216.239.38.10: bytes=32 time=430ms TTL=238
Reply from 216.239.38.10: bytes=32 time=370ms TTL=238
Reply from 216.239.38.10: bytes=32 time=470ms TTL=238
Reply from 216.239.38.10: bytes=32 time=350ms TTL=238
Reply from 216.239.38.10: bytes=32 time=440ms TTL=238
Reply from 216.239.38.10: bytes=32 time=510ms TTL=238
Reply from 216.239.38.10: bytes=32 time=350ms TTL=238

Ping statistics for 216.239.38.10:
Packets: Sent = 30, Received = 28, Lost = 2 (6% loss),
Approximate round trip times in milli-seconds:
Minimum = 340ms, Maximum = 941ms, Average = 462ms
Ran it twice and got this.
Location: Randburg
 
I don't have any loss, but those stupid international pings in the 300-400 range for people in Joburg is still irritating.

Pinging google.com [72.14.207.99] with 32 bytes of data:

Reply from 72.14.207.99: bytes=32 time=569ms TTL=240
Reply from 72.14.207.99: bytes=32 time=564ms TTL=240
Reply from 72.14.207.99: bytes=32 time=560ms TTL=240
Reply from 72.14.207.99: bytes=32 time=559ms TTL=240
Reply from 72.14.207.99: bytes=32 time=575ms TTL=240
Reply from 72.14.207.99: bytes=32 time=584ms TTL=240
Reply from 72.14.207.99: bytes=32 time=594ms TTL=240
Reply from 72.14.207.99: bytes=32 time=564ms TTL=240
Reply from 72.14.207.99: bytes=32 time=564ms TTL=240
Reply from 72.14.207.99: bytes=32 time=579ms TTL=240
Reply from 72.14.207.99: bytes=32 time=579ms TTL=240
Reply from 72.14.207.99: bytes=32 time=549ms TTL=240
Reply from 72.14.207.99: bytes=32 time=564ms TTL=240
Reply from 72.14.207.99: bytes=32 time=570ms TTL=240
Reply from 72.14.207.99: bytes=32 time=574ms TTL=240
Reply from 72.14.207.99: bytes=32 time=585ms TTL=240
Reply from 72.14.207.99: bytes=32 time=579ms TTL=240
Reply from 72.14.207.99: bytes=32 time=569ms TTL=240
Reply from 72.14.207.99: bytes=32 time=565ms TTL=240
Reply from 72.14.207.99: bytes=32 time=554ms TTL=240
Reply from 72.14.207.99: bytes=32 time=579ms TTL=240
Reply from 72.14.207.99: bytes=32 time=544ms TTL=240
Reply from 72.14.207.99: bytes=32 time=549ms TTL=240
Reply from 72.14.207.99: bytes=32 time=569ms TTL=240
Reply from 72.14.207.99: bytes=32 time=564ms TTL=240
Reply from 72.14.207.99: bytes=32 time=564ms TTL=240
Reply from 72.14.207.99: bytes=32 time=574ms TTL=240
Reply from 72.14.207.99: bytes=32 time=575ms TTL=240
Reply from 72.14.207.99: bytes=32 time=550ms TTL=240
Reply from 72.14.207.99: bytes=32 time=554ms TTL=240

Ping statistics for 72.14.207.99:
Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 544ms, Maximum = 594ms, Average = 567ms
 
My usual package of pings:

----83.138.189.100 PING Statistics----
66 packets transmitted, 54 packets received, 18% packet loss
round-trip (ms) min/avg/max = 220/272/390

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

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

Special request:

----216.239.38.10 PING Statistics----
30 packets transmitted, 25 packets received, 16% packet loss
round-trip (ms) min/avg/max = 320/351/470

Yup, looks like an international issue.
 
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 = 359ms, Average = 337ms

Ran this several times, no packet loss. Pretoria
 
This is great now we getting somewhere, i have sent a long email to iburst about the problem and included all the details i could collect. What would be great is if more ppl(everyone who reads this) could post their results here so if by monday the probem is still there i can try get hold of iburst management or even go into their offices and show them this thread. As i said it would really help if i had 50+ post here with packet loss because then we really cant be ignored.
But great job, lets take some action about this problem as we're not getting the service we are paying for.
Tnx all.
 
Using the same ip's as before this is at 11:55 03/02/2007

Ping statistics for 83.138.189.100:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
Minimum = 336ms, Maximum = 350ms, Average = 343ms

Ping statistics for 216.239.38.10:
Packets: Sent = 30, Received = 23, Lost = 7 (23% loss),
Approximate round trip times in milli-seconds:
Minimum = 310ms, Maximum = 564ms, Average = 369ms

Ping statistics for 72.14.207.99:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 344ms, Maximum = 400ms, Average = 372ms
 
At 1400

Ping statistics for 216.239.38.10:
Packets: Sent = 30, Received = 24, Lost = 6 (20% loss),
Approximate round trip times in milli-seconds:
Minimum = 406ms, Maximum = 484ms, Average = 429ms

Personally, I think this has got bôggerôl to do with iburst. It's the connection out of the country that can't take the punch.
 
Pinging 216.239.38.10 with 32 bytes of data:

Reply from 216.239.38.10: bytes=32 time=346ms TTL=237
Reply from 216.239.38.10: bytes=32 time=431ms TTL=237
Reply from 216.239.38.10: bytes=32 time=321ms TTL=237
Reply from 216.239.38.10: bytes=32 time=320ms TTL=237
Reply from 216.239.38.10: bytes=32 time=334ms TTL=237
Reply from 216.239.38.10: bytes=32 time=352ms TTL=237
Reply from 216.239.38.10: bytes=32 time=328ms TTL=237
Reply from 216.239.38.10: bytes=32 time=331ms TTL=237
Reply from 216.239.38.10: bytes=32 time=326ms TTL=237
Request timed out.
Reply from 216.239.38.10: bytes=32 time=336ms TTL=237
Reply from 216.239.38.10: bytes=32 time=332ms TTL=237
Reply from 216.239.38.10: bytes=32 time=573ms TTL=237
Reply from 216.239.38.10: bytes=32 time=450ms TTL=237
Reply from 216.239.38.10: bytes=32 time=342ms TTL=237
Reply from 216.239.38.10: bytes=32 time=303ms TTL=237
Reply from 216.239.38.10: bytes=32 time=323ms TTL=237
Reply from 216.239.38.10: bytes=32 time=330ms TTL=237
Reply from 216.239.38.10: bytes=32 time=339ms TTL=237
Reply from 216.239.38.10: bytes=32 time=334ms TTL=237
Reply from 216.239.38.10: bytes=32 time=343ms TTL=237
Reply from 216.239.38.10: bytes=32 time=348ms TTL=237
Reply from 216.239.38.10: bytes=32 time=328ms TTL=237
Reply from 216.239.38.10: bytes=32 time=321ms TTL=237
Reply from 216.239.38.10: bytes=32 time=320ms TTL=237
Reply from 216.239.38.10: bytes=32 time=333ms TTL=237
Reply from 216.239.38.10: bytes=32 time=332ms TTL=237
Request timed out.
Reply from 216.239.38.10: bytes=32 time=331ms TTL=237
Reply from 216.239.38.10: bytes=32 time=330ms TTL=237

Ping statistics for 216.239.38.10:
Packets: Sent = 30, Received = 28, Lost = 2 (6% loss),
Approximate round trip times in milli-seconds:
Minimum = 303ms, Maximum = 573ms, Average = 347ms

and here is another IP for comparison

Pinging 216.239.59.99 with 32 bytes of data:

Ping statistics for 216.239.59.99:
Packets: Sent = 32, Received = 22, Lost = 10 (31% loss),
Approximate round trip times in milli-seconds:
Minimum = 253ms, Maximum = 574ms, Average = 301ms
 
Stats at 15:00 04/02/2007

Ping statistics for 216.239.38.10:
Packets: Sent = 30, Received = 23, Lost = 7 (23% loss),
Approximate round trip times in milli-seconds:
Minimum = 307ms, Maximum = 548ms, Average = 359ms
 
Mercury said:
My usual package of pings:

----83.138.189.100 PING Statistics----
66 packets transmitted, 54 packets received, 18% packet loss
round-trip (ms) min/avg/max = 220/272/390

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

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

Special request:

----216.239.38.10 PING Statistics----
30 packets transmitted, 25 packets received, 16% packet loss
round-trip (ms) min/avg/max = 320/351/470

Yup, looks like an international issue.
Click to expand...

Today's update:

----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?
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X