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

Hello - the guy in the top hat texted me to answer, even though I am now bubbleless (get it - babbelas). Ok moving along.

The network has some AAA proxies which are configured to operate in a mode that facilitates connectivity even when the OSS is offline. This is called blind AUTH. To prevent someone being blind AUTH'd and then remaining connected for a few months without being billed, the blind AUTH has a time to live of two hours.

Firstly check if you have session reports on the website. If you do not have session reports then the OSS has had an accident. Moenie worry nie, bly dan stil. If you have session reports then there is an issue between the proxies and OSS.

Firstly start with a wireshark capture on the proxy and post the file here.
 
Problems in Paarl area?

Connection is very slow. I was trying to download the desktop software and driver so I can test signal strength but the iburst website is not available.

I phoned technical support but like always they're no help.
 
Hi Kaaskop

There was an issue with Paarl has been resolved in the last 10 minutes.
The issue with our website should be resolved in the next hour.
 
iBurst said:
Hi Kaaskop

There was an issue with Paarl has been resolved in the last 10 minutes.
The issue with our website should be resolved in the next hour.
Click to expand...

Thank you for the feedback.

What I don't understand is why I can get network updates from Bubbles™ and the technical support call centre got no idea if something is wrong.

At least I can get some answers on the forum.
 
Faerie glen, Pretoria area. Looks like that tower is not working since loadshedding last night.
 
Looks like international traffic is dead in cape town.

bianca@bianca-PC:~$ traceroute facebook.com
traceroute to facebook.com (173.252.120.6), 64 hops max, 52 byte packets
1 router (192.168.1.1) 1.058 ms 0.758 ms 0.708 ms
2 lac1.cpt.wbs.co.za (41.56.212.1) 54.915 ms 44.399 ms 45.081 ms
3 vl75.cs2.cpt.wbs.co.za (41.56.254.3) 44.930 ms 43.802 ms 40.158 ms
4 ge0-1.75.cr2.cpt.wbs.co.za (41.56.254.31) 44.720 ms 44.411 ms 39.902 ms
5 * * *
 
B.K said:
Looks like international traffic is dead in cape town.

bianca@bianca-PC:~$ traceroute facebook.com
traceroute to facebook.com (173.252.120.6), 64 hops max, 52 byte packets
1 router (192.168.1.1) 1.058 ms 0.758 ms 0.708 ms
2 lac1.cpt.wbs.co.za (41.56.212.1) 54.915 ms 44.399 ms 45.081 ms
3 vl75.cs2.cpt.wbs.co.za (41.56.254.3) 44.930 ms 43.802 ms 40.158 ms
4 ge0-1.75.cr2.cpt.wbs.co.za (41.56.254.31) 44.720 ms 44.411 ms 39.902 ms
5 * * *
Click to expand...

Agreed. Experiencing the same here.
 
B.K said:
Looks like international traffic is dead in cape town.

bianca@bianca-PC:~$ traceroute facebook.com
traceroute to facebook.com (173.252.120.6), 64 hops max, 52 byte packets
1 router (192.168.1.1) 1.058 ms 0.758 ms 0.708 ms
2 lac1.cpt.wbs.co.za (41.56.212.1) 54.915 ms 44.399 ms 45.081 ms
3 vl75.cs2.cpt.wbs.co.za (41.56.254.3) 44.930 ms 43.802 ms 40.158 ms
4 ge0-1.75.cr2.cpt.wbs.co.za (41.56.254.31) 44.720 ms 44.411 ms 39.902 ms
5 * * *
Click to expand...
`

Highly frustrating because I am 2.4 GB into a 2.8 GB international download which is currently stuck...

Still not connecting

tracert facebook.com

Tracing route to facebook.com [173.252.120.6]
over a maximum of 30 hops:

1 55 ms 39 ms 39 ms lac3.cpt.wbs.co.za [41.56.220.1]
2 54 ms 43 ms 45 ms vl75.cs2.cpt.wbs.co.za [41.56.254.3]
3 54 ms 45 ms 43 ms ge0-1.75.cr2.cpt.wbs.co.za [41.56.254.31]
4 * * * Request timed out.
 
Last edited:
So iburst is still down... and to think I got a call from them on Saturday asking if I wanted to change my month-to-month to a two year contract... I just laughed at the guy.
 
All data services in Cape Town critically impacted due to fiber damage at data center infrastructure. Cabling operators attending. ETR: 14:00
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X