Trouble with Supersport on Afrihost

[AfriMan]

We've run a few tests on our side. From what I can see, all seems normal. A few of you have sent us trace routes and what I can see is that our traffic bounces around in the Mweb network a bit. Up to that latencies seem pretty solid. It could be a peering issue, but we need more evidence to raise this with Mweb.

If you can send me comparative trace routes, that would REALLY help me

 

[fishfly]

I keep getting error ERROR: 3322 when using my Afrihost account to stream on supersports

 

[AfriMan]

I keep getting error ERROR: 3322 when using my Afrihost account to stream on supersports

Can you run a traceroute to the server and see what happens?

 

[BravoVictor]

Hear you go .

Tracing route to www.supersport.com [197.80.203.136]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 8 ms 5 ms 6 ms 105-236-11-1-esr-lo.mtnbusiness.co.za [105.236.11.1]
3 7 ms 10 ms 7 ms 41.181.221.254
4 7 ms 68 ms 7 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
5 8 ms 7 ms 7 ms compj-cpt-1.mtnns.net [196.44.18.2]
6 29 ms 29 ms 29 ms ct-cr-2.za--tb-cr-1.za.mtnns.net [196.44.31.134]
7 8 ms 12 ms 8 ms 196.44.0.74
8 8 ms 8 ms 8 ms 196-28-178-141.adsl.mweb.co.za [196.28.178.141]
9 37 ms 35 ms 35 ms 197-84-7-2.cpt.mweb.co.za [197.84.7.2]
10 38 ms 41 ms 39 ms tengig0-7-0-1.vic-p-1.mweb.co.za [197.84.4.47]
11 57 ms 57 ms 57 ms tengig0-0-0-0.vic-pe-1.mweb.co.za [197.80.4.243]
12 36 ms 36 ms 35 ms tengig0-0-0-0.mca-pe-1.mweb.co.za [197.80.4.37]
13 59 ms 58 ms 57 ms 197-80-96-30.jhb.mweb.co.za [197.80.96.30]
14 36 ms 36 ms 35 ms 197-80-206-100.jhb.mweb.co.za [197.80.206.100]
15 36 ms 35 ms 36 ms 197-80-203-5.jhb.mweb.co.za [197.80.203.5]
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

 

[Crowley]

Tracing route to www.supersport.com [197.80.203.136]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 6 ms 6 ms 6 ms 105-236-1-65-esr-lo.mtnbusiness.co.za [105.236.1
.65]
3 8 ms 8 ms 71 ms ipc-recieve-jh-4a.za.mtnbusiness.net [41.181.178
.41]
4 8 ms 7 ms 8 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165
.115]
5 8 ms 8 ms 14 ms jh-dca-2.za--qux-b.za.mtnbusiness.net [41.181.16
5.114]
6 8 ms 8 ms 9 ms 41.181.180.10
7 8 ms 8 ms 7 ms 196.44.0.72
8 9 ms 8 ms 8 ms postfix.wipronet.co.za [196.22.161.133]
9 11 ms 10 ms 11 ms tengig0-0-0-1.vic-p-1.mweb.co.za [197.80.4.140]

10 9 ms 9 ms 10 ms tengig0-0-0-0.vic-pe-1.mweb.co.za [197.80.4.243]

11 9 ms 9 ms 9 ms tengig0-0-0-0.mca-pe-1.mweb.co.za [197.80.4.37]

12 9 ms 9 ms 9 ms 197-80-96-30.jhb.mweb.co.za [197.80.96.30]
13 9 ms 9 ms 9 ms 197-80-206-100.jhb.mweb.co.za [197.80.206.100]
14 9 ms 10 ms 9 ms 197-80-203-5.jhb.mweb.co.za [197.80.203.5]
15 * * * Request timed out.

 

[DJ...]

I'm with Openweb and have the same timeout issues, but I have a theory - you cannot run a tracert to their live video site. So using that same logic, could the timeouts not be caused by the live score information bar that perhaps comes from a different server and doesn't respond to tracerts? It's always the last to load on my end so I figured that's the last server that responds as well...

 

