Amazingly slow ?

[marine1]

It's the end of the world as we know it......la la la here I come Vodacom 3G with HSDPA

 

[MrH]

Certainly looks like they don't know how to fix it since I can't see them leaving it this way for almost a week with the competition winning over customers, UNLESS they DO NOT KNOW how to fix it.

I notice that SHAUN GREEN has also seemed to have disappeared from the forums around the same time as Ed, I guess he has no answers to the problems either.

 

[dsd]

night has fallen, and with it comes errant behaviour of the iBurst speed vampire - will they find it? is there a silver bullet?

we'll probably never know....

 

[DaEvAnAm]

Well i know that the 2 companies that i have dealt with concerning iBurst have both "disappeared" and so has my speed along with Ed and Shaun and all that iBurst offered. Time to enquire about other options.

 

[MrH]

Look here:

http://www.iburst.co.za/default.aspx?link=support_network

CT totally screwed up yet again

 

[GreatBigMouth]

Wow, more than 50% of CT base stations are either down or degraded.

The rest of us are experiencing rather k@k speeds at this time. Last time I checked, it was 300kb/s. Quality of service is at a mere 24%.

I must say, March has been my worst month on iBurst.

 

[dsd]

As expected, things are nice and speedy again during the day. Seen as this is a public holiday, I don't think we can blame the problem on residential users.

I agree with MrH - there is some problem that either 1) they haven't identified properly, or 2) they don't know how to fix it. They really need to sort this out. I'm happy with the service in general, but having an erratic week once a month is just not on.

More night time issues here, http://mybroadband.co.za/vb/showthread.php?t=69771

 

[Ekhaatvensters]

Look here:

http://www.iburst.co.za/default.aspx?link=support_network

CT totally screwed up yet again

It took then long enough to report this, there were obvious problems a day or two before.

 

[Ekhaatvensters]

Hey I just checked my pings, and they are great. Better than I have ever seen on my connection. Is this just because of the public holiday, can it actually be so much better even during the day?

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

Reply from 196.40.97.13: bytes=32 time=81ms TTL=248
Reply from 196.40.97.13: bytes=32 time=57ms TTL=248
Reply from 196.40.97.13: bytes=32 time=52ms TTL=248
Reply from 196.40.97.13: bytes=32 time=63ms TTL=248
Reply from 196.40.97.13: bytes=32 time=52ms TTL=248
Reply from 196.40.97.13: bytes=32 time=52ms TTL=248
Reply from 196.40.97.13: bytes=32 time=52ms TTL=248
Reply from 196.40.97.13: bytes=32 time=73ms TTL=248
Reply from 196.40.97.13: bytes=32 time=47ms TTL=248
Reply from 196.40.97.13: bytes=32 time=53ms TTL=248
Reply from 196.40.97.13: bytes=32 time=42ms TTL=248
Reply from 196.40.97.13: bytes=32 time=52ms TTL=248
Reply from 196.40.97.13: bytes=32 time=63ms TTL=248
Reply from 196.40.97.13: bytes=32 time=58ms TTL=248
Reply from 196.40.97.13: bytes=32 time=83ms TTL=248
Reply from 196.40.97.13: bytes=32 time=48ms TTL=248
Reply from 196.40.97.13: bytes=32 time=72ms TTL=248
Reply from 196.40.97.13: bytes=32 time=113ms TTL=248
Reply from 196.40.97.13: bytes=32 time=58ms TTL=248
Reply from 196.40.97.13: bytes=32 time=63ms TTL=248
Reply from 196.40.97.13: bytes=32 time=88ms TTL=248
Reply from 196.40.97.13: bytes=32 time=1849ms TTL=248
Reply from 196.40.97.13: bytes=32 time=96ms TTL=248
Reply from 196.40.97.13: bytes=32 time=48ms TTL=248
Reply from 196.40.97.13: bytes=32 time=103ms TTL=248
Reply from 196.40.97.13: bytes=32 time=53ms TTL=248
Reply from 196.40.97.13: bytes=32 time=88ms TTL=248
Reply from 196.40.97.13: bytes=32 time=58ms TTL=248
Reply from 196.40.97.13: bytes=32 time=98ms TTL=248
Reply from 196.40.97.13: bytes=32 time=78ms TTL=248

Ping statistics for 196.40.97.13:
Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 42ms, Maximum = 1849ms, Average = 126ms

Never mind the one huge spike, that is my stupid wireless adapter, its having some issues, it makes me lag in games on a LAN

 

[GreatBigMouth]

Those are some pretty good pings. Mine avg at about 170ms today.

 

[MrH]

