*READ FIRST* iBurst Network Status & Issues (DNS, Throughput and Latency)

r00igev@@r said:
Please PM me your UTID so that I can fwd it to Operations.
Tx
Click to expand...

With all due respect to you and Mel for at least trying to keep iBurst customers happy, we are beyond gatvol for iBurst.
10 months of nothing but frustration due to paying R800-00 per month for an internet connection that went from brilliant to a sub-standard service within a month (from 2+Mb/s during the day at the beginning of December 2011 to less than dial-up at the end of December 2011 and still continues up to today, 10 months later), we will stick it out for until March 2013 when I will make a bonfire in our back yard and throw the 2Mb modem, cables, power supply, flat panel antenna, splitter, etc into that fire.

Then I will do a happy dance around the fire to celebrate the end of a 10+ year relationship with an ISP that went from really awesome with regards to speed, customer service, etc to total crap.

Does anyone think this kind of "speed" is fair to live with on a daily basis for the last 10 months:
http://www.speedtest.net/result/2177511543.png

No? Thought not.

And with the general view that iBurst deems this as acceptable regardless of my arguments that we would get over 2Mb/s during the day and their inability to see my point of view was the final nail in the coffin.

No amount of arguing, begging, pleading, phone calls, e-mails, etc actually did any good. Yes, I am grateful that Mel organised for the installation of the flat panel antenna (after 3 months of moaning, I might add), but it did little to get our speed back to where it was.

From March 2013, we will spend our hard earned R800 per month on another ISP that gives us 10Mb/s ADSL (not the throttled-to-hell ADSL that iBurst offers, either), and be happy in the fact that we will support an ISP that actually does give a damn about customers.

Sorry iBurst, but after 10+ years, you lose another customer.
 
And still no reply from anyone at iBurst on this forum? No surprise really seeing as I have been waiting for going on 2 months for some mythical consultant from iBurst to contact me.
 
Bursty-dude said:
FFS.......... I honestly wish that someone somewhere at iBurst will get their finger out of their ***, wake up, smell the coffee, sniff the daisy's and do something about pathetic customer service, slow speeds, congested towers, and a whole host of other things.

Clowns.....
Click to expand...

+1

 
2206602637.png


while playing an mmo and streaming a twit video... maybe "you are the only one with this problem" ....ooops that was sentech's pat answer ;)
 
Last edited:
Anybody else having issues in the Durban area? I've had terrible latency since Friday. Iburst has been awesome for me for months now all of a sudden the service is up the pole. Iburst get your act together and fix this crap.
 
Horrible speeds in Alberton as well.

In this speedtest, you can see that the PING is great! I've got 100% signal with barely any FER.

 
 
I have a good mind to take this 2Mb modem, power supply, flat panel antenna, 1Mb modem and power supply and go drop them off at iBurst's head office in Randburg (seeing as I am going to drive right past there tomorrow) and tell them to take these useless items back and take their contract and shove it where the sun does not shine.

Thieves. You take our R800 every month and what do we get in return? Nothing but dial up speeds and no resolution to speed problems which are YOUR problem as you do not upgrade your network to handle the load on towers.
 
They aren't in Randburg anymore, they've moved to Bryanston. Yeah their speeds have gotten atrocious and there is no one responding on the forums anymore.
 
For a couple of weeks now I've been having issues accessing http://penelope.uchicago.edu/Thayer/E/home.html - it's a site containing numerous texts and translations of ancient literature, among other things. Today, the site is definitely up (can be accessed via proxies), but keeps timing out via iBurst. Here's a ping:

Pinging penelope.uchicago.edu [128.135.44.111] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 128.135.44.111:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Click to expand...

and a tracert:

Tracing route to penelope.uchicago.edu [128.135.44.111]
over a maximum of 30 hops:

