Should it matter on a 10Mbps business account?
Yes. If it is set to the lowest quality it will default to that regardless of line speed.
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
Should it matter on a 10Mbps business account?
Yes. If it is set to the lowest quality it will default to that regardless of line speed.
It's not the quality that's an issue, buffering and streaming is.
Just a note to Netflix users. I did a bandwidth test a while back to see how much it uses. You'd be surprised actually how heavy it can be and 10Mbps in some circumstances is just cutting it.
Here is bandwidth graph while streaming super HD quality.
![]()
Yeah. They really need to give people choice as to what quality they'd like to stream. This Good, Better and Best is not cutting it.
Under best you have better than DVD, 720p, 1080p, Super HD and 3D depending on connection speed.
Just a note to Netflix users. I did a bandwidth test a while back to see how much it uses. You'd be surprised actually how heavy it can be and 10Mbps in some circumstances is just cutting it.
Here is bandwidth graph while streaming super HD quality.
![]()
I'm not having issues at present. Watching MIB.
Mine is suffering again tonight...
I think for their main markets like the US, it's probably less of an issue. Even here on a great 10Mbps line you can battle to stream on HD![]()
That is probably true but surely it can't be that difficult to allow a more detailed quality setting which gives control over to the viewer instead of the network.
For my needs 720p is fine, so why would I want to consume more bandwidth just because I can?
They are already offering those but just under one umbrella. I'm not too sure but it really shouldn't affect costs that much if at all.I suppose it means more costs for them because they have to store and retain more versions of the content in different compression rates.
But yeah, more choice should always be a good thing. Maybe that's why they don't offer services in SA, maybe they don't want to offer more choices cos it raises their costs![]()
They are already offering those but just under one umbrella. I'm not too sure but it really shouldn't affect costs that much if at all.
I was getting those kind of results with WORSE ping on my 10mbps line! sigh...Looking pretty good for a 1Mbps. Like that ping![]()
I was getting those kind of results with WORSE ping on my 10mbps line! sigh...
Good news: Kyle helped me find the problem.
Bad news: Problem is with the exchange and while the fault is logged with telkom we know that they are not the fastest on any given day so I guess I will be sitting with this problem for weeks
Afripeople, I do apologise for all my ranting. Your service on social media has been nothing but spectacular! (not so sure about the call centre) So thank you for all the help and putting me in touch with someone who helped me find the problem at the root of it all... it is very much appreciated!
Now I just hope that telkom ups their game and actually sorts this out quickly.
Latency a tad high today, sitting at 100ms I normally get 18ms to local.......![]()
Tracing route to microsoft.com [65.55.58.201]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.201
2 11 ms 11 ms 11 ms ?-esr-lo.mtnbusiness.co.za [105.236.9.65]
3 25 ms 27 ms 27 ms ipc-recieve-tb-2a.mtnbusiness.net [41.181.54.86]
4 17 ms 14 ms 14 ms tb-dca-2.za--qux-a.za.mtnbusiness.net [41.181.184.28]
5 19 ms 14 ms 15 ms compj-cpt-1.mtnns.net [196.44.18.2]
6 159 ms 172 ms 179 ms ls-cr-2.uk--tb-cr-1.za.mtnns.net [196.44.31.113]
7 181 ms 171 ms 178 ms ls-pr-1.uk--ls-cr-2.uk-a.mtn.net [209.212.111.201]
8 * * * Request timed out.
9 * * * Request timed out.
10 * 255 ms * xe-0-1-2-0.blu-96c-1b.ntwk.msn.net [207.46.46.142]
11 299 ms 299 ms 298 ms xe-4-1-1-0.co1-96c-1b.ntwk.msn.net [207.46.40.78]
12 296 ms 298 ms 298 ms xe-0-0-0-0.co1-96c-1a.ntwk.msn.net [207.46.33.178]
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 * * * 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.
Trace complete.
Pinging microsoft.com [65.55.58.201] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 65.55.58.201:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Tracing route to cnn.com [157.166.226.26]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.201
2 18 ms 18 ms 16 ms ?-esr-lo.mtnbusiness.co.za [105.236.9.65]
3 48 ms 51 ms 58 ms ipc-send-tb-3a.mtnbusiness.net [41.181.53.214]
4 99 ms 102 ms 103 ms tb-dca-2.za--qux-a.za.mtnbusiness.net [41.181.184.28]
5 45 ms 48 ms 54 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 21 ms 20 ms 19 ms 196.44.31.106
7 264 ms 273 ms 282 ms am-cr-1.am--lt-cr-1.uk-a.mtnns.net [196.44.31.221]
8 167 ms 169 ms 171 ms ls-pr-2.uk--ls-cr-1.uk-a.mtn.net [209.212.111.203]
9 241 ms 241 ms 249 ms 195.50.122.181
10 267 ms 266 ms 267 ms vl-3607-ve-231.csw2.London1.Level3.net [4.69.166.26]
11 245 ms 249 ms 249 ms ae-57-222.ebr2.London1.Level3.net [4.69.153.133]
12 247 ms 248 ms 249 ms ae-43-43.ebr1.NewYork1.Level3.net [4.69.137.74]
13 274 ms 253 ms 245 ms 4.69.201.66
14 269 ms 277 ms 269 ms ae-1-100.ebr1.Washington12.Level3.net [4.69.143.213]
15 265 ms 267 ms 270 ms ae-8-8.ebr1.Washington1.Level3.net [4.69.143.217]
16 267 ms 267 ms 266 ms ae-2-2.ebr3.Atlanta2.Level3.net [4.69.132.85]
17 261 ms 252 ms 275 ms ae-73-73.ebr2.Atlanta2.Level3.net [4.69.148.254]
18 244 ms 243 ms 246 ms ae-2-52.edge4.Atlanta2.Level3.net [4.69.150.77]
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 ^C
Pinging cnn.com [157.166.226.25] with 32 bytes of data:
Request timed out.
Request timed out.
Ping statistics for 157.166.226.25:
Packets: Sent = 2, Received = 0, Lost = 2 (100% loss),
Tracing route to bbc.co.uk [212.58.251.195]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.201
2 26 ms 28 ms 29 ms ?-esr-lo.mtnbusiness.co.za [105.236.9.65]
3 95 ms 74 ms 69 ms ipc-recieve-tb-1a.mtnbusiness.net [41.181.53.150]
4 20 ms 19 ms 22 ms tb-dca-2.za--qux-a.za.mtnbusiness.net [41.181.184.28]
5 64 ms 64 ms 59 ms compj-cpt-1.mtnns.net [196.44.18.2]
6 297 ms 336 ms 293 ms ls-cr-2.uk--tb-cr-1.za.mtnns.net [196.44.31.113]
7 286 ms 314 ms 344 ms ls-pr-1.uk--ls-cr-2.uk-a.mtn.net [209.212.111.201]
8 358 ms 326 ms 344 ms bbc-linx.pr01.thdow.bbc.co.uk [195.66.224.103]
9 * * * Request timed out.
10 * * * Request timed out.
11 370 ms 376 ms 382 ms ae0.er01.telhc.bbc.co.uk [132.185.254.109]
12 298 ms 249 ms 201 ms 132.185.255.140
13 169 ms 157 ms 160 ms www-vip.telhc.bbc.co.uk [212.58.251.195]
Trace complete.