[Hectic]

This might possibly of no use, but I will post it anyway.
I stream Radio Algoa most of the day.
I use a TI uncapped account for this.
Yesterday a friend asked me to dl a couple of torrents.
I decided to this with my Afrihost capped account.
I used about 65% of the 4meg line speed for the dl's. The streaming was useless. I don't think I could listen longer than 3 minutes at a time, then it would dissapear for 30 minutes. It was extremely frustrating.

I do a lot of http downloads and at times the odd P2P during the day and it has little impact on my streaming.

I'm not sure if Afrihost had a bad day yesterday or if the account is generally bad on streaming.

The streaming runs at about 32kB/s afik.

 

[AfriMan]

Tracing route to www.supersport.com [197.80.203.136]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 6 ms 6 ms 6 ms 105-236-1-65-esr-lo.mtnbusiness.co.za [105.236.1
.65]
3 8 ms 8 ms 71 ms ipc-recieve-jh-4a.za.mtnbusiness.net [41.181.178
.41]
4 8 ms 7 ms 8 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165
.115]
5 8 ms 8 ms 14 ms jh-dca-2.za--qux-b.za.mtnbusiness.net [41.181.16
5.114]
6 8 ms 8 ms 9 ms 41.181.180.10
7 8 ms 8 ms 7 ms 196.44.0.72
8 9 ms 8 ms 8 ms postfix.wipronet.co.za [196.22.161.133]
9 11 ms 10 ms 11 ms tengig0-0-0-1.vic-p-1.mweb.co.za [197.80.4.140]

10 9 ms 9 ms 10 ms tengig0-0-0-0.vic-pe-1.mweb.co.za [197.80.4.243]

11 9 ms 9 ms 9 ms tengig0-0-0-0.mca-pe-1.mweb.co.za [197.80.4.37]

12 9 ms 9 ms 9 ms 197-80-96-30.jhb.mweb.co.za [197.80.96.30]
13 9 ms 9 ms 9 ms 197-80-206-100.jhb.mweb.co.za [197.80.206.100]
14 9 ms 10 ms 9 ms 197-80-203-5.jhb.mweb.co.za [197.80.203.5]
15 * * * Request timed out.

Hear you go .

Tracing route to www.supersport.com [197.80.203.136]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 8 ms 5 ms 6 ms 105-236-11-1-esr-lo.mtnbusiness.co.za [105.236.11.1]
3 7 ms 10 ms 7 ms 41.181.221.254
4 7 ms 68 ms 7 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
5 8 ms 7 ms 7 ms compj-cpt-1.mtnns.net [196.44.18.2]
6 29 ms 29 ms 29 ms ct-cr-2.za--tb-cr-1.za.mtnns.net [196.44.31.134]
7 8 ms 12 ms 8 ms 196.44.0.74
8 8 ms 8 ms 8 ms 196-28-178-141.adsl.mweb.co.za [196.28.178.141]
9 37 ms 35 ms 35 ms 197-84-7-2.cpt.mweb.co.za [197.84.7.2]
10 38 ms 41 ms 39 ms tengig0-7-0-1.vic-p-1.mweb.co.za [197.84.4.47]
11 57 ms 57 ms 57 ms tengig0-0-0-0.vic-pe-1.mweb.co.za [197.80.4.243]
12 36 ms 36 ms 35 ms tengig0-0-0-0.mca-pe-1.mweb.co.za [197.80.4.37]
13 59 ms 58 ms 57 ms 197-80-96-30.jhb.mweb.co.za [197.80.96.30]
14 36 ms 36 ms 35 ms 197-80-206-100.jhb.mweb.co.za [197.80.206.100]
15 36 ms 35 ms 36 ms 197-80-203-5.jhb.mweb.co.za [197.80.203.5]
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

To me these traces look fine until they reach Mweb's network and then seem to lose their minds somehow.

