Afrihost New Network Feedback - Part 2

Status
Not open for further replies.
Hummercellc said:
I see Afrihost setup a Varnish Cache server for ShowMax on 169.1.1.227.
Now I see SSL errors every now and again when watching Showmax, changing to google DNS and all is fine.
Click to expand...

Not sure if this is something new.
Either way, if you're experiencing issues with that specific server please let our Critical Care team know.
 
dj2381 said:
Last Result:
Download Speed: 15804 kbps (1975.5 KB/sec transfer rate)
Upload Speed: 835 kbps (104.4 KB/sec transfer rate)
Latency: 6 ms
Jitter: 1 ms
2016/08/01, 2:08:58 PM

Just had a port reset.

SNR still at 5.8

It does suck, the line has been reduced to 19Mbs and 18Mbs previously but no change in the SNR. It would suck to downgrade and find out it's this terrible Telkom Pace modem, but I suppose it's wishful thinking. If only there was a option for 15Mbs, with cheaper data :whistle:
Click to expand...

Not too bad, but if your 15Mbps line drops multiple times a day it'll drive you nuts :(
You can try and replace your modem, some do make a difference but i'll be marginal at best.
 
dj2381 said:
I upgraded from 10Mb, because 20Mb recently became available, I live just over 1km form the exchange which should give me a great ratio.
Funny enough the 1st week the line was hitting a full 20Mbs without issue, if I could get fiber here , I would drop them in a second. The lack of any further support, I'm not sure why I'm surprised.
Click to expand...

Same thing with me. I upgraded from 10mb (at the time was syncing @ 12mb) to 20mb because it became available in my area.

Started off with 20mb, but with a low 6db SNR. After a few days sync dropped to 18, then to 16, now it's on 14mb, so I'm just going to go back to 10mb (12mb) as I'm not seeing much benefit. Just to add though that I didn't have any disconnects or none that I noticed (I work during the day).

+1 on the fiber, but I don't see much activity on that side in my area.
 
krustyrsa said:
Did you check to make sure you are indeed running on VDSL and not ADSL2+?, I have seen somewhere on MyBB a user had the same issue. Turns out the modulation was causing poor SNR..If you have a VDSL router and its not on VDSL mode, then you need to log a call and request it to be moved over to VDSL. Check if it solves your issue. If not then do what Afriguy suggested and downgrade back to 10mb, until telkom can replace the copper in your area.
Click to expand...

I'm still on the ADSL2+ exchange that only goes up to 20mb. The 40mb exchanges are VDSL requiring a VDSL modem. If I understood what you said correctly.
 
krustyrsa said:
20mb runs on both VDSL and ADSL2+..but 20mb VDSL is just more stable on some lines.
Click to expand...

I understand that but isn't it the "type" of exchange that determines the mode? Only the new exchanges are VDSL, then you get the ADSL2+ that only used to go up to 10mb and now recently 20mb, then the really old 4mb exchanges that use G.dmt mode.
 
wingnut771 said:
I understand that but isn't it the "type" of exchange that determines the mode? Only the new exchanges are VDSL, then you get the ADSL2+ that only used to go up to 10mb and now recently 20mb, then the really old 4mb exchanges that use G.dmt mode.
Click to expand...

New exchanges support both ADSL2+ and VDSL at 20Mbps. You'd prefer VDSL as it has less overhead, about 18Mbps out of 20Mbps in a speedtest versus the 16-17Mbps in ADSL2+ and you get 2Mbps upload instead of 1Mbps. VDSL can sometimes also be more stable.
 
wingnut771 said:
I understand that but isn't it the "type" of exchange that determines the mode? Only the new exchanges are VDSL, then you get the ADSL2+ that only used to go up to 10mb and now recently 20mb, then the really old 4mb exchanges that use G.dmt mode.
Click to expand...
Only MSAN's (new exchanges)are capable of doing 20mb ADSL2+ and VDSL as far as I know..but VDSL must be enabled and you need be within the coverage area to get it..
 
