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

I noticed that, my Wimax connection died during the storm but my iBurst was still going strong :P
 
Im having problems with my online gaming especially World of warcraft. At random times when the game uses more bandwidth I get huge latency, it jumps from 600ms to 19000ms latency. I have heard that wow uses a new tipe of data that can be sometimes picked up as torrent traffic through the servers and then shapped. Can someone please look into this for me?
 
tp3to Apparently IBurst is changing upstream provider sometime in the near future and this should resolve or better us poor wow addicts position. Keep your eyes open for any news :)
 
tp3to Apparently IBurst is changing upstream provider sometime in the near future and this should resolve or better us poor wow addicts position. Keep your eyes open for any news :)

Alas, too late for me.
 
A m8 told me this when I logged in last night on WoW I have been unable to play WoW on IBurst for the last 2 months so Im hoping for some resolution otherwise will have to jump ship which makes me slightly sad.
 
jip same. my contract ending in Desember.

But the stange thing is, is that my friend that uses openweb has the same problem. Maybe something with seacom?
 
jip same. my contract ending in Desember.

But the stange thing is, is that my friend that uses openweb has the same problem. Maybe something with seacom?

Also known as "bottleneck", when lagging starts at international level, that's what happens in my case.
 
This is my tracert, doesnt look good, Seems like Im router through washington to get to europe?

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Dviance>tracert 80.239.233.42

Tracing route to 80-239-233-42.customer.teliacarrier.com [80.239.233.42]
over a maximum of 30 hops:

1 82 ms 44 ms 47 ms wbs-196-2-100-1.wbs.co.za [196.2.100.1]
2 81 ms 44 ms 39 ms 192.168.0.97
3 72 ms 44 ms 49 ms 192.168.0.113
4 78 ms 44 ms 44 ms iburst-41-213-126-21.iburst.co.za [41.213.126.21
]
5 78 ms 44 ms 179 ms 41.0.4.225
6 348 ms 299 ms 314 ms 41.0.244.5
7 378 ms 330 ms 313 ms ge-9-24.car3.Washington1.Level3.net [4.79.169.22
9]
8 312 ms 320 ms 308 ms ae-4-99.edge1.Washington4.Level3.net [4.68.17.21
0]
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 *


Tracert is done to my wow Europe server IP address
 
Weather causing some issues in northen Johannesburg.

Of course. But then how the weather didn't cause any issues with my brand new Cell C 3G connection? It was only affecting my iBurst. Guess the technology used by iBurst then is the problem, not the weather.
 
ok seems like I found the problem with the huge latency.

my tracert to the server I play on routed me through Washington, Im not the only person who get this as many other people using iburst also is getting routed through Washington and causes wow to be unplayable.

