massive packet loss again

M

markos

Member
Joined
Feb 2, 2007
Messages
16
Reaction score
0
Hi all,
In the last few day's me and a few friends using iburst have been experiencing massive packet loss both internationally and localy. After contacting iburst help desk and asking them to ping google they are experiencing the same problem in the head office.

This is not the first time it happened, a few months ago the same thing went on and after 2 weeks it got fixed only after i started making posts like this on the forums and brought it to peoples attention.

I would like to ask all iburst users to help me in getting this resolved asap not like last time, so please run the ping commands pasted here and call/mail iburst with details to prove that this is not isolated, they have a problem on the network affecting all paying users and we need this resolved asap.

Thanx
Regards

pinging www.google.com (30% packet loss)

Pinging 66.218.71.63 with 32 bytes of data:

Reply from 66.218.71.63: bytes=32 time=492ms TTL=48
Request timed out.
Reply from 66.218.71.63: bytes=32 time=460ms TTL=49
Reply from 66.218.71.63: bytes=32 time=419ms TTL=49
Request timed out.
Request timed out.
Reply from 66.218.71.63: bytes=32 time=740ms TTL=49
Reply from 66.218.71.63: bytes=32 time=449ms TTL=49
Reply from 66.218.71.63: bytes=32 time=501ms TTL=49
Reply from 66.218.71.63: bytes=32 time=471ms TTL=48

Ping statistics for 66.218.71.63:
Packets: Sent = 10, Received = 7, Lost = 3 (30% loss),
Approximate round trip times in milli-seconds:
Minimum = 419ms, Maximum = 740ms, Average = 504ms


pinging www.google.co.za (30% packet loss)

Pinging 216.239.38.10 with 32 bytes of data:

Request timed out.
Reply from 216.239.38.10: bytes=32 time=347ms TTL=237
Request timed out.
Request timed out.
Reply from 216.239.38.10: bytes=32 time=351ms TTL=237
Reply from 216.239.38.10: bytes=32 time=346ms TTL=237
Reply from 216.239.38.10: bytes=32 time=443ms TTL=237
Reply from 216.239.38.10: bytes=32 time=348ms TTL=237
Reply from 216.239.38.10: bytes=32 time=334ms TTL=237
Reply from 216.239.38.10: bytes=32 time=504ms TTL=237

Ping statistics for 216.239.38.10:
Packets: Sent = 10, Received = 7, Lost = 3 (30% loss),
Approximate round trip times in milli-seconds:
Minimum = 334ms, Maximum = 504ms, Average = 381ms
 
I forgot to paste command for people who dont know.

ping -n 10 66.218.71.63
ping -n 10 216.239.38.10
 
66.218.71.63 - 40% Loss
216.239.38.10 - 10% Loss

"hmm maybe we should only pay them a % of subscription fee for a % of their service"

