Performance issues AGAIN?

For this time of day speeds seem to be normal again at least from the Plumstead tower.
---------
Below is the data used to calculate your download speed:

* Download time: 4.36 seconds
* Size of file: 500 KiloBytes
* Estimated line speed: 935.8 (kilobits/second)
* Estimated line speed: 114.7 (kiloBytes/second)
 
Slicky said:
i've checked the Verizon website and it has no important notices about a router down or anything that affects speed or connectivity. Still have to check IS, does iburst even use IS?
Click to expand...

I think they use a combination of both.
 
Wow I evny you Mr.H, what time of day is that exactly? Middle of the day or at night, either way thats a great speed, well these days it is. I might move back to plumbstead just for the internet. Terrible what our crappy internet can make us do...
 
Ekhaatvensters said:
Wow I evny you Mr.H, what time of day is that exactly? Middle of the day or at night, either way thats a great speed, well these days it is. I might move back to plumbstead just for the internet. Terrible what our crappy internet can make us do...
Click to expand...

I did that speed test just before I posted my last reply so it must have been around 9:34am

I don't normally have bad speeds during the day, of course it's not as good as during the night but in general it's pretty fast from the Plumstead tower.
Not sure if it makes any difference but my PC room is upstairs and not much in the way between me and the tower.
 
Must be making a huge difference, I am feeling the problems that everyone is complaining about. Right now I am running DU meter and my speed never goes over 80kb/s (as in really slow, not the OK download speeds of 80Kb/s) even when opening 2-4 pages it also stops every 2 seconds, literally, very bad packet loss is causing this, i can see it when I ping any address.

It is absoloutley terrible, weird that you arent affected by it though. Well I'm giving them a call or two or three tomorrow if this carries on.
Well I'm happy for you at least Mr.H... Being on about the same level as the tower or at least alot higher up than most people and living within a kilometer of the tower with perfect LOS must be great, you mind showing me some pings to say www.mybroadband.co.za and dslreports.com or google.com, Please? I would just like to compare and see how Iburst performs pretty much at its best. Oh look at me I'm even flattering your connecting....
 
Last edited:
I have the same problem if I trie to copy my ping or tracert results, once finished the window just closes. We must be missing something really simple because everyone else does it just fine, any help someone?

Those are some great pings though (fro Iburst, before anyone jumps on me, thanks)... very stable and a bit better than my own. My international to dslreports is about 530-580 and with big jumps to around 600-700ms every four or five pings. At the moment alot of "destination unreachable" packet loss.
 
yes and it seems to be worse now than when I posted +_ 1hr ago. Local is fine but international is a bit dodgy right now.
Some websites are giving me timeouts with the first attempt now.:eek:
 
me too:
this is local:(telkom speed test)

Below is the data used to calculate your download speed:

Download time: 4.641 seconds
Size of file: 500 KiloBytes
Estimated line speed: 879.1 (kilobits/second)
Estimated line speed: 107.7 (kiloBytes/second)

international is about 200kpbs
 
Capture pings / tracert

MrH said:
Well I pinged http://www.mybroadband.co.za/ and it was not too bad, but the pings to dslreports.com or google.com really suck right now.

How do you capture text from a CMD screen?

http://img236.imageshack.us/img236/1479/pingmybroadband10ms.jpg

http://img236.imageshack.us/img236/7213/pingdslreports16nv.jpg
Click to expand...


Get a command prompt window and run the command from there: So don't "Start" "Run" "ping 123.123.123.123", but "start" "run" "cmd". This will give you a dos box to run ping in that wont dissapear.

Otherwise if you know that stuff, right click on the title bar of the command window and choose edit - mark ............. mouse a bit and push enter.
 
Last edited:
DDT said:
Get a command prompt window and run the command from there: So don't "Start" "Run" "ping 123.123.123.123", but "start" "run" "cmd". This will give you a dos box to run ping in that wont dissapear.

Otherwise if you know that stuff, right click on the title bar of the command window and choose edit - mark ............. mouse a bit and push enter.
Click to expand...

I know about "start" "run" "cmd" and I don't have the same problem of it disapearing, but thanks for the info of how to capture the text as that part I did not know about.
Should make it quicker to post next time it's needed.
 
Just did another ping a min ago to mybroadband which seems a little better than the last ping, but dslreports.com is still giving me high pings.


Pinging www.mybroadband.co.za [196.7.147.165] with 32 bytes of data:

