Amazingly slow ?

Looks okay over here, (Cape Town, Bellville Tower)

Pinging myadsl.co.za [196.40.97.12] with 32 bytes of data:

Reply from 196.40.97.12: bytes=32 time=44ms TTL=247
Reply from 196.40.97.12: bytes=32 time=54ms TTL=247
Reply from 196.40.97.12: bytes=32 time=53ms TTL=247
Reply from 196.40.97.12: bytes=32 time=52ms TTL=247
Reply from 196.40.97.12: bytes=32 time=61ms TTL=247
Reply from 196.40.97.12: bytes=32 time=66ms TTL=247
Reply from 196.40.97.12: bytes=32 time=64ms TTL=247
Reply from 196.40.97.12: bytes=32 time=54ms TTL=247
Reply from 196.40.97.12: bytes=32 time=53ms TTL=247
Reply from 196.40.97.12: bytes=32 time=102ms TTL=247

Ping statistics for 196.40.97.12:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 44ms, Maximum = 102ms, Average = 60ms
 
Looking a bit better than earlier but still not good enough:

---------------
Pinging 196.40.97.13 with 32 bytes of data:

Reply from 196.40.97.13: bytes=32 time=66ms TTL=247
Reply from 196.40.97.13: bytes=32 time=58ms TTL=247
Reply from 196.40.97.13: bytes=32 time=383ms TTL=247
Reply from 196.40.97.13: bytes=32 time=74ms TTL=247
Reply from 196.40.97.13: bytes=32 time=60ms TTL=247
Reply from 196.40.97.13: bytes=32 time=80ms TTL=247
Reply from 196.40.97.13: bytes=32 time=176ms TTL=247
Reply from 196.40.97.13: bytes=32 time=65ms TTL=247
Reply from 196.40.97.13: bytes=32 time=65ms TTL=247
Reply from 196.40.97.13: bytes=32 time=171ms TTL=247
Reply from 196.40.97.13: bytes=32 time=121ms TTL=247
Reply from 196.40.97.13: bytes=32 time=81ms TTL=247
Reply from 196.40.97.13: bytes=32 time=62ms TTL=247
Reply from 196.40.97.13: bytes=32 time=163ms TTL=247
Reply from 196.40.97.13: bytes=32 time=65ms TTL=247

Ping statistics for 196.40.97.13:
Packets: Sent = 15, Received = 15, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 58ms, Maximum = 383ms, Average = 112ms
----------------
 
Ping statistics for 196.40.97.13:
Packets: Sent = 35, Received = 35, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 92ms, Maximum = 131ms, Average = 110ms
 
Its a Cape Town based server, I assume, so JHB pings to myadsl are always worse, yours look very good for up there though :)
 
Need I say more...

I just hope Vodacom/Telkom takes over this badly BEE run company soon! - It can't continue like this for much longer...

C:\>ping 196.40.97.13 -t -l 1

Pinging 196.40.97.13 with 1 bytes of data:

Reply from 196.40.97.13: bytes=1 time=59ms TTL=247
Request timed out.
Reply from 196.40.97.13: bytes=1 time=65ms TTL=247
Request timed out.
Reply from 196.40.97.13: bytes=1 time=64ms TTL=247
Reply from 196.40.97.13: bytes=1 time=62ms TTL=247
Request timed out.
Reply from 196.40.97.13: bytes=1 time=58ms TTL=247
Reply from 196.40.97.13: bytes=1 time=57ms TTL=247
Reply from 196.40.97.13: bytes=1 time=60ms TTL=247
Reply from 196.40.97.13: bytes=1 time=69ms TTL=247
Reply from 196.40.97.13: bytes=1 time=67ms TTL=247
Reply from 196.40.97.13: bytes=1 time=71ms TTL=247
Reply from 196.40.97.13: bytes=1 time=59ms TTL=247
Reply from 196.40.97.13: bytes=1 time=163ms TTL=247
Reply from 196.40.97.13: bytes=1 time=66ms TTL=247
Reply from 196.40.97.13: bytes=1 time=70ms TTL=247
Reply from 196.40.97.13: bytes=1 time=70ms TTL=247
Reply from 196.40.97.13: bytes=1 time=62ms TTL=247
Reply from 196.40.97.13: bytes=1 time=60ms TTL=247

Ping statistics for 196.40.97.13:
Packets: Sent = 20, Received = 17, Lost = 3 (15% loss)
Approximate round trip times in milli-seconds:
Minimum = 57ms, Maximum = 163ms, Average = 69ms
 
Michael, right now yours is looking a lot better than mine except for the lost packets.
 
That aint good news....

Was unable to use P2P connections this week, the iBurst network was just too slow, and connection times out too frequently!

Surely we should be able to lodge a complaint either by ICASA or with the ASA?

This is just not on!
 
Ping done right now:
---------------
Pinging 196.40.97.13 with 32 bytes of data:

Reply from 196.40.97.13: bytes=32 time=291ms TTL=247
Reply from 196.40.97.13: bytes=32 time=342ms TTL=247
Reply from 196.40.97.13: bytes=32 time=236ms TTL=247
Reply from 196.40.97.13: bytes=32 time=285ms TTL=247
Reply from 196.40.97.13: bytes=32 time=148ms TTL=247
Reply from 196.40.97.13: bytes=32 time=171ms TTL=247
Reply from 196.40.97.13: bytes=32 time=263ms TTL=247
Reply from 196.40.97.13: bytes=32 time=297ms TTL=247
Reply from 196.40.97.13: bytes=32 time=338ms TTL=247
Reply from 196.40.97.13: bytes=32 time=175ms TTL=247

Ping statistics for 196.40.97.13:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 148ms, Maximum = 342ms, Average = 254ms
-----------------
No packet loss but look at the ms times.:(
 
ICASA or with the ASA don't have any "teeth" or something would have been done long ago.
 
Yeah, but there must be a way to get this incompetent crowd to honour there promises?

It's currently a rip-off, to say the least – inflated prices, nonexistent support service, poor service delivery, etc…
 
You're forgetting where we are, it's all about grabbing as much $$ and doing as little as possible in order to get hold of it no matter what the customer thinks.

I was a fool and had great hopes that iBurst would be different until I woke up.:eek:

The words "service delivery" in this country is a dirty word.
 
C:\>ping google.com

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

Reply from 64.233.167.99: bytes=32 time=618ms TTL=240
Request timed out.
Reply from 64.233.167.99: bytes=32 time=569ms TTL=240
Reply from 64.233.167.99: bytes=32 time=578ms TTL=240

Ping statistics for 64.233.167.99:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 569ms, Maximum = 618ms, Average = 588ms

C:\>ping google.com -t -l 1

Pinging google.com [64.233.167.99] with 1 bytes of data:

Reply from 64.233.167.99: bytes=1 time=548ms TTL=240
Reply from 64.233.167.99: bytes=1 time=602ms TTL=240
Reply from 64.233.167.99: bytes=1 time=569ms TTL=240
Request timed out.
Reply from 64.233.167.99: bytes=1 time=587ms TTL=240
Reply from 64.233.167.99: bytes=1 time=596ms TTL=240
Reply from 64.233.167.99: bytes=1 time=567ms TTL=240
Reply from 64.233.167.99: bytes=1 time=628ms TTL=240
Reply from 64.233.167.99: bytes=1 time=557ms TTL=240
Reply from 64.233.167.99: bytes=1 time=552ms TTL=240
Reply from 64.233.167.99: bytes=1 time=584ms TTL=240
Reply from 64.233.167.99: bytes=1 time=627ms TTL=240
Reply from 64.233.167.99: bytes=1 time=570ms TTL=240
Reply from 64.233.167.99: bytes=1 time=602ms TTL=240
Reply from 64.233.167.99: bytes=1 time=616ms TTL=240
Reply from 64.233.167.99: bytes=1 time=559ms TTL=240
Request timed out.
Reply from 64.233.167.99: bytes=1 time=596ms TTL=240
Reply from 64.233.167.99: bytes=1 time=549ms TTL=240
Reply from 64.233.167.99: bytes=1 time=568ms TTL=240
Reply from 64.233.167.99: bytes=1 time=606ms TTL=240
Reply from 64.233.167.99: bytes=1 time=564ms TTL=240
Reply from 64.233.167.99: bytes=1 time=552ms TTL=240
Reply from 64.233.167.99: bytes=1 time=595ms TTL=240
Reply from 64.233.167.99: bytes=1 time=573ms TTL=240
Reply from 64.233.167.99: bytes=1 time=731ms TTL=240
Request timed out.
Reply from 64.233.167.99: bytes=1 time=582ms TTL=240

Ping statistics for 64.233.167.99:
Packets: Sent = 28, Received = 25, Lost = 3 (10% loss),
Approximate round trip times in milli-seconds:
Minimum = 548ms, Maximum = 731ms, Average = 587ms
 
Thats just about what I've been seeing lately, but ADSL users in Cape Town have been having problems too, it might just be the international connection?

Anyway... ADSL still just seems magical from his side :/
 
My HTTP is fine but I can't use torrents at all!? :( it just says connection closed by peer on every torrent local and international...anyone else with a similar problem?
 
I can use torrents but they're acting up, so is the DC++ Hub.

I think iBurst are redesigning their shaping to mess us around even more as the problem only seems to be on a p2p level. Someone should call them and complain that we can't get our warez on.
 
I'm glad it's not just me who's gettign cr@p speeds. I thought maby they were getting back at me for downloading too much...Hope this will will be sorted out soon. I'm getting less than 500Bytes per second transfer rate.
 
Maybe thats the new improvement they've been talking about, completely blocking P2P to speed up their network. :D :D

Sounds great, keep up the good work iBurst.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X