krustyrsa said:
Only MSAN's (new exchanges)are capable of doing 20mb ADSL2+ and VDSL as far as I know..but VDSL must be enabled and you need be within the coverage area to get it..
Click to expand...

Not necessarily :)
Regular DSLAMs will support ADSL2+ to anything up to 20Mbps where enabled. That's about the max throughput available 24Mbps of ADSL2+.
 
AfriPeeps, the issue still remains :)

6:07pm

Tracing route to mweb.co.za [196.2.63.110]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1]
2 * * * Request timed out.
3 31 ms 27 ms 28 ms cpt-tx2.ip.adsl.co.za [169.1.5.81]
4 35 ms 34 ms 34 ms cpt-rx2.ip.adsl.co.za [169.1.5.82]
5 27 ms 26 ms 26 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
6 34 ms 34 ms 34 ms optinet.ixp.capetown [196.10.140.145]
7 29 ms 30 ms 30 ms te0-7-0-3.cpt-p-2.optinet.net [197.84.7.2]
8 34 ms 34 ms 34 ms vl11.cpt-hscore-1.optinet.net [197.84.5.238]
9 29 ms 28 ms 27 ms 196.28.178.66
10 36 ms 35 ms 35 ms cte-core-sw2.vwol.net [196.41.144.35]
11 34 ms 35 ms 34 ms www.mweb.co.za [196.2.63.110]

7:55pm

Tracing route to mweb.co.za [196.2.63.110]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1]
2 * * * Request timed out.
3 28 ms 28 ms 27 ms cpt-tx2.ip.adsl.co.za [169.1.5.81]
4 137 ms 147 ms 149 ms cpt-rx2.ip.adsl.co.za [169.1.5.82]
5 57 ms 52 ms 48 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
6 35 ms 34 ms 34 ms optinet.ixp.capetown [196.10.140.145]
7 52 ms 47 ms 44 ms te0-7-0-3.cpt-p-2.optinet.net [197.84.7.2]
8 58 ms 60 ms 57 ms vl11.cpt-hscore-1.optinet.net [197.84.5.238]
9 29 ms 29 ms 30 ms 196.28.178.66
10 108 ms 107 ms 110 ms cte-core-sw2.vwol.net [196.41.144.35]
11 85 ms 87 ms 96 ms www.mweb.co.za [196.2.63.110]
 
Well the Mweb Peering problem is still ongoing, day 17 now?
Surely something must be done about it?
How long are we expected to wait? 2 weeks+ seems a bit ridiculous or am I just being impatient here? And no critical care are of no assistance, apologising does not fix the problem.
 
Masik3R said:
AfriPeeps, the issue still remains :)

6:07pm

Tracing route to mweb.co.za [196.2.63.110]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1]
2 * * * Request timed out.
3 31 ms 27 ms 28 ms cpt-tx2.ip.adsl.co.za [169.1.5.81]
4 35 ms 34 ms 34 ms cpt-rx2.ip.adsl.co.za [169.1.5.82]
5 27 ms 26 ms 26 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
6 34 ms 34 ms 34 ms optinet.ixp.capetown [196.10.140.145]
7 29 ms 30 ms 30 ms te0-7-0-3.cpt-p-2.optinet.net [197.84.7.2]
8 34 ms 34 ms 34 ms vl11.cpt-hscore-1.optinet.net [197.84.5.238]
9 29 ms 28 ms 27 ms 196.28.178.66
10 36 ms 35 ms 35 ms cte-core-sw2.vwol.net [196.41.144.35]
11 34 ms 35 ms 34 ms www.mweb.co.za [196.2.63.110]

7:55pm

