Status
Not open for further replies.
By the way @DJ... Do you know what company uses orange and purple fibre pipe?

Even though Telkom confirmed with me that my area wasn't getting fibre, for the past 2 weeks people have been digging up the sides of the roads and laying this pipe, sometimes purple sometimes orange and I have confirmed it is for holding fibre.

In shared trenches, yes there has been a tendency to "colour code" the duct bundles. Started in Cape Town, which I think was the first municipal authority to insist that the operators all got together to dig up the roads once and lay their ducts in the same excavations. The other project was long distance co-operative project between the non Telkom operators when the new fibre route between Cape Town and JHB was undertaken. There, the ducts were colour coded, with Orange being the colour for Neotel?
 
In shared trenches, yes there has been a tendency to "colour code" the duct bundles. Started in Cape Town, which I think was the first municipal authority to insist that the operators all got together to dig up the roads once and lay their ducts in the same excavations. The other project was long distance co-operative project between the non Telkom operators when the new fibre route between Cape Town and JHB was undertaken. There, the ducts were colour coded, with Orange being the colour for Neotel?

damned hippies...
 
The gaming latencies have been terrible - the suggestion to use tunnelbear worked a treat - thank you.


Hoping they can sort it out quickly.
 
The gaming latencies have been terrible - the suggestion to use tunnelbear worked a treat - thank you.


Hoping they can sort it out quickly.

Unfortunately this is for Blizzard and their network partners to sort out. It's not something happening on our network causing it...
 
Unfortunately this is for Blizzard and their network partners to sort out. It's not something happening on our network causing it...

This is probably the wrong place to ask, however does anyone have any insight in to configuring an AWS VPN that actually works with Battle.net and Overwatch?

Figuring that Blizzard is using AWS (Frankfurt) to host Overwatch, setting up a VPN there might just be the best thing. I have opened up the ports found on Blizzard's site, and while I have had some traffic routing through my VPN successfully (it downloads the content in the launcher and even lets me update!), I just cannot get it to login (on both the launcher and Overwatch launched without the launcher).

My googlefu has failed me so far. =(
 
Blizzard has now responded here: http://eu.battle.net/wow/en/forum/topic/17611871728?page=2#23
He's basically saying it's not their problem, we have to contact our ISP's to sort it out :( I don't know what to do anymore.

I feel for them. But the routing happens from another network provider entirely. That network provider has acknowledged an issue with their routing due to a problem with one of their links. I read the response from the employee and he says the jump is before it leaves South Africa but then says he acknowledges that it goes to the UK and US which the IPs quite clearly show (so he appears a bit confused). It lands in the UK as it normally should so no issues there. Once it moves over to the peering network as per their routing tables for their traffic, it all of a sudden hops to USA and then back again. So, he has not explained that correctly and has therefore given you some very poor advice.

However, I will discuss this with netops once again...
 
Last edited:
I feel for them. But the routing happens from another network provider entirely. That network provider has acknowledged an issue with their routing due to a problem with one of their links. I read the response from the employee and he says the jump is before it leaves South Africa but then says he acknowledges that it goes to the UK and US which the IPs quite clearly show. It lands in the UK as it normally should so no issues there. Once it moves over to the peering network as per their routing tables for their traffic, it all of a sudden hops to USA and then back again. So, he has not explained that correctly and has not therefore given you some very poor advice.

However, I will discuss this with netops once again...

I believe you, DJ. You're probably far more knowledgeable than he is. They just don't wanna listen, Telkom style. I'll see tonight if I can get WTFast up and running. I used to use it many years ago so should be fine.
 
WinMTR Results: at what pointdo youconsider results unacceptable?

HI,
Running winMTR via a test account on CW. (www.mybroadband.co.za)

At what point would you start considering WINMTR results bad?

best

Geoff
 
>1ms



/runs ;)

Funny ha ha. Trying to give the test account a good run before posting anything ....

Also will only post results if I think the results are credible and a fair reflection of performance ....


This is a BIG decision ... Not going to move if I see marginal improvement ......

Ja for you okes on fibre, but we are still sucking on ADSL2 -----
 
So after back and forth between various parties in the EU I now have a definitive answer about what is happening with Blizzard traffic on Zayo's network.

Contrary to Blizzard's claims, they are advertising the USA route to Zayo themselves. It has nothing to do with any link failures and other related issues on Zayo's network.

Here is the exact quote from Zayo's netops guys:

The reason for your latency is due to Blizzard not advertising routes to us in the EU. This causes traffic to route to the USA which causes approximately 70 ms latency. Unfortunately we are not able to resolve this issue without Blizzard re-advertising the correct routes to us.

So after contact with Blizzard, they have stated the following:

Blizzard is in the process of turning up new services which should alleviate these problems.

We did not receive a time frame for this resolution but the bottom line is that it is an issue with the way that Blizzard are announcing their routes to various parties in the EU, and they are advertising the USA route themselves which at this point they have not changed and Zayo cannot change. We are however now in communication with the guys now directly but Blizzard do not appear able to provide definitive time-frames for their solution just yet.

I hope this helps you guys out to take the matter further with Blizzard, as we will also attempt to do, but know that this has nothing to do with our network and is absolutely not something that we can control...
 
Last edited:
Awesome work DJ!

Thank you so much for getting real feedback.

Do you mind if I post this info on the Blizzard forums?
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X