Reply from 196.7.147.165: bytes=32 time=41ms TTL=249
Reply from 196.7.147.165: bytes=32 time=70ms TTL=249
Reply from 196.7.147.165: bytes=32 time=75ms TTL=249
Reply from 196.7.147.165: bytes=32 time=55ms TTL=249
Reply from 196.7.147.165: bytes=32 time=61ms TTL=249
Reply from 196.7.147.165: bytes=32 time=59ms TTL=249
Reply from 196.7.147.165: bytes=32 time=56ms TTL=249
Reply from 196.7.147.165: bytes=32 time=72ms TTL=249
Reply from 196.7.147.165: bytes=32 time=56ms TTL=249
Reply from 196.7.147.165: bytes=32 time=56ms TTL=249
Reply from 196.7.147.165: bytes=32 time=64ms TTL=249
Reply from 196.7.147.165: bytes=32 time=59ms TTL=249
Reply from 196.7.147.165: bytes=32 time=55ms TTL=249
Reply from 196.7.147.165: bytes=32 time=53ms TTL=249
Reply from 196.7.147.165: bytes=32 time=54ms TTL=249
Reply from 196.7.147.165: bytes=32 time=57ms TTL=249
Reply from 196.7.147.165: bytes=32 time=54ms TTL=249
Reply from 196.7.147.165: bytes=32 time=60ms TTL=249
Reply from 196.7.147.165: bytes=32 time=73ms TTL=249
Reply from 196.7.147.165: bytes=32 time=63ms TTL=249
Reply from 196.7.147.165: bytes=32 time=61ms TTL=249

Ping statistics for 196.7.147.165:
Packets: Sent = 21, Received = 21, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 41ms, Maximum = 75ms, Average = 59ms
 
Fourways - POOR!!

For all it's worth, becuase I'm sure that no-one from iBurst, WBS, etc, actually reads or takes note of what is said on these forums, but I am getting terrible speeds here in Fourways, Lonehill area.

Last week it was pumping but this week it has become worse and today is terrible. Connected VIA GPS on my cell phone to write this!!!!
 
I haven't had issues with speed in quite some time. Until tonight. Downloading Ubuntu updates at a whopping 3000B/s ... It is going to take me days!

Pings all over the show:

PING www.iburst.co.za (196.30.31.120) 56(84) bytes of data.
64 bytes from 196.30.31.120: icmp_seq=1 ttl=124 time=43.1 ms
64 bytes from 196.30.31.120: icmp_seq=2 ttl=124 time=66.9 ms
64 bytes from 196.30.31.120: icmp_seq=3 ttl=124 time=219 ms
64 bytes from 196.30.31.120: icmp_seq=4 ttl=124 time=61.6 ms
64 bytes from 196.30.31.120: icmp_seq=5 ttl=124 time=115 ms
64 bytes from 196.30.31.120: icmp_seq=6 ttl=124 time=551 ms
64 bytes from 196.30.31.120: icmp_seq=7 ttl=124 time=48.3 ms
64 bytes from 196.30.31.120: icmp_seq=8 ttl=124 time=140 ms
64 bytes from 196.30.31.120: icmp_seq=9 ttl=124 time=262 ms
64 bytes from 196.30.31.120: icmp_seq=10 ttl=124 time=129 ms
64 bytes from 196.30.31.120: icmp_seq=11 ttl=124 time=82.4 ms
 
I am on the Bryanston tower;

Pinging www.iburst.co.za [196.30.31.120] with 32 bytes of data:

Reply from 196.30.31.120: bytes=32 time=60ms TTL=124
Reply from 196.30.31.120: bytes=32 time=75ms TTL=124
Reply from 196.30.31.120: bytes=32 time=50ms TTL=124
Reply from 196.30.31.120: bytes=32 time=177ms TTL=124
Reply from 196.30.31.120: bytes=32 time=145ms TTL=124
Reply from 196.30.31.120: bytes=32 time=302ms TTL=124
Reply from 196.30.31.120: bytes=32 time=325ms TTL=124
Reply from 196.30.31.120: bytes=32 time=41ms TTL=124
Reply from 196.30.31.120: bytes=32 time=222ms TTL=124
Reply from 196.30.31.120: bytes=32 time=174ms TTL=124
Reply from 196.30.31.120: bytes=32 time=190ms TTL=124
Reply from 196.30.31.120: bytes=32 time=113ms TTL=124
Reply from 196.30.31.120: bytes=32 time=79ms TTL=124
Reply from 196.30.31.120: bytes=32 time=163ms TTL=124
Reply from 196.30.31.120: bytes=32 time=61ms TTL=124
Reply from 196.30.31.120: bytes=32 time=113ms TTL=124
Reply from 196.30.31.120: bytes=32 time=223ms TTL=124
Reply from 196.30.31.120: bytes=32 time=70ms TTL=124
Reply from 196.30.31.120: bytes=32 time=66ms TTL=124

Ping statistics for 196.30.31.120:
Packets: Sent = 19, Received = 19, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 41ms, Maximum = 325ms, Average = 139ms

I suspect these towers are oversubscribed, hopefully the new epsom downs BS will help.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X