1 99 ms 49 ms 53 ms wbs-196-2-112-1.wbs.co.za [196.2.112.1]
2 146 ms 55 ms 53 ms iburst-41-213-1-2.iburst.co.za [41.213.1.2]
3 72 ms 49 ms 53 ms 192.168.0.113
4 62 ms 93 ms 55 ms pgw04-int-ge03.jhb.wbs.co.za [41.213.126.25]
5 296 ms 289 ms 319 ms gi9-1.223.mag01.lon02.atlas.cogentco.com [149.6.186.169]
6 352 ms 409 ms 533 ms te7-2.ccr01.lon02.atlas.cogentco.com [130.117.50.138]
7 438 ms 353 ms 405 ms te0-0-0-2.ccr21.lon01.atlas.cogentco.com [130.117.1.157]
8 526 ms 341 ms 489 ms te0-4-0-5.ccr21.lon13.atlas.cogentco.com [154.54.72.186]
9 382 ms 339 ms 345 ms te0-0-0-4.ccr21.bos01.atlas.cogentco.com [154.54.5.161]
10 538 ms 353 ms 359 ms te0-1-0-7.mpd21.ord01.atlas.cogentco.com [154.54.43.177]
11 442 ms 455 ms 359 ms te3-7.mag02.ord01.atlas.cogentco.com [154.54.45.206]
12 448 ms 403 ms 389 ms 38.104.103.10
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.
Click to expand...
 
Psychopompous said:
For a couple of weeks now I've been having issues accessing http://penelope.uchicago.edu/Thayer/E/home.html - it's a site containing numerous texts and translations of ancient literature, among other things. Today, the site is definitely up (can be accessed via proxies), but keeps timing out via iBurst.
Click to expand...
Similar problem on iBurst in Cape Town:
Code: 
$ traceroute penelope.uchicago.edu
traceroute to penelope.uchicago.edu (128.135.44.111), 30 hops max, 60 byte packets
 1  mikrotik (192.168.88.1)  0.395 ms  0.541 ms  0.694 ms
 2  lac3.cpt.wbs.co.za (41.56.220.1)  39.564 ms  44.563 ms  49.599 ms
 3  vl75.cs2.cpt.wbs.co.za (41.56.254.3)  59.462 ms  64.580 ms  64.629 ms
 4  ge0-1.75.cr2.cpt.wbs.co.za (41.56.254.31)  74.529 ms  74.588 ms  84.499 ms
 5  ldn-b4-link.telia.net (80.239.135.233)  259.474 ms  259.576 ms  264.740 ms
 6  level3-ic-143383-ldn-b5.c.telia.net (213.248.96.38)  259.348 ms  259.214 ms level3-ic-153380-ldn-b5.c.telia.net (213.248.91.58)  259.310 ms
 7  ae-52-52.csw2.london1.level3.net (4.69.139.120)  263.733 ms  249.849 ms  229.910 ms
 8  ae-57-222.ebr2.london1.level3.net (4.69.153.133)  249.786 ms ae-58-223.ebr2.london1.level3.net (4.69.153.137)  234.737 ms ae-56-221.ebr2.london1.level3.net (4.69.153.129)  234.735 ms
 9  ae-43-43.ebr1.newyork1.level3.net (4.69.137.74)  289.657 ms  279.790 ms ae-42-42.ebr1.newyork1.level3.net (4.69.137.70)  284.741 ms
10  ae-4-4.ebr1.newyork2.level3.net (4.69.141.18)  284.872 ms  310.651 ms  281.077 ms
11  ae-1-100.ebr2.newyork2.level3.net (4.69.135.254)  305.877 ms  305.602 ms  264.195 ms
12  ae-2-2.ebr1.chicago1.level3.net (4.69.132.65)  289.089 ms  304.031 ms  307.153 ms
13  ae-11-51.car1.chicago1.level3.net (4.69.138.3)  287.091 ms  307.128 ms  307.227 ms
14  * * *
...
30  * * *
Works fine from my connection at work though.
 
Website does not work properly (for months already....), call centre does not answer calls and when by some miracle someone does answer, they know f-all about anything, e-mails do not get answered within a decent time frame, response from anyone regarding continual speed issues is below dismal, the list is endless with this company.

And then we get this:
http://www.speedtest.net/result/2254474713.png

Like I said, thieves.....
 
@Bursty-dude Their coverage map is using the SDK Developer license...makes me think their live server is also their development server!

Note: MapXtreme SDK and deployment licenses are seperate items and must be used together...as in Developer uses SDK to develop and then when deployed on server it uses deployment license.
 
