I had the same issue last night too. Streaming was just dead. Switched to Axxess backup account same problem.
-
Join the MyBroadband community
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
-
Question of the Day: Will you be watching the FIFA World Cup Final?
Afrihost CAPPED ADSL Feedback (MTN)
- Thread starter eddief1
- Start date
- Status
I had the same issue last night too. Streaming was just dead. Switched to Axxess backup account same problem.
- Joined
- Oct 9, 2014
- Messages
- 7,265
- Reaction score
- 6
Have you been able to test your performance this morning on streaming? Which streaming services do you primarily use?
I have a 10Mb/s ADSL line which is synced at 5Mb/s, and everything works very well.
I'm considering changing to a 4Mb/s ADSL line, but I have a question. If there is congestion in the exchange, would a 10Mb/s line get priority over a 4Mb/s line?
Or put another way, would a 10Mb/s line set to sync at 4Mb/s out perform a 4Mb/s line which syncs at 4Mb/s?
I'm considering changing to a 4Mb/s ADSL line, but I have a question. If there is congestion in the exchange, would a 10Mb/s line get priority over a 4Mb/s line?
Or put another way, would a 10Mb/s line set to sync at 4Mb/s out perform a 4Mb/s line which syncs at 4Mb/s?
- Joined
- Oct 9, 2014
- Messages
- 7,265
- Reaction score
- 6
The actual performance will be very similar for a 10Mbps line synced to 4Mbps and a 4Mbps synced at the full 4Mbps.
The congestion will still be an issue on either account, it will however be less noticeable on a 4Mbps line in theory.
How badly is the congestion affecting your connection speeds at the moment?
For the past 4 weeks I have had very good speeds, which may be as a result of everyone being on holiday (I live in Jhb). I will find out in the next week or 2
However prior to that I had problems with another ISP and they claimed that it was either congestion or a Telkom routing problem.
- Joined
- Oct 9, 2014
- Messages
- 7,265
- Reaction score
- 6
For the past 4 weeks I have had very good speeds, which may be as a result of everyone being on holiday (I live in Jhb). I will find out in the next week or 2
However prior to that I had problems with another ISP and they claimed that it was either congestion or a Telkom routing problem.
I certainly hope you continue to experience those speeds, we are working very hard to ensure that our users do not experience it drops in performance due to capacity issues on our side.
analytical
Active Member
Thanks for the info,my line is with afrihost.
Ill log a fault with support.
Ill log a fault with support.
- Joined
- Oct 9, 2014
- Messages
- 7,265
- Reaction score
- 6
No problem, if we can assist at all with logging the fault, or following up for you, please let me know. -E
ScottulusMaximus
Honorary Master
No need to rub it in Microsoft!
EDIT: nothing wrong with line, just found it funny that the biggest software company in the world is calling my connection crap
Last edited:
Speedtest from my HTPC:
Traceroutes to google.com/.co.za
Currently using the Google DNS servers.
Testing with "namebench" for best DNS to use. It could only access 18% of DNS servers on 1st try. Trying again with longer timeouts.
Code:
xbmc@htpc:~$ ./speedtest-cli
Retrieving speedtest.net configuration...
Retrieving speedtest.net server list...
Testing from MTN Business (105.xxx.xxx.xxx)...
Selecting best server based on latency...
Hosted by Telkom Internet (Cape Town) [6.76 km]: 103.271 ms
Testing download speed........................................
Download: 3.34 Mbits/s
Testing upload speed..................................................
Upload: 0.38 Mbits/s
Code:
xbmc@htpc:~$ traceroute google.com
traceroute to google.com (173.194.67.138), 30 hops max, 60 byte packets
1 10.0.0.2 (10.0.0.2) 6.022 ms 6.019 ms 5.999 ms
2 105-xxx-xxx-xxx-esr-lo.mtnbusiness.co.za (105.xxx.xxx.xxx) 99.605 ms 105.464 ms 105.473 ms
3 41.181.51.182 (41.181.51.182) 116.332 ms 116.336 ms 116.329 ms
4 tb-dca-2.za--qux-i.za.mtnbusiness.net (66.8.11.186) 120.732 ms tb-dca-2.za--qux-a.za.mtnbusiness.net (41.181.184.28) 120.738 ms tb-dca-2.za--qux-i.za.mtnbusiness.net (66.8.11.186) 120.724 ms
5 compj-cpt-1.mtnns.net (196.44.18.2) 128.830 ms 128.838 ms 135.679 ms
6 ls-cr-2--tb-cr-1.uk-b.mtnns.net (196.44.31.113) 284.474 ms 253.293 ms 253.251 ms
7 ls-pr-2.uk--ls-cr-2.uk-a.mtn.net (209.212.111.187) 259.112 ms 252.959 ms 255.113 ms
8 google-peering-ls-pr-2.uk.mtnns.net (209.212.99.13) 261.712 ms 261.748 ms 261.733 ms
9 209.85.255.76 (209.85.255.76) 261.729 ms 269.355 ms 269.363 ms
10 proxy.google.com (216.239.51.5) 319.413 ms 209.85.245.2 (209.85.245.2) 275.295 ms 209.85.244.240 (209.85.244.240) 289.897 ms
11 66.249.95.173 (66.249.95.173) 305.397 ms 64.233.174.82 (64.233.174.82) 289.802 ms 242.278 ms
12 209.85.250.165 (209.85.250.165) 284.296 ms 216.239.51.155 (216.239.51.155) 261.940 ms 216.239.47.87 (216.239.47.87) 262.492 ms
13 * * *
14 wi-in-f138.1e100.net (173.194.67.138) 286.082 ms 286.092 ms 286.077 ms
xbmc@htpc:~$ traceroute google.co.za
traceroute to google.co.za (216.58.223.35), 30 hops max, 60 byte packets
1 10.0.0.2 (10.0.0.2) 7.140 ms 7.129 ms 7.108 ms
2 105-xxx-xxx-xxx-esr-lo.mtnbusiness.co.za (105.xxx.xxx.xxx) 153.862 ms 153.867 ms 160.387 ms
3 ipc-send-tb-3a.mtnbusiness.net (41.181.53.214) 166.585 ms 166.593 ms 179.066 ms
4 tb-dca-2.za--qux-a.za.mtnbusiness.net (41.181.184.28) 179.077 ms 179.066 ms tb-dca-2.za--qux-i.za.mtnbusiness.net (66.8.11.186) 179.052 ms
5 compj-cpt-1.mtnns.net (196.44.18.2) 182.856 ms 182.866 ms 182.851 ms
6 ls-cr-2.uk--tb-cr-1.za.mtnns.net (196.44.31.113) 346.892 ms 308.631 ms 315.526 ms
7 ls-pr-2.uk--ls-cr-2.uk-a.mtn.net (209.212.111.187) 301.467 ms 241.462 ms 228.830 ms
8 google-peering-ls-pr-2.uk.mtnns.net (209.212.99.13) 228.804 ms 228.790 ms 235.806 ms
9 209.85.255.76 (209.85.255.76) 235.813 ms * 241.300 ms
10 66.249.95.9 (66.249.95.9) 270.782 ms 270.792 ms 270.778 ms
11 72.14.239.129 (72.14.239.129) 270.767 ms 265.877 ms 265.853 ms
12 jnb01s08-in-f3.1e100.net (216.58.223.35) 287.096 ms 287.106 ms 271.636 msCurrently using the Google DNS servers.
Testing with "namebench" for best DNS to use. It could only access 18% of DNS servers on 1st try. Trying again with longer timeouts.
View attachment 182450
No need to rub it in Microsoft!
EDIT: nothing wrong with line, just found it funny that the biggest software company in the world is calling my connection crap
That's not cool. Microsoft calling us names
What service are you running here?
Your ping to the 2nd hop is already over 100ms, which means you're getting latency before you reach our network. Your ping to your router is also over 6ms, which is high even over WiFi. Anything happening on the local network like a torrent or update? Maybe shut off all connected PC's and devices, and connect a single device via LAN cable with WiFi switched off and test again and see if you still get this
Your ping to the 2nd hop is already over 100ms, which means you're getting latency before you reach our network. Your ping to your router is also over 6ms, which is high even over WiFi. Anything happening on the local network like a torrent or update? Maybe shut off all connected PC's and devices, and connect a single device via LAN cable with WiFi switched off and test again and see if you still get this
The wife was streaming a show at the time.
Also, I'm using ethernet over power, which might add some overhead to the mix.
I also suspect that our copper is a bit noisy at times.
Which hop is the first one on the Telkom network, and from there on the MTN/AH network?
ScottulusMaximus
Honorary Master
That's not cool. Microsoft calling us names
What service are you running here?
Haha 4mB capped.
Bashley
Well-Known Member
Hi Peoples,
I am unable to open a couple of webpages. Is there a problem with Afrihost again? I PM'd the Afri-people but the do not reply.
Thanks
I am unable to open a couple of webpages. Is there a problem with Afrihost again? I PM'd the Afri-people but the do not reply.
Thanks
I'm also experiencing issues with streaming, especially at night. Here's my trace route:
Tracing route to google.com [216.58.223.46]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms DD-WRT [192.168.1.1]
2 9 ms 9 ms 9 ms 105-236-4-65-esr-lo.mtnbusiness.co.za [105.236.4
.65]
3 13 ms 11 ms 12 ms ipc-recieve-rb-4a.za.mtnbusiness.net [41.181.178
.89]
4 13 ms 13 ms 13 ms rb-dca-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.1
20]
5 13 ms 11 ms 12 ms jh-cr-1.za--rb-cr-2.za.mtnns.net [196.44.0.42]
6 11 ms 12 ms 17 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165
.115]
7 258 ms 211 ms 210 ms ls-cr-2.uk--rb-cr-1.za-g.mtnns.net [196.44.31.11
4]
8 209 ms 195 ms 199 ms ls-pr-2.uk--ls-cr-2.uk-a.mtn.net [209.212.111.18
7]
9 209 ms 208 ms 209 ms google-peering-ls-pr-2.uk.mtnns.net [209.212.99.
13]
10 193 ms 216 ms 193 ms 209.85.255.76
11 195 ms 191 ms 191 ms 66.249.95.9
12 191 ms 191 ms 190 ms 72.14.239.129
13 194 ms 192 ms 190 ms jnb01s08-in-f14.1e100.net [216.58.223.46]
Tracing route to google.com [216.58.223.46]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms DD-WRT [192.168.1.1]
2 9 ms 9 ms 9 ms 105-236-4-65-esr-lo.mtnbusiness.co.za [105.236.4
.65]
3 13 ms 11 ms 12 ms ipc-recieve-rb-4a.za.mtnbusiness.net [41.181.178
.89]
4 13 ms 13 ms 13 ms rb-dca-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.1
20]
5 13 ms 11 ms 12 ms jh-cr-1.za--rb-cr-2.za.mtnns.net [196.44.0.42]
6 11 ms 12 ms 17 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165
.115]
7 258 ms 211 ms 210 ms ls-cr-2.uk--rb-cr-1.za-g.mtnns.net [196.44.31.11
4]
8 209 ms 195 ms 199 ms ls-pr-2.uk--ls-cr-2.uk-a.mtn.net [209.212.111.18
7]
9 209 ms 208 ms 209 ms google-peering-ls-pr-2.uk.mtnns.net [209.212.99.
13]
10 193 ms 216 ms 193 ms 209.85.255.76
11 195 ms 191 ms 191 ms 66.249.95.9
12 191 ms 191 ms 190 ms 72.14.239.129
13 194 ms 192 ms 190 ms jnb01s08-in-f14.1e100.net [216.58.223.46]
The results look good here, was this run when you see the issues occur?
This was done now. All working fine. Will do another one tonight.
- Status