My tracert to eu.battle.net (wow's website) showed this.

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Dviance>tracert eu.battle.net

Tracing route to eu.battle.net [80.239.186.40]
over a maximum of 30 hops:

1 50 ms 44 ms 44 ms wbs-196-2-100-1.wbs.co.za [196.2.100.1]
2 59 ms 44 ms 163 ms 192.168.0.97
3 42 ms 44 ms 44 ms 192.168.0.114
4 43 ms 199 ms 44 ms iburst-41-213-126-21.iburst.co.za [41.213.126.21
]
5 58 ms 44 ms 44 ms 41.0.4.225
6 328 ms 329 ms 355 ms 41.0.244.5
7 339 ms 324 ms 404 ms ge-9-24.car3.Washington1.Level3.net [4.79.169.22
9]
8 327 ms 314 ms 305 ms ae-2-79.edge1.Washington4.Level3.net [4.68.17.82
]
9 354 ms 310 ms 348 ms ash-bb1-link.telia.net [213.248.81.117]
10 392 ms 334 ms 334 ms prs-bb2-link.telia.net [80.91.254.215]
11 368 ms 339 ms 330 ms prs-b7-link.telia.net [80.91.253.110]
12 364 ms 344 ms 334 ms prs-sdix-i2-link.telia.net [80.91.253.78]
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 *




So this leads me to believe that all battle.net games gets routed through Washington, why iburst why??

This means that the traffic has got to go to usa and then to europe and back. wth?:mad:
 
I have proof!!

First tracert is of a friend of mien thats using Afrihost ISP


C:\Users\JC>tracert 80.239.233.42

Tracing route to 80-239-233-42.customer.teliacarrier.com [80.239.233.42]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms login.router [10.0.0.2]
2 8 ms 8 ms 7 ms dsl-145-0-01.telkomadsl.co.za [41.145.0.1]
3 39 ms 38 ms 38 ms cdsl1-rba-vl2253.ip.isnet.net [196.38.73.181]
4 41 ms 38 ms 40 ms cdsl1-rba-vl150.ip.isnet.net [196.38.73.17]
5 38 ms 39 ms 38 ms core1b-rba-te2-0-0.ip.isnet.net [196.26.0.181]
6 316 ms 318 ms 317 ms mi-za-rba-p5-gi2-0-0-301.ip.isnet.net [168.209.1
64.148]
7 317 ms 318 ms 316 ms 168.209.161.22
8 324 ms 323 ms 324 ms core1a-ny-gi1-0-0-301.ip.isnet.net [168.209.164.
100]
9 323 ms 322 ms 325 ms 168.209.244.3
10 323 ms 323 ms 323 ms xe-6-1.r02.nycmny03.us.bb.gin.ntt.net [129.250.1
93.253]
11 325 ms * 323 ms xe-8-4.r03.nycmny01.us.bb.gin.ntt.net [129.250.2
.46]
12 * * * Request timed out.
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 * *




Second tracert is through Vodacom 3G

Tracing route to gw.ptr-80-238-233-42.customer.ch.netstream.com [80.238.233.42]
over a maximum of 30 hops:

1 395 ms 709 ms 399 ms 10.17.10.139
2 * * * Request timed out.
3 692 ms 741 ms 397 ms vc-196-207-33-2.3g.vodacom.co.za [196.207.33.2]

4 386 ms 359 ms 359 ms 192.168.107.22
5 308 ms 329 ms 380 ms 41.0.164.1
6 899 ms 549 ms 480 ms 41.0.246.5
7 439 ms 508 ms 539 ms ge-6-4-581.car5.London1.Level3.net [217.163.45.1
37]
8 438 ms 480 ms 618 ms ae-34-52.ebr2.London1.Level3.net [4.69.139.97]
9 497 ms 639 ms 528 ms ae-24-24.ebr2.Frankfurt1.Level3.net [4.69.148.19
8]
10 587 ms 460 ms 559 ms ae-7-7.car2.Zurich1.Level3.net [4.69.133.238]
11 768 ms 530 ms 558 ms ae-11-11.car1.Zurich1.Level3.net [4.69.133.233]

12 * * 492 ms NETSTREAM-A.car1.Zurich1.Level3.net [213.242.67.
30]
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.


all of them are not getting routed through Washington.
 
I believe its their upstream Vodacom Business who go through US to Europe.
 
Of course. But then how the weather didn't cause any issues with my brand new Cell C 3G connection? It was only affecting my iBurst. Guess the technology used by iBurst then is the problem, not the weather.

You playing online with your CellC?
 
You playing online with your CellC?

Not playing games. Just testing it at the moment. With very weak Cell C signal at my place (I'm on the edge of the coverage area) I get stable 1.5Mbps and pings at about 53ms. And the weather doesn't seem to affect it.
 
Of course. But then how the weather didn't cause any issues with my brand new Cell C 3G connection? It was only affecting my iBurst. Guess the technology used by iBurst then is the problem, not the weather.

The weather affects the microwave backhaul links and not the iBurst signal. Each tower has a redunadant microwave so weather may cause an intermittent issue depending how the storm is moving and its strength.
 
The weather affects the microwave backhaul links and not the iBurst signal. Each tower has a redunadant microwave so weather may cause an intermittent issue depending how the storm is moving and its strength.

And the 3G towers don't use microwave backhaul links?
 
Not playing games. Just testing it at the moment. With very weak Cell C signal at my place (I'm on the edge of the coverage area) I get stable 1.5Mbps and pings at about 53ms. And the weather doesn't seem to affect it.

Well, that is already better than what I get with Iburst, when it is working. Where do you stay?
 
Top
Sign up to the MyBroadband newsletter
X