Browsing issues?

No change no, Guys at Airport still can't browse (last checked at 9:00pm)


None of the application can connect either, MSN, Mirc, Teamspeak, Skype. Almost no connectivity.

Problem is prolly something minor ;)
 
I have been having problems accesing www.fnb.co.za for the last 2 weeks.
Intermittently

Also I believe iBurst has over sold the towers in my area badly.
In 2005 when I got iBurst I installed an external antenna , I have a very good signal.
I used to get 800 kb/s - 900kb/s
Now I am lucky if I get 400kb/s
Of course I'm still paying the every month that hasn't changed, only the service from their side.
They have me by the balls, cos I don't have any other option.
 
Agreed, iBurst has been useless for me for the last few days. The DNS resolves (not through iBursts DNS) and then sits.... and sits.... and sits....

Route the connections through a squid proxy on my web servers in germany and poooooof... suddenly everything is working again. It's annoying since I have to update the ACL to allow the IP and iBurst also dumps IPs pretty often.

It's not limited to local or international sites, it's any site.

Oh, and of course I have a directional like almost everyone here.

iBurst iBurst iBurst... why does it need to be this difficult & frustrating every few weeks?
 
Hi guys


Please provide me with detail of which site you are opening etc.

This I will pass onto networks.

Currently there are no outstanding issues in Cape Town according to the status screens.

Let me know.


cheers

Shaun
 
I continue to get more than 250-300 ms than normal on Ventrillo, TS and WoW since last night, I cant do much like this.

Update @ 16:48, latency seems much better now after I reset modem and reconnected and its what I am use too since I been with iBurst :). Dont know if something was change in the rerouting at iBurst at 16:30 but it helped.

Seems I got same issues now accessing www.fnb.co.za

Tracert below, hope it helps:

Tracing route to www.fnb.co.za [196.11.125.149]
over a maximum of 30 hops:

1 70 ms 46 ms 46 ms wbs-41-208-200-1.wbs.co.za [41.208.200.1]
2 62 ms 46 ms 46 ms 192.168.0.97
3 * * * Request timed out.
4 62 ms 62 ms 46 ms ge2-24.gw14.jnb6.za.mtnbusiness.net [66.8.42.21]

5 * * * Request timed out.
6 * * * Request timed out.
7 * *
 
Last edited:
Tracing route to www.cnn.com [157.166.255.19]
over a maximum of 30 hops:

1 45 ms 49 ms 45 ms wbs-196-2-100-1.wbs.co.za [196.2.100.1]
2 59 ms 45 ms 39 ms 192.168.0.97
3 * * * Request timed out.
4 292 ms 274 ms 259 ms rndf-ip-ll-1-wan.telkom-ipnet.co.za [196.25.200.
97]
5 742 ms 782 ms 623 ms lon-ip-dir-telecity-gig-4-0-1025.telkom-ipnet.co
.za [196.43.18.121]
6 612 ms 593 ms 629 ms ge-6-2-903.car5.London1.Level3.net [212.113.10.6
9]
7 605 ms 603 ms 606 ms ae-34-52.ebr2.London1.Level3.net [4.69.139.97]
8 695 ms


Absolutely ridiculous ping time here via telkom-ipnet.co.za at 17:58



Tracing route to www.cnn.com [157.166.226.25]
ver a maximum of 30 hops:

1 49 ms 43 ms 59 ms wbs-41-208-200-1.wbs.co.za [41.208.200.1]
2 392 ms 436 ms 323 ms 192.168.0.97
3 * * * Request timed out.
4 65 ms 44 ms 45 ms ge2-24.gw14.jnb6.za.mtnbusiness.net [66.8.42.21]

5 64 ms 49 ms 140 ms 196.30.1.7
6 299 ms * 283 ms so0-2-0.cr1.lnd19.za.mtnbusiness.net [196.30.229
169]
7 273 ms 243 ms * ge7-0-1.ir1.lnd19.za.mtnbusiness.net [196.30.229
201]
8 * 280 ms 247 ms so1-0-3.ir1.par6.za.mtnbusiness.net [196.30.229.
78]
9 452 ms 340 ms 319 ms 0.so-3-1-0.IH1.NYC1.ALTER.NET [152.63.16.109]
10 * 394 ms 322 ms 500.at-2-2-0.XR2.NYC1.ALTER.NET [152.63.19.94]
11 336 ms 310 ms 319 ms 0.so-1-1-0.XL2.NYC1.ALTER.NET [152.63.19.98]
12 344 ms 303 ms 295 ms 0.so-7-3-0.XL4.NYC4.ALTER.NET [152.63.17.2]
13 304 ms 299 ms 302 ms 0.ge-2-3-0.BR3.NYC4.ALTER.NET [152.63.3.134]
14 366 ms 346 ms 316 ms xe-10-2-0.edge2.NewYork2.level3.net [4.68.110.23
]
15 300 ms 308 ms * vlan51.ebr1.NewYork2.Level3.net [4.69.138.222]
16 * 348 ms 363 ms ae-3-3.ebr2.Washington1.Level3.net [4.69.132.89]

17 362 ms 335 ms 360 ms ae-92-92.csw4.Washington1.Level3.net [4.69.134.1
8]
18 376 ms 345 ms 356 ms ae-91-91.ebr1.Washington1.Level3.net [4.69.134.1
1]
19 369 ms * 366 ms ae-2.ebr3.Atlanta2.Level3.net [4.69.132.85]
20 373 ms 352 ms * ae-2-52.edge4.Atlanta2.Level3.net [4.68.103.46]

21 * * * Request timed out.


Much better ping time via mtnbusiness.net

Dont know what going on with telkom-ipnet.co.za
 
Last edited:
Telkom having severe issues with most of Cape Town not having internet for several hours today and iBurst connectivity is getting worse by the day!
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X