And any idea how tracing from other networks differs at all?

 

[AfriMan]

This might possibly of no use, but I will post it anyway.
I stream Radio Algoa most of the day.
I use a TI uncapped account for this.
Yesterday a friend asked me to dl a couple of torrents.
I decided to this with my Afrihost capped account.
I used about 65% of the 4meg line speed for the dl's. The streaming was useless. I don't think I could listen longer than 3 minutes at a time, then it would dissapear for 30 minutes. It was extremely frustrating.

I do a lot of http downloads and at times the odd P2P during the day and it has little impact on my streaming.

I'm not sure if Afrihost had a bad day yesterday or if the account is generally bad on streaming.

The streaming runs at about 32kB/s afik.

We were shaping quite a bit during the course of yesterday. If you're account was being shaped (if you're on Uncapped, not Capped or Business) then trying to saturate your line with torrents does affect performance. We try to overcome this with QoS, but we can only do some much from our side. QoS on your router or local network is much more effective to make sure that your streaming gets the best priority if you need to max out on torrents at the same time.

 

[Crowley]

And there we go again.

Tracing route to www.supersport.com [197.80.203.136]
over a maximum of 30 hops:

1 <1 ms <1 ms 1 ms 192.168.0.1
2 6 ms 6 ms 6 ms 105-236-1-65-esr-lo.mtnbusiness.co.za [105.236.1
.65]
3 7 ms 7 ms 7 ms ipc-recieve-jh-4a.za.mtnbusiness.net [41.181.178
.41]
4 8 ms 7 ms 8 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165
.115]
5 7 ms 8 ms 7 ms jh-dca-2.za--qux-b.za.mtnbusiness.net [41.181.16
5.114]
6 8 ms 9 ms 8 ms jh-cr-2.za--jh-dca-2.za-a.mtnns.net [196.44.0.22
4]
7 8 ms 7 ms 7 ms jh-pr-1.za--jh-cr-2.za.mtnns.net [196.44.0.222]

8 8 ms 8 ms 8 ms postfix.wipronet.co.za [196.22.161.133]
9 10 ms 11 ms 12 ms tengig0-0-0-3.vic-p-1.mweb.co.za [197.80.7.1]
10 9 ms 9 ms 9 ms tengig0-0-0-0.vic-pe-1.mweb.co.za [197.80.4.243]

11 9 ms 9 ms 8 ms tengig0-0-0-0.mca-pe-1.mweb.co.za [197.80.4.37]

12 9 ms 9 ms 9 ms 197-80-96-30.jhb.mweb.co.za [197.80.96.30]
13 10 ms 9 ms 10 ms 197-80-206-100.jhb.mweb.co.za [197.80.206.100]
14 9 ms 10 ms 9 ms 197-80-203-5.jhb.mweb.co.za [197.80.203.5]
15 * * * Request timed out.

 

[Crowley]

I loaded a 2gb Webafrica account to finish watching the rugby. The streaming was perfect but the traceroute gave me the same result except it was redirected to dstv.com.

Tracing route to redirect.dstv.com [196.28.29.245]
over a maximum of 30 hops:

1 <1 ms 1 ms 1 ms 192.168.0.1
2 6 ms 5 ms 5 ms 196-210-132-129.dynamic.isadsl.co.za [196.210.13
2.129]
3 8 ms 8 ms 7 ms 196.38.72.229
4 8 ms 8 ms 8 ms cdsl2-rba-vl150.ip.isnet.net [196.38.73.9]
5 8 ms 8 ms 7 ms 168.209.1.140
6 8 ms 68 ms 19 ms 168.209.1.170
7 8 ms 8 ms 8 ms mweb-2.jinx.net.za [196.223.14.32]
8 11 ms 11 ms 11 ms 197-80-7-65.jhb.mweb.co.za [197.80.7.65]
9 9 ms 9 ms 8 ms vl-11.vic-hscore-1.mweb.co.za [197.80.5.237]
10 183 ms 184 ms 182 ms tengig0-0-0-2.11.vic-p-1.mweb.co.za [197.80.5.22
5]
11 183 ms 183 ms 182 ms pos0-3-2-0.lon-up-1.mweb.co.za [197.80.5.7]
12 182 ms 183 ms 183 ms 176.67.177.131
13 179 ms 179 ms 179 ms 196.22.169.86
14 180 ms 179 ms 178 ms 252.29.28.196.mweb.co.za [196.28.29.252]
15 * * * Request timed out.

 

