DStv Online addresses streaming issues

Raath went on to outline some points in the route where problems could creep in:

The in-home network;
last mile network (copper to the DSLAM);
backhaul from the DSLAM to the exchange;
the IPC network which the ISP leases directly from Telkom;
peering link between ISPs, or if there is no peering, the routing from the MWEB network where the stream originates.
This routing complexity can introduce latency, Raath said.

This is called passing the buck, not fixing the problem.
I'm sure DJ is going to throw a fit (at them telling us to blame the ISP) :p
 
Absolute colly wobble, next excuse please!!!

It is impossible to be an end user problem when so many separate people have the exact same issue in different parts of the country, different lines, different ISP's etc etc... If someone on a 20Mb line is buffering with those 'moving legos' then it's the hosts problem!!!
 
I just wonder why I don't have sport streaming issues with oversea based sites, but only with SS.
 
“The fact that Mweb users tend not to have issues while other ISPs do indicates that the load on the streaming servers is perfectly within their capabilities, and points more to the routing that sits between the servers and the end-user,” Raath said.

How stupid are you? So Mweb users having no issues, excuses buffering Supersport streams?
 
Last edited:
Dear Mr. Mike Raath. While I appreciate the technical response, most of what you said is complete hogwosh.

Sure, ISP's play a vital role in the routing process, but when you got user complaints over various ISP's using entirely different backbones, in entirely different areas within the country, using entirely different exchanges... well, it just make it sound like you are passing the buck.

Stop making excuses, blaming the ISP's and fix your content streaming servers.

It's really not that hard. This is a tech forum, filled with people in the know and I personally, dont appreciate being BS'd
 
And then when our ISP calls mweb they will tell our ISP to f-off. Sounds like Raath is feeling some heat.
 
It has nothing to do with Mweb subscribers getting priority. It has everything to do with how they deliver their streams. It's not one steady delivery like all other streams. They send it in bursts of data as I've shown time and time again.

I also notice that it has taken them quite a while to respond to these questions, because they've invested more in their infrastructure since our collective bitching and moaning. There are few issues over the last few weeks. Pity it takes such complaining to get them to do something. Thanks to mybb for not giving up...
 
It has nothing to do with Mweb subscribers getting priority. It has everything to do with how they deliver their streams. It's not one steady delivery like all other streams. They send it in bursts of data as I've shown time and time again.

I also notice that it has taken them quite a while to respond to these questions, because they've invested more in their infrastructure since our collective bitching and moaning. There are few issues over the last few weeks. Pity it takes such complaining to get them to do something. Thanks to mybb for not giving up...

Does it work now?
 
Works better. Minimal buffering issues but they still happen on occasion. Things are a lot better though...
 
Ye I am very greatful that MyBB has brought this matter into the spotlight. I hope the infrastructure changes DJ is mentioning will make some difference. Will test it with the springbok game tonight. :)
 
He added that DStv Online serves its streams from one of the largest content delivery network (CDN) providers in the world, which Mweb has partnered with. They are also the only CDN with a streaming presence in South Africa, Raath said.

Uhm, I actually work very close with CDN providers... They are wrong.

Also, their CDN explanation is wrong.
 
I am actually interested in knowing where the Akamai node is hosted, probably within the Mweb data centre…
 
Well a tracert points straight to Mweb...

I know that there was one hosted at Internet Solutions, also used to work closely with Mweb until 2011... Know some things not to be discussed online. I don't work with Akamai, but with two other CDN provides (one being larger than Akamai) with streaming services in SA. We are also bringing another big player over to SA, but all this is confidential.
 
I have no idea about the technical side of things but every tracert I've run (and there are many) have pointed to Mweb servers...
 
I have no idea about the technical side of things but every tracert I've run (and there are many) have pointed to Mweb servers...

In my opinion there is nothing wrong with Akamai CDN, it is more in the method how the data is reachable at the node, should it be hosted at Mweb then they are in control how data is send and received… going more in-depth with their rules might change the game. There is numerous variables going along with this issue, capacity, management etc. This largely give me the idea that the problem (or actually regulated) is at Mweb in my honest opinion.

Looking at this:

“I would stress that users must get in touch with their ISP to investigate the root cause bearing in mind all the complexities above, and possibly even get their ISP to liaise directly with MWEB who can assist and advise those ISPs, with queries as they arise,” Raath said.

Well, last time the Free the Web campaign said something about open peering…
 
Top
Sign up to the MyBroadband newsletter
X