Tracing route to mweb.co.za [196.2.63.110]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1]
2 * * * Request timed out.
3 28 ms 28 ms 27 ms cpt-tx2.ip.adsl.co.za [169.1.5.81]
4 137 ms 147 ms 149 ms cpt-rx2.ip.adsl.co.za [169.1.5.82]
5 57 ms 52 ms 48 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
6 35 ms 34 ms 34 ms optinet.ixp.capetown [196.10.140.145]
7 52 ms 47 ms 44 ms te0-7-0-3.cpt-p-2.optinet.net [197.84.7.2]
8 58 ms 60 ms 57 ms vl11.cpt-hscore-1.optinet.net [197.84.5.238]
9 29 ms 29 ms 30 ms 196.28.178.66
10 108 ms 107 ms 110 ms cte-core-sw2.vwol.net [196.41.144.35]
11 85 ms 87 ms 96 ms www.mweb.co.za [196.2.63.110]
Click to expand...
My trace route stops at hop 6. Can't access anything at Mweb ATM day 17 now.
 
C'mon guys, stop saying you logging calls and lets start seeing some results. Peering to M-Web is broken once again. This is now dragging on far too long. I have been with Afrihost through all the rough patches. But I think it's time to start looking elsewhere.

Tracing route to www.news24.com [41.86.110.200]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.254
2 * * * Request timed out.
3 20 ms 19 ms 19 ms dbn-up1.ip.adsl.co.za [169.1.5.161]
4 21 ms 19 ms 20 ms dbn-up2.ip.adsl.co.za [169.1.5.162]
5 29 ms 29 ms 25 ms 169-1-5-208.ip.afrihost.co.za [169.1.5.208]
6 19 ms 19 ms 19 ms optinet.ixp.durban [196.10.141.75]
7 * * * Request timed out.
8 * * * Request timed out.


Tracing route to www.mweb.co.za [196.2.63.110]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.254
2 * * * Request timed out.
3 80 ms 79 ms 72 ms dbn-up1.ip.adsl.co.za [169.1.5.161]
4 60 ms 65 ms 68 ms dbn-up2.ip.adsl.co.za [169.1.5.162]
5 19 ms 19 ms 19 ms 169-1-5-208.ip.afrihost.co.za [169.1.5.208]
6 19 ms 19 ms 20 ms optinet.ixp.durban [196.10.141.75]
7 * * * Request timed out.
8 * * * Request timed out.


:mad:
 
Same in pe
782215138abc0442911d4a3299942ceb.jpg


Tomorrow their saying we have no problem
 
Rage_Monkey said:
Anyone else experience Afrihost shaping peer2peer on a capped account?
I've caught them doing this to me 3 times now, every time I need to log a call and have them "reset" my account which then sorts it out.
And before you comment - yes I have PLENTY of data available, yes I get full line speed on other protocols!
*sarcasm*And I just *LOVE* how they no longer have after hours tel support staff!
Probably cause their helpdesk got sick of having to deal with customer complaints!
Click to expand...

I have a 40Mbps VDSL line. And I wouldn't say I am being shaped, but most certainly throttled on many occasions. For instance I will only get about 17-18Mbps until 12am. Then suddenly I will get close to my full line speed. Not sure if this is the usual practice.
 
Mine looks a bit healthier but still looks like a problem. I'll throw mine in just to try and help out.

Tracing route to mweb.co.za [196.2.63.110]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1]
2 * * * Request timed out.
3 21 ms 20 ms 20 ms cpt-up2.ip.adsl.co.za [169.1.5.106]
4 26 ms 21 ms 20 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
5 21 ms 21 ms 21 ms optinet.ixp.capetown [196.10.140.145]
6 43 ms 41 ms 39 ms bu-ether1.cpt-p-1.optinet.net [197.84.7.33]
7 77 ms 82 ms 230 ms vl11.cpt-hscore-1.optinet.net [197.84.5.238]
8 21 ms 21 ms 21 ms 196.28.178.66
9 32 ms 33 ms 35 ms cte-core-sw2.vwol.net [196.41.144.35]
10 21 ms 21 ms 21 ms www.mweb.co.za [196.2.63.110]
 
I sent more trace routes to Afrihost's so called 'critical care'.
Can't access news24.com either.

"The webpage at https://www.mweb.co.za might be temporarily down or it may have moved permanently to a new web address."
 
Last edited:
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X