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

Bad international tonight; disconnections and slower speeds than usual.
 
Same thing again!
Disconnections, slow surfing and time-outs during night.
Something is wrong... :(
 
Same thing again!
Disconnections, slow surfing and time-outs during night.
Something is wrong... :(

I know services sometimes have problems, but when they do not give feedback or answer something in the lines of "we tested from our side and it seems fine" - after holding for-friggen-ever, THAT is when I start getting really angry.

On a side note, anyone realise that they are using a 'developers license' for their coverage maps? Haha, they even steal from other people!
 
Pretty sad as usual: also steps 3 & 4 are interesting are they not?
@r00igev@@r in the past I asked for a comment - why does iburst use MTN business? see how slow they ALWAYS are


2 68 ms 54 ms 59 ms iburst-41-56-199-1.iburst.co.za [41.56.199.1]
3 83 ms 54 ms 49 ms 192.168.2.3
4 64 ms 49 ms 54 ms 192.168.2.9
5 71 ms 44 ms 110 ms 66.8.22.205
6 68 ms 59 ms 54 ms 196.7.21.22
7 71 ms 54 ms 44 ms 196.7.21.43
8 67 ms 54 ms 54 ms tb-cr-1.za--tb-cr-2.za-a.mtn.net [196.44.31.158]

9 257 ms 273 ms 254 ms lt-cr-1.uk--tb-cr-2-a.uk.mtn.net [196.44.31.213]

10 306 ms 393 ms 340 ms ct-nt-1--rb-nt-1-b.mtnns.net [196.44.31.154]
11 347 ms 265 ms 269 ms ls-pr-1.uk--ls-cr-1.uk-a.mtn.net [209.212.111.83
 
Thanks r00igev@@r, PM'ed

Hi, I haven't received any feedback from my original query and I am still having problems with pages sometimes not loading with error and pages that just keep on loading, never completing.

I sent my UTID number, did any come out of that investigation?

Many Thanks
Nick
 
Hi, I haven't received any feedback from my original query and I am still having problems with pages sometimes not loading with error and pages that just keep on loading, never completing.

I sent my UTID number, did any come out of that investigation?

Many Thanks
Nick

r00igev@@r has been MIA since sunday.
 
Routing going where??

So I went and did a tracert to a European based address:
Tracing route to prs-bb1-link.telia.net [80.91.251.46] over a maximum of 30 hops:
1 104 ms 355 ms 153 ms iburst-41-213-32-1.iburst.co.za [41.213.32.1]
2 58 ms 53 ms 39 ms 192.168.0.97
3 76 ms 39 ms 39 ms 192.168.0.114
4 363 ms 39 ms 49 ms iburst-41-213-126-21.iburst.co.za [41.213.126.21]
5 65 ms 59 ms 53 ms 41.0.4.225
6 362 ms 313 ms 345 ms 41.0.244.5
7 739 ms 600 ms 822 ms ge-9-24.car3.Washington1.Level3.net [4.79.169.229]
8 1039 ms 399 ms 439 ms ae-2-79.edge1.Washington4.Level3.net [4.68.17.82]
9 470 ms 345 ms 319 ms ash-bb1-link.telia.net [213.248.81.117]
10 428 ms 389 ms 365 ms prs-bb1-link.telia.net [80.91.251.46]
Trace complete.​

What stood out most for me (should be bolded), was the words containing WASHINGTON. :confused: :wtf: Is it really the fasters route to Europe? Or is that the name for something in Europe that I missed? Is there something really screwed up with the iBurst routing, or South African routing, that nobody wants to acknowledge? Some feedback from someone in the know would be awesome, because this just cost us another 5 victories in the WoW arenas! :mad:

Btw, I did a reverse trace from that server using http://lg.telia.net
I used the address from step 6 above, and selected the Paris node. These were the results. Note that there was NO mention of Washington.

Router: Paris
Command: traceroute 41.0.244.5 as-number-lookup
traceroute to 41.0.244.5 (41.0.244.5), 30 hops max, 40 byte packets
1 prs-bb2-link.telia.net (80.91.251.44) 0.503 ms prs-bb1-link.telia.net (80.91.251.46) 0.768 ms prs-bb1-link.telia.net (80.91.251.113) 0.801 ms
2 ldn-bb2-link.telia.net (80.91.247.241) 7.572 ms ldn-bb1-link.telia.net (80.91.247.7) 8.270 ms ldn-bb2-link.telia.net (80.91.247.241) 7.543 ms
3 ldn-b5-link.telia.net (80.91.248.216) 8.436 ms ldn-b5-link.telia.net (80.91.246.147) 7.492 ms 7.543 ms
4 ldn-tch-i1-link.telia.net (80.91.250.210) 8.606 ms 90.339 ms 9.184 ms
5 telkomsa-ic-134482-ldn-tch-i1.c.telia.net (213.155.141.154) 7.738 ms 7.691 ms 8.030 ms
6 tpr-ip-esr-6-gig-6-1-0.telkom-ipnet.co.za (196.43.51.82) [AS 5713] 191.173 ms 191.339 ms 197.832 ms
7 vodacom-gw.telkom-ipnet.co.za (196.25.10.70) [AS 5713] 270.043 ms 263.022 ms 265.386 ms
8 41.0.160.10 (41.0.160.10) [AS 36994] 257.352 ms 258.764 ms 263.694 ms
MPLS Label=410 CoS=3 TTL=1 S=1
9 * * *
10 * * *
11 * * *
12 41.0.244.5 (41.0.244.5) [AS 36994] 262.666 ms 262.657 ms *​

Regards
 
Small update regarding routing. It seems more than one ISP has this issue. From the office it is also routed through US first. Then again, my friend is on yet another ISP and his routing is fine. :confused:
 
Severe Degradation in Service in Cape Town

Please note we are experiencing connectivity issues in the Cape Town region. The engineers from our upstream provider are currently working to resolve this.

We sincerely apologizes for any inconvenience caused at this time.
 
I don't know what iBurst has done lately, but latency and speed is so much better now...:)

Midrand:

New York:
 
Wow, so I guess I just joined the orange/yellow light (signal from 90% to 5%) and insanely useless service club....
 
Wow, so I guess I just joined the orange/yellow light (signal from 90% to 5%) and insanely useless service club....
Before someone points out that you're in the insanely useless post club, please update your location.
 
My routing still going through Washington to get to Europe.
iBurst response: "Please kindly contact Vodacom on 082155 for assistance in regards to your query."
So even though iBurst are my service provider I have to call someone else to figure out what is wrong with their stuff. Meanwhile I play WoW flawlessly on a simple 384 ADSL line. Guess I'm going back to fixed line ADSL permanently. Oh well.
 
My routing still going through Washington to get to Europe.
iBurst response: "Please kindly contact Vodacom on 082155 for assistance in regards to your query."
So even though iBurst are my service provider I have to call someone else to figure out what is wrong with their stuff. Meanwhile I play WoW flawlessly on a simple 384 ADSL line. Guess I'm going back to fixed line ADSL permanently. Oh well.

Please PM me your ticket reference and I'll have it escalated.
 
Top
Sign up to the MyBroadband newsletter
X