:(
 
Last edited:
ping and stuff ..

yay .. another night of not playing online games. *sigh*

root@han:~# ping -c 10 66.218.71.63
PING 66.218.71.63 (66.218.71.63) 56(84) bytes of data.
64 bytes from 66.218.71.63: icmp_seq=1 ttl=48 time=475 ms
64 bytes from 66.218.71.63: icmp_seq=2 ttl=47 time=1346 ms
64 bytes from 66.218.71.63: icmp_seq=3 ttl=48 time=421 ms
64 bytes from 66.218.71.63: icmp_seq=4 ttl=48 time=566 ms
64 bytes from 66.218.71.63: icmp_seq=8 ttl=48 time=462 ms
64 bytes from 66.218.71.63: icmp_seq=9 ttl=48 time=717 ms
64 bytes from 66.218.71.63: icmp_seq=10 ttl=47 time=432 ms

--- 66.218.71.63 ping statistics ---
10 packets transmitted, 7 received, 30% packet loss, time 9054ms
rtt min/avg/max/mdev = 421.191/631.817/1346.209/306.841 ms, pipe 2

PING 216.239.38.10 (216.239.38.10) 56(84) bytes of data.
64 bytes from 216.239.38.10: icmp_seq=2 ttl=236 time=330 ms
64 bytes from 216.239.38.10: icmp_seq=3 ttl=236 time=349 ms
64 bytes from 216.239.38.10: icmp_seq=4 ttl=236 time=460 ms
64 bytes from 216.239.38.10: icmp_seq=5 ttl=236 time=356 ms
64 bytes from 216.239.38.10: icmp_seq=6 ttl=236 time=375 ms
64 bytes from 216.239.38.10: icmp_seq=7 ttl=236 time=380 ms
64 bytes from 216.239.38.10: icmp_seq=9 ttl=236 time=366 ms
64 bytes from 216.239.38.10: icmp_seq=10 ttl=236 time=341 ms

--- 216.239.38.10 ping statistics ---
10 packets transmitted, 8 received, 20% packet loss, time 9084ms
rtt min/avg/max/mdev = 330.584/370.062/460.170/37.542 ms

I really am beginning to hate This country.
 
I win

:D
Code: 
Pinging [url]www.l.google.com[/url] [66.249.93.147] with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 66.249.93.147: bytes=32 time=366ms TTL=235
Reply from 66.249.93.147: bytes=32 time=465ms TTL=235
Request timed out.
Reply from 66.249.93.147: bytes=32 time=471ms TTL=235
Reply from 66.249.93.147: bytes=32 time=401ms TTL=235
Reply from 66.249.93.147: bytes=32 time=320ms TTL=235

Ping statistics for 66.249.93.147:
    Packets: Sent = 10, Received = 5, Lost = 5 ([B][COLOR="Red"]50% loss[/COLOR][/B]),
Approximate round trip times in milli-seconds:
    Minimum = 320ms, Maximum = 471ms, Average = 404ms

Pinging 66.218.71.63 with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Reply from 66.218.71.63: bytes=32 time=452ms TTL=48
Reply from 66.218.71.63: bytes=32 time=743ms TTL=47
Request timed out.
Reply from 66.218.71.63: bytes=32 time=502ms TTL=47
Reply from 66.218.71.63: bytes=32 time=509ms TTL=48
Request timed out.
Reply from 66.218.71.63: bytes=32 time=628ms TTL=48

Ping statistics for 66.218.71.63:
    Packets: Sent = 10, Received = 5, Lost = 5 ([B][COLOR="Red"]50% loss[/COLOR][/B]),
Approximate round trip times in milli-seconds:
    Minimum = 452ms, Maximum = 743ms, Average = 566ms

C:Documents and SettingsDeon>ping -n 10 216.239.38.10

Pinging 216.239.38.10 with 32 bytes of data:

Reply from 216.239.38.10: bytes=32 time=499ms TTL=236
Request timed out.
Request timed out.
Reply from 216.239.38.10: bytes=32 time=372ms TTL=236
Reply from 216.239.38.10: bytes=32 time=406ms TTL=236
Reply from 216.239.38.10: bytes=32 time=406ms TTL=236
Reply from 216.239.38.10: bytes=32 time=372ms TTL=236
Request timed out.
Request timed out.
Reply from 216.239.38.10: bytes=32 time=402ms TTL=236

Ping statistics for 216.239.38.10:
    Packets: Sent = 10, Received = 6, Lost = 4 (40% loss),
Approximate round trip times in milli-seconds:
    Minimum = 372ms, Maximum = 499ms, Average = 409ms
 
Last edited:
Looks like it's region specific.

Pinging www.l.google.com [66.249.93.104] with 32 bytes of data:

Reply from 66.249.93.104: bytes=32 time=366ms TTL=236
Reply from 66.249.93.104: bytes=32 time=365ms TTL=236
Reply from 66.249.93.104: bytes=32 time=419ms TTL=236
Reply from 66.249.93.104: bytes=32 time=378ms TTL=236

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

Are ther any other Durbanites experiencing packet loss?
 
Ping statistics for 66.218.71.63:
Packets: Sent = 10, Received = 5, Lost = 5 (50% loss),
Approximate round trip times in milli-seconds:
Minimum = 413ms, Maximum = 612ms, Average = 472ms

Ping statistics for 216.239.38.10:
Packets: Sent = 10, Received = 4, Lost = 6 (60% lo
Approximate round trip times in milli-seconds:
Minimum = 349ms, Maximum = 417ms, Average = 383ms
 
Been fine here in Cape Town.

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

Reply from 72.14.207.99: bytes=32 time=335ms TTL=238
Reply from 72.14.207.99: bytes=32 time=365ms TTL=238
Reply from 72.14.207.99: bytes=32 time=360ms TTL=238
Reply from 72.14.207.99: bytes=32 time=355ms TTL=238
Reply from 72.14.207.99: bytes=32 time=355ms TTL=238
Reply from 72.14.207.99: bytes=32 time=359ms TTL=238
Reply from 72.14.207.99: bytes=32 time=353ms TTL=238
Reply from 72.14.207.99: bytes=32 time=368ms TTL=238
Reply from 72.14.207.99: bytes=32 time=379ms TTL=238
Reply from 72.14.207.99: bytes=32 time=358ms TTL=238

Ping statistics for 72.14.207.99:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 335ms, Maximum = 379ms, Average = 358ms

Local:

Pinging 41.208.232.1 with 32 bytes of data:

Reply from 41.208.232.1: bytes=32 time=62ms TTL=255
Reply from 41.208.232.1: bytes=32 time=64ms TTL=255
Reply from 41.208.232.1: bytes=32 time=64ms TTL=255
Reply from 41.208.232.1: bytes=32 time=64ms TTL=255
Reply from 41.208.232.1: bytes=32 time=64ms TTL=255
Reply from 41.208.232.1: bytes=32 time=64ms TTL=255
Reply from 41.208.232.1: bytes=32 time=64ms TTL=255
Reply from 41.208.232.1: bytes=32 time=79ms TTL=255
Reply from 41.208.232.1: bytes=32 time=64ms TTL=255
Reply from 41.208.232.1: bytes=32 time=79ms TTL=255

Ping statistics for 41.208.232.1:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 62ms, Maximum = 79ms, Average = 66ms

btw google.co.za isn't local. Rather use myadsl.co.za.
 
Pinging www.l.google.com [64.233.183.103] with 32 bytes of data:

Reply from 64.233.183.103: bytes=32 time=364ms TTL=236
Request timed out.
Request timed out.
Reply from 64.233.183.103: bytes=32 time=345ms TTL=236

Ping statistics for 64.233.183.103:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
Minimum = 345ms, Maximum = 364ms, Average = 354ms


Pinging www.l.google.com [64.233.183.103] with 32 bytes of data:

Reply from 64.233.183.103: bytes=32 time=352ms TTL=236
Request timed out.
Reply from 64.233.183.103: bytes=32 time=361ms TTL=236
Reply from 64.233.183.103: bytes=32 time=351ms TTL=236

Ping statistics for 64.233.183.103:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 351ms, Maximum = 361ms, Average = 354ms


Request timed out.
Reply from 64.233.183.103: bytes=32 time=396ms TTL=236
Reply from 64.233.183.103: bytes=32 time=361ms TTL=236
Request timed out.

Ping statistics for 64.233.183.103:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
Minimum = 361ms, Maximum = 396ms, Average = 378ms



This makes sense now why I am getting errors downloading big emails from gmail in outlook at work and sometimes at home
 
:eek:WOO HOO what a night it almost felt like playing in JPEG. Anyone else had the same feeling?
 
I had a horrible time playing Guild Wars last night. Latency was insane. I did kinda feel like watching a slide show
 
Can't wow...browsing is slow...I hate this place -_- Nothing ever changes...I am REALLY getting fed up now. Been with iburst since the beginning and they just never can get it right. Every other week theres packet loss or some problems that don't allow me to do what I want with my internet. If I wasn't moving to UK in a few months I would have ordered my ADSL today...I have had enough! But then again ADSL is only a bit better as well. Most of my friends have ADSL and they have gone weeks with massive packet loss also :/ But I think iburst is the worst by far! I guess this is africa hey :/

Pinging www.l.google.com [66.249.93.104] with 32 bytes of data:

Ping statistics for 66.249.93.104:
Packets: Sent = 20, Received = 16, Lost = 4 (20% loss),
Approximate round trip times in milli-seconds:
Minimum = 249ms, Maximum = 375ms, Average = 310ms
 
Guys...surely I don't have to tel you that you need to ping more than just 4 or 10 times for a accurate reading? I would say minimum 20 pings for example
--> ping insert address here -n 20

I can also ping 4 or even 10 times and not get packet loss...the more you ping the more likely you will be to see the extent of the problem.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X