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

Been trying to download a 3.2 GB file for a MMO the last 2 days. I got to 1.4 GB today and i got disconnected again. 1.4 GB gone with nothing to show for it. My download speed at most was 35kB/sec.

Dunno what i am gonna do. Telkom lines don't work here and 3G is to expensive.
 
Been trying to download a 3.2 GB file for a MMO the last 2 days. I got to 1.4 GB today and i got disconnected again. 1.4 GB gone with nothing to show for it. My download speed at most was 35kB/sec.

Dunno what i am gonna do. Telkom lines don't work here and 3G is to expensive.
You need a download manager, for any internet connection, unless it's 20Mbps uncapped FTTH.
 
Downloaded Adobe CS6 Master Collection from Adobe's website (bought the program, not a torrent from some torrent site that is throttled), program size: 6352Mb, time taken: 7 days, 11 hours, 23 minutes.

Yes, more than 7 freaking days to download a 6.2Gb program for work purposes is simply pathetic....
Another friend downloaded the same program from the same site using his Telkom line and took less than one day to download.

Yay for iBurst download speeds. NOT!
 
really crappy speeds :(

Local
Test conducted on 22 May 2012 08:45:40 PM
Download Speed: 365 kbps (45.6 KB/sec transfer rate)
Upload Speed: 289 kbps (36.1 KB/sec transfer rate)
Latency: 248 ms

International
Test conducted on 22 May 2012 08:47:07 PM
Download Speed: 160 kbps (20 KB/sec transfer rate)
Upload Speed: 127 kbps (15.9 KB/sec transfer rate)
Latency: 758 ms
 
I have come to the conclusion that moaning about download speeds and connectivity issues here in this thread is as pointless as watching grass grow.........

Just when you think you saw that one blade of grass grow in length by a Micron, you realise it was just you mind screwing with you.
 
Interesting. iBurst seem to be doing something to their backend...

Code:
Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:

  1   125 ms   200 ms   153 ms  lac4.jhb.wbs.co.za [41.208.192.1]
  2    57 ms    42 ms    96 ms  192.168.0.97
  3    72 ms   102 ms    76 ms  192.168.0.113
  4    51 ms    46 ms    53 ms  pgw01-ge01.jhb.wbs.co.za [41.213.126.19]
  5   234 ms    54 ms    56 ms  ge2-24.gw14.jnb6.za.mtnbusiness.net [66.8.42.21]
  6    89 ms    79 ms   171 ms  [b]74.125.49.218[/b]
  7   269 ms   275 ms   254 ms  209.85.248.215
  8   369 ms   267 ms   534 ms  209.85.252.44
  9   314 ms   348 ms   258 ms  209.85.253.92
 10   264 ms   343 ms   306 ms  209.85.243.33
 11   289 ms   270 ms   259 ms  216.239.49.28
 12   305 ms   415 ms   445 ms  209.85.255.126
 13   343 ms     *      433 ms  google-public-dns-a.google.com [8.8.8.8]

Definitely.

Compare my traceroute from May 16:
International working again:
Code:
$ traceroute 8.8.8.8
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
 1  mikrotik (192.168.88.1)  0.562 ms  0.724 ms  0.868 ms
 2  iburst-41-56-212-1.iburst.co.za (41.56.212.1)  74.147 ms  76.789 ms  76.882 ms
 3  iburst-41-56-254-3.iburst.co.za (41.56.254.3)  84.019 ms  108.940 ms  109.024 ms
 4  iburst-41-56-254-30.iburst.co.za (41.56.254.30)  113.965 ms  114.066 ms  139.132 ms
 5  [b]google.cinx.net.za[/b] (196.223.22.41)  139.007 ms  139.183 ms  139.274 ms
 6  209.85.248.215 (209.85.248.215)  354.231 ms  351.468 ms  358.413 ms
 7  209.85.252.44 (209.85.252.44)  358.572 ms  243.534 ms  238.170 ms
 8  209.85.253.92 (209.85.253.92)  248.333 ms  253.280 ms  258.277 ms
 9  209.85.243.33 (209.85.243.33)  263.319 ms  268.290 ms  273.285 ms
10  216.239.49.28 (216.239.49.28)  278.171 ms  283.126 ms  403.243 ms
11  * 209.85.255.126 (209.85.255.126)  343.544 ms 209.85.255.118 (209.85.255.118)  675.398 ms
12  google-public-dns-a.google.com (8.8.8.8)  675.428 ms  745.256 ms  745.243 ms

..to one done this morning:
Code:
$ traceroute 8.8.8.8
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
 1  mikrotik (192.168.88.1)  0.597 ms  0.718 ms  0.856 ms
 2  iburst-41-56-212-1.iburst.co.za (41.56.212.1)  44.643 ms  49.685 ms  59.642 ms
 3  iburst-41-56-254-3.iburst.co.za (41.56.254.3)  64.564 ms  64.635 ms  69.540 ms
 4  iburst-41-56-254-31.iburst.co.za (41.56.254.31)  79.617 ms  84.491 ms  89.509 ms
 5  fe11-0-0.gw1.cpt1.za.mtnbusiness.net (66.8.33.45)  114.487 ms  114.743 ms  119.482 ms
 6  196.44.0.74 (196.44.0.74)  104.344 ms  98.958 ms  108.704 ms
 7  [b]74.125.49.218[/b] (74.125.49.218)  133.886 ms  87.529 ms  87.522 ms
 8  209.85.248.215 (209.85.248.215)  299.275 ms  294.437 ms  349.423 ms
 9  209.85.252.44 (209.85.252.44)  369.195 ms  354.148 ms  354.136 ms
10  209.85.253.196 (209.85.253.196)  349.436 ms  334.679 ms 209.85.253.92 (209.85.253.92)  349.222 ms
11  209.85.240.28 (209.85.240.28)  354.398 ms  348.538 ms 209.85.243.33 (209.85.243.33)  300.355 ms
12  216.239.49.28 (216.239.49.28)  304.754 ms 216.239.49.36 (216.239.49.36)  275.115 ms  274.801 ms
13  * 209.85.255.118 (209.85.255.118)  279.522 ms 209.85.255.126 (209.85.255.126)  299.604 ms
14  google-public-dns-a.google.com (8.8.8.8)  299.706 ms  299.750 ms  304.404 ms
 
How about bbc.com?

Definitely.

Compare my traceroute from May 16:


..to one done this morning:
Code:
$ traceroute 8.8.8.8
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
 1  mikrotik (192.168.88.1)  0.597 ms  0.718 ms  0.856 ms
 2  iburst-41-56-212-1.iburst.co.za (41.56.212.1)  44.643 ms  49.685 ms  59.642 ms
 3  iburst-41-56-254-3.iburst.co.za (41.56.254.3)  64.564 ms  64.635 ms  69.540 ms
 4  iburst-41-56-254-31.iburst.co.za (41.56.254.31)  79.617 ms  84.491 ms  89.509 ms
 5  fe11-0-0.gw1.cpt1.za.mtnbusiness.net (66.8.33.45)  114.487 ms  114.743 ms  119.482 ms
 6  196.44.0.74 (196.44.0.74)  104.344 ms  98.958 ms  108.704 ms
 7  [b]74.125.49.218[/b] (74.125.49.218)  133.886 ms  87.529 ms  87.522 ms
 8  209.85.248.215 (209.85.248.215)  299.275 ms  294.437 ms  349.423 ms
 9  209.85.252.44 (209.85.252.44)  369.195 ms  354.148 ms  354.136 ms
10  209.85.253.196 (209.85.253.196)  349.436 ms  334.679 ms 209.85.253.92 (209.85.253.92)  349.222 ms
11  209.85.240.28 (209.85.240.28)  354.398 ms  348.538 ms 209.85.243.33 (209.85.243.33)  300.355 ms
12  216.239.49.28 (216.239.49.28)  304.754 ms 216.239.49.36 (216.239.49.36)  275.115 ms  274.801 ms
13  * 209.85.255.118 (209.85.255.118)  279.522 ms 209.85.255.126 (209.85.255.126)  299.604 ms
14  google-public-dns-a.google.com (8.8.8.8)  299.706 ms  299.750 ms  304.404 ms
 
How about bbc.com?
Code:
$ traceroute bbc.com
traceroute to bbc.com (212.58.241.131), 30 hops max, 60 byte packets
 1  mikrotik (192.168.88.1)  0.485 ms  0.654 ms  0.802 ms
 2  iburst-41-56-212-1.iburst.co.za (41.56.212.1)  32.941 ms  42.913 ms  47.939 ms
 3  iburst-41-56-254-2.iburst.co.za (41.56.254.2)  52.878 ms  57.750 ms  62.755 ms
 4  iburst-41-56-254-31.iburst.co.za (41.56.254.31)  67.781 ms  72.739 ms  82.695 ms
 5  ldn-b4-link.telia.net (80.239.135.233)  232.933 ms  237.831 ms  237.906 ms
 6  ldn-bb2-link.telia.net (80.91.249.133)  242.832 ms  241.860 ms  261.850 ms
 7  ldn-b3-link.telia.net (213.155.133.31)  266.882 ms  187.920 ms ldn-b3-link.telia.net (80.91.247.88)  187.891 ms
 8  siemens-ic-119241-ldn-b2.c.telia.net (213.248.104.70)  197.755 ms  202.695 ms  207.704 ms
 9  * * *
10  ae1.er01.thdow.bbc.co.uk (132.185.254.18)  318.510 ms  300.787 ms  239.926 ms
11  132.185.255.130 (132.185.255.130)  239.813 ms  239.973 ms  244.565 ms
12  212.58.241.131 (212.58.241.131)  249.569 ms  249.637 ms  280.348 ms
What does it look like from Jozi?
 
C:\Users\Johan>tracert bbc.com

Tracing route to bbc.com [212.58.241.131]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 67 ms 46 ms 179 ms lac4.jhb.wbs.co.za [41.208.192.1]
3 68 ms 47 ms 49 ms 192.168.0.97
4 172 ms 44 ms 99 ms 192.168.0.113
5 368 ms 174 ms 44 ms pgw02-int-ge03.jhb.wbs.co.za [41.213.126.21]
6 383 ms 529 ms 269 ms ldn-b4-link.telia.net [213.248.95.177]
7 393 ms 300 ms 288 ms ldn-bb2-link.telia.net [80.91.249.133]
8 267 ms 283 ms 295 ms ldn-b3-link.telia.net [80.91.254.17]
9 350 ms 250 ms 273 ms siemens-ic-119241-ldn-b2.c.telia.net [213.248.10
4.70]
10 * * * Request timed out.
11 395 ms 427 ms 362 ms ae1.er01.thdow.bbc.co.uk [132.185.254.18]
12 350 ms 219 ms 489 ms 132.185.255.130
13 227 ms 264 ms 224 ms 212.58.241.131

Trace complete.
 
Any network issues on the go in the Durban area? I have been experiencing really poor speeds in the last 24 hours or so, simple web browsing has even become a painful exercise.
 
Any network issues on the go in the Durban area? I have been experiencing really poor speeds in the last 24 hours or so, simple web browsing has even become a painful exercise.

Hard to believe that our already dodgy connection has also worsened since yesterday morning...:sick:
 
iburst & durban

for nearly a week now, iburst has not been loading pages well.
the loading is very slow, some pages won't load at all.
is there a server problem that is affecting my area?
 
Is there anything wrong with the network

Just need to know if there's anything wrong with the network, I run a custom minecraft gaming server in France and since yesterday I just can't connect to the server at all I connect but the latency is so bad that I get chucked out couple seconds later, previously been able to connect to the server and play on it with almost zero problems except during peak times, so whats happening currently just doesn't make any sense at all, does anybody know why this might be happening.
 
Past three nights have been appalling for me, internationally. Local not too bad.

Im having horible speeds during the day, yesterday kept disconecting (unable to make pppoe conction errors) goes up for a few minutes then down again, and now again wife says internet is down again then after a while reconects. but after midnight dont think anything got disconetced as downloads went by fine
After hours (0000 - 0800) its OK checked my bandwitdh monitor records and i prety much get full speeds most of the time (more or less 2Mbps) so realy great, but i cant surf properly the rest of the time, geting speeds less then 200Kbps .

Cmon Iburst whats hapening?
Why are you throtaling trafic so much during peak hours, I mean i would be happy if i get at least 1Mb conection speed on my 2Mb modem during the day, but 200Kbp is ridiculous
 
Well think my problems have come to and end with iburst finally after years of waiting patiently for them to wake up the last two days of international speeds has eventually forced me to order Telkom ADSL and rather pay the phone rental and get ADSL uncapped, was expecting a 2 week telkom installation delay but will only take 2 days for them to install a new line and sort me out.
 
Top
Sign up to the MyBroadband newsletter
X