Just did this ping test a min ago:
----------------
Reply from 196.40.97.13: bytes=32 time=60ms TTL=247
Reply from 196.40.97.13: bytes=32 time=130ms TTL=247
Reply from 196.40.97.13: bytes=32 time=66ms TTL=247
Reply from 196.40.97.13: bytes=32 time=61ms TTL=247
Reply from 196.40.97.13: bytes=32 time=61ms TTL=247
Reply from 196.40.97.13: bytes=32 time=61ms TTL=247
Reply from 196.40.97.13: bytes=32 time=71ms TTL=247
Reply from 196.40.97.13: bytes=32 time=212ms TTL=247
Reply from 196.40.97.13: bytes=32 time=61ms TTL=247
Reply from 196.40.97.13: bytes=32 time=56ms TTL=247
Reply from 196.40.97.13: bytes=32 time=56ms TTL=247
Reply from 196.40.97.13: bytes=32 time=56ms TTL=247
Reply from 196.40.97.13: bytes=32 time=121ms TTL=247
Reply from 196.40.97.13: bytes=32 time=57ms TTL=247
Reply from 196.40.97.13: bytes=32 time=87ms TTL=247
Reply from 196.40.97.13: bytes=32 time=62ms TTL=247
Reply from 196.40.97.13: bytes=32 time=43ms TTL=247
Reply from 196.40.97.13: bytes=32 time=68ms TTL=247
Reply from 196.40.97.13: bytes=32 time=78ms TTL=247
Reply from 196.40.97.13: bytes=32 time=64ms TTL=247
Reply from 196.40.97.13: bytes=32 time=64ms TTL=247
Reply from 196.40.97.13: bytes=32 time=65ms TTL=247
Reply from 196.40.97.13: bytes=32 time=69ms TTL=247
Reply from 196.40.97.13: bytes=32 time=64ms TTL=247
Reply from 196.40.97.13: bytes=32 time=70ms TTL=247
Reply from 196.40.97.13: bytes=32 time=61ms TTL=247
Reply from 196.40.97.13: bytes=32 time=65ms TTL=247
Reply from 196.40.97.13: bytes=32 time=66ms TTL=247
Reply from 196.40.97.13: bytes=32 time=61ms TTL=247
Reply from 196.40.97.13: bytes=32 time=202ms TTL=247

Ping statistics for 196.40.97.13:
Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 43ms, Maximum = 212ms, Average = 77ms
------------------

A few high pings that should not be there, but browsing is still much slower than normal, in fact browsing is slower now than when I'm capped which is bullsh!t.

 

[Ekhaatvensters]

Mines is completely messed up again, local around 300+ consistently and international almost 1000?

:/

 

[dsd]

Hey I just checked my pings, and they are great. Better than I have ever seen on my connection. Is this just because of the public holiday, can it actually be so much better even during the day?

I'm seeing pretty similar values at the moment. No problems with browsing or anything else - nice and fast at the moment....will have to wait and see what happens tonight though.

 

[DaEvAnAm]

Mine are still up to ****. Slow, timing out, slow browsing, unable to download ect..

 

[GreatBigMouth]

Mine's still pretty much the same. Not that bad but also not the best I've seen.

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

Reply from 196.40.97.12: bytes=32 time=110ms TTL=247
Reply from 196.40.97.12: bytes=32 time=124ms TTL=247
Reply from 196.40.97.12: bytes=32 time=124ms TTL=247
Reply from 196.40.97.12: bytes=32 time=125ms TTL=247
Reply from 196.40.97.12: bytes=32 time=124ms TTL=247
Reply from 196.40.97.12: bytes=32 time=124ms TTL=247
Reply from 196.40.97.12: bytes=32 time=109ms TTL=247
Reply from 196.40.97.12: bytes=32 time=124ms TTL=247
Reply from 196.40.97.12: bytes=32 time=140ms TTL=247
Reply from 196.40.97.12: bytes=32 time=203ms 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 = 109ms, Maximum = 203ms, Average = 130ms

 

[MrH]

Mine seems to have gone over to the "dark side"

Amazing how quiet iBurst have been when they read this forum, yet they advertise for more suckers.

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

Reply from 196.40.97.13: bytes=32 time=315ms TTL=247
Reply from 196.40.97.13: bytes=32 time=265ms TTL=247
Reply from 196.40.97.13: bytes=32 time=409ms TTL=247
Request timed out.
Reply from 196.40.97.13: bytes=32 time=244ms TTL=247
Reply from 196.40.97.13: bytes=32 time=206ms TTL=247
Reply from 196.40.97.13: bytes=32 time=204ms TTL=247
Request timed out.
Reply from 196.40.97.13: bytes=32 time=199ms TTL=247
Reply from 196.40.97.13: bytes=32 time=192ms TTL=247
Reply from 196.40.97.13: bytes=32 time=154ms TTL=247
Reply from 196.40.97.13: bytes=32 time=43ms TTL=247
Reply from 196.40.97.13: bytes=32 time=205ms TTL=247
Reply from 196.40.97.13: bytes=32 time=60ms TTL=247

Ping statistics for 196.40.97.13:
Packets: Sent = 14, Received = 12, Lost = 2 (14% loss),
Approximate round trip times in milli-seconds:
Minimum = 43ms, Maximum = 409ms, Average = 208ms
---------------

 

[Jongi]

1. Cancellation notice. Check.
2. ADSL order placed. Check.

 

[Ekhaatvensters]

1. Cancellation notice. Check.
2. ADSL order placed. Check.

How long does the ADSL self install usually take to get authorised? If anyone here has any idea.

 

[Pilgrim]

How long does the ADSL self install usually take to get authorised? If anyone here has any idea.

Anything from now to never

 

[Jongi]

The fella at the Telkom shop in Rosebank (Jhb) informed me within 9 days I should get a call from the technicians telling me to go pick up the free Wifi for a self install.