[7h3Ch3353]

This thread is also related to this problem, http://mybroadband.co.za/vb/showthread.php/545549-Afrihoax-Just-Keeping-Promises?highlight=afrihoax
I've since moved back to afrihost because everything else is still so much better on the business accounts than the other isp's but streaming still sucks and I'm on a 8 meg line now.

 

[Ho3n3r]

Streaming was much better today, but at stages it still buffers a lot.

 

[BravoVictor]

well just watching the hi lights sucks ffs all other accounts work fine but afrihost account gets lost for some reason ??? enough i say I will buy a mweb package just too watch my sport ffs . You guys wanted a tracert and look sane *** diffrent day dammit man make a plan ???

 

[DJ...]

Sucks on openweb as well. Could be mweb pulling their usual underhanded nonsense again. Who knows. The ISPs need to investigate...

 

[PurSpyk!!]

Is this ever going to be address, or ignored and hope we don't bother trying to use Supersport? The odd thing is even just opening the supersport site is far slower than opening any other sites.

 

[AfriGuy]

Is this ever going to be address, or ignored and hope we don't bother trying to use Supersport? The odd thing is even just opening the supersport site is far slower than opening any other sites.

This definitely isn't being ignored on our end We are battling to try and replicate the slow response times from the site though. Please send me a PM with your account info and as much info you have on the issues being experienced.

 

[wconan]

The fact that one cant pull tracert results to the Supersport Server makes things even more difficult to address. I've given up trying to watch anything via my Afrihost account

 

[AfriGuy]

The fact that one cant pull tracert results to the Supersport Server makes things even more difficult to address. I've given up trying to watch anything via my Afrihost account

Even if their servers aren't accepting ICMP, we can still look at a traceroute to see if any latency is being introduced on our network. Could you please try and have one pasted up here?

 

[wconan]

tracert supersport.com

Tracing route to supersport.com [197.80.203.245]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 9 ms 10 ms 10 ms 105-236-5-1-esr-lo.mtnbusiness.co.za [105.236.5.1]
3 11 ms 11 ms 11 ms ipc-recieve-tb-2a.mtnbusiness.net [41.181.54.86]
4 10 ms 10 ms 41 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
5 11 ms 11 ms 12 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 33 ms 34 ms 34 ms 196.44.31.106
7 34 ms 35 ms 36 ms nl-ha-2.za--rb-cr-1.za-a.mtnns.net [196.44.0.121]
8 13 ms 13 ms 12 ms 196-28-178-141.adsl.mweb.co.za [196.28.178.141]
9 43 ms 42 ms 39 ms 197-84-7-2.cpt.mweb.co.za [197.84.7.2]
10 44 ms 44 ms 43 ms tengig0-7-0-1.vic-p-1.mweb.co.za [197.84.4.47]
11 41 ms 40 ms 40 ms tengig0-0-0-0.vic-pe-1.mweb.co.za [197.80.4.243]
12 62 ms 62 ms 62 ms tengig0-0-0-0.mca-pe-1.mweb.co.za [197.80.4.37]
13 40 ms 39 ms * 197-80-96-30.jhb.mweb.co.za [197.80.96.30]
14 62 ms 60 ms 59 ms 197-80-206-100.jhb.mweb.co.za [197.80.206.100]
15 41 ms 40 ms 41 ms 197-80-203-5.jhb.mweb.co.za [197.80.203.5]
16 * * * Request timed out.
17 * * * Request timed out.
18 ^C