AfricanTech
Honorary Master
Pity you're not in an area serviced by a decent provider. It's cheaper than dsl, like for like.
How so dear fellow?
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
Pity you're not in an area serviced by a decent provider. It's cheaper than dsl, like for like.
There is an issue coming from Blizzard's side with the way they are announcing their routes once it hops off our network and on to some of their peering networks overseas. They're pushing the data to the US first which is absurd. Unfortunately it's not routing under ours nor IS's control so nothing we can necessarily do here to fix the problem, but it seems they are slowly deploying fixes and changes to address this...
DJ, why isn't it affecting other ISP's though? I've tested the Mweb connection here at work and it's at 190ms vs the 290ms on CW.
DJ, why isn't it affecting other ISP's though? I've tested the Mweb connection here at work and it's at 190ms vs the 290ms on CW.
Because 1) it doesn't appear to hit all parts of all of their peering networks; and 2) not all ISPs use the same international peering partners and boxes, and devices, and so on.
But honestly, you know I'd fix this if it were something under our control. We'd just update routing ourselves or get IS to have the international guys update their routing tables. In this case it's simply not an option as the wonky routing happens off any part of the network that either us or IS have any influence or control over. There's just no way to control somebody else's network and force changes onto their end...
Because 1) it doesn't appear to hit all parts of all of their peering networks; and 2) not all ISPs use the same international peering partners and boxes, and devices, and so on.
But honestly, you know I'd fix this if it were something under our control. We'd just update routing ourselves or get IS to have the international guys update their routing tables. In this case it's simply not an option as the wonky routing happens off any part of the network that either us or IS have any influence or control over. There's just no way to control somebody else's network and force changes onto their end...
OK, I see, thanks. I trust you have made Blizzard aware of this problem though? Sorry, for harping on about this. I just really want my low pings back![]()
Pity I don't get no Vumatel in my area
Eish, how the hell Telkom actually sells anything is a miracle when you compare their offers to the ISP's offerings on Vuma.
Drop me a PM quickly. I have new staff who are handling the custom requests and we're nearly finished with our POCs and costings...![]()
Custom Request 50GB's for R100 and ill take it DJ.. is that how we need to do it?![]()
![]()
![]()
Custom Request 50GB's for R100 and ill take it DJ.. is that how we need to do it?![]()
![]()
![]()
OK, I see, thanks. I trust you have made Blizzard aware of this problem though? Sorry, for harping on about this. I just really want my low pings back![]()
So after some digging and investigating we have found an answer to what you are seeing, its due to maintenance work due to be carried out on one of the major links due to a hungry rat.
They routed the traffic through America to allow for the works, but it has since been rescheduled to happen in June, yet the traffic diversion was never taken away.
After speaking with Zayo and their service desk they are going to investigate and hopefully revert things until needed, but this is just speculation at this point as I am unsure how bad the link is, or if it can take any traffic at all.
It does get more strange though, as I don't believe that the traffic ever leaves America as the latency seen is the typical round trip to America only, although the IP route suggests America, France and Germany so its left me confused how they are doing this.
It may just be Blizzard keeping all this in their network and using their American servers to do all the work instead of adding the round trip latency spikes which are typically seen when jumping continents.
Supposedly so, rats have apparently chewed through a major cable leaving it damaged enough for them to perform maintenance works on it, ultimately causing this issue.
Once the network team get hold of this during normal working hours, they may well revert the traffic to its original routes, as it was only due to be in place whilst maintenance work was carried out, now that they have moved the dates, they will hopefully move the diversion.
Hehehe, cools. But will keep a look out for any change in data packages etcThat's for our custom broadband-evolve builds that we are doing...![]()
Yeh i knowNow that's taking a chance given that 100GB costs R279![]()