ginggs said:
Similar problem on iBurst in Cape Town:
Code: 
$ traceroute penelope.uchicago.edu
traceroute to penelope.uchicago.edu (128.135.44.111), 30 hops max, 60 byte packets
 1  mikrotik (192.168.88.1)  0.395 ms  0.541 ms  0.694 ms
 2  lac3.cpt.wbs.co.za (41.56.220.1)  39.564 ms  44.563 ms  49.599 ms
 3  vl75.cs2.cpt.wbs.co.za (41.56.254.3)  59.462 ms  64.580 ms  64.629 ms
 4  ge0-1.75.cr2.cpt.wbs.co.za (41.56.254.31)  74.529 ms  74.588 ms  84.499 ms
 5  ldn-b4-link.telia.net (80.239.135.233)  259.474 ms  259.576 ms  264.740 ms
 6  level3-ic-143383-ldn-b5.c.telia.net (213.248.96.38)  259.348 ms  259.214 ms level3-ic-153380-ldn-b5.c.telia.net (213.248.91.58)  259.310 ms
 7  ae-52-52.csw2.london1.level3.net (4.69.139.120)  263.733 ms  249.849 ms  229.910 ms
 8  ae-57-222.ebr2.london1.level3.net (4.69.153.133)  249.786 ms ae-58-223.ebr2.london1.level3.net (4.69.153.137)  234.737 ms ae-56-221.ebr2.london1.level3.net (4.69.153.129)  234.735 ms
 9  ae-43-43.ebr1.newyork1.level3.net (4.69.137.74)  289.657 ms  279.790 ms ae-42-42.ebr1.newyork1.level3.net (4.69.137.70)  284.741 ms
10  ae-4-4.ebr1.newyork2.level3.net (4.69.141.18)  284.872 ms  310.651 ms  281.077 ms
11  ae-1-100.ebr2.newyork2.level3.net (4.69.135.254)  305.877 ms  305.602 ms  264.195 ms
12  ae-2-2.ebr1.chicago1.level3.net (4.69.132.65)  289.089 ms  304.031 ms  307.153 ms
13  ae-11-51.car1.chicago1.level3.net (4.69.138.3)  287.091 ms  307.128 ms  307.227 ms
14  * * *
...
30  * * *
Works fine from my connection at work though.
Click to expand...

Both telia and cogent state that that IP is not being advertized to them. The owner of the IP either has a problem advertizing to tier 1 or has puposely filtered it.
 
r00igev@@r said:
Both telia and cogent state that that IP is not being advertized to them. The owner of the IP either has a problem advertizing to tier 1 or has puposely filtered it.
Click to expand...

Is it possible for iBurst to route traffic to uchicago through TENET?
Code: 
$ traceroute penelope.uchicago.edu
traceroute to penelope.uchicago.edu (128.135.44.111), 30 hops max, 60 byte packets
...
 8  jnb2-t95-bfn1-t200.net.tenet.ac.za (155.232.6.33)  43.168 ms  42.989 ms  43.085 ms
 9  pta1-t42-jnb2-75.net.tenet.ac.za (155.232.6.26)  44.847 ms  44.800 ms  44.819 ms
10  dur1-t100-pta1-t45.net.tenet.ac.za (155.232.6.30)  41.435 ms  41.456 ms  41.445 ms
11  unknown.uni.net.za (155.232.6.102)  43.142 ms  43.092 ms  43.070 ms
12  mtzub1-vl700-mtz1pe1-x001-700.net.tenet.ac.za (155.232.6.85)  43.097 ms  43.090 ms  43.086 ms
13  lnd1-ub-pos400-dur1-pos300.net.tenet.ac.za (196.32.209.45)  214.744 ms  214.777 ms  214.714 ms
14  unknown.uni.net.za (196.32.209.78)  216.351 ms  216.357 ms  216.341 ms
15  ubuntunet.rt1.lon.uk.geant.net (62.40.124.253)  215.038 ms  215.082 ms  215.050 ms
16  as1.rt1.ams.nl.geant2.net (62.40.112.137)  223.396 ms  223.415 ms  223.427 ms
17  so-2-0-0.rt1.fra.de.geant2.net (62.40.112.9)  230.259 ms  229.475 ms  229.695 ms
18  abilene-wash-gw.rt1.fra.de.geant.net (62.40.125.18)  323.471 ms  323.501 ms  323.448 ms
19  xe-1-1-3.10.rtr.chic.net.internet2.edu (64.57.28.50)  340.969 ms  340.443 ms 64.57.28.200 (64.57.28.200)  340.507 ms
20  omnipop-mcleod-10g-local.uchicago.edu (128.135.247.126)  340.191 ms  436.362 ms  436.344 ms
21  * * *
22  penelope.uchicago.edu (128.135.44.111)  341.381 ms  341.414 ms  341.390 ms
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X