Afrihost New Network Feedback - Part 2

Status
Not open for further replies.
Wait, isn't upload speed on a 8 MB line also suppose to be 1 MB just like on a 10 MB line?
When I had a 10 MB line ASSIA forced my download speed down to 8 MB though my upload was kept at 1 MB.
Since my line anyway synced at 8 MB and wouldn't go higher because of ASSIA, I thought I might as well downgrade to a 8 MB line. The downgrade will also make my SNR a bit better to keep ASSIA happy, so on the new line speed my 8 MB sync should be nice and solid.

Fast forward a few days after ASSIA got hold of my 8 MB line, upstream SNR is better now sitting at 9.5 where it was around 6 before, but downstream SNR is worse, at times dipping below 6.
My line now syncs at only 7 MB down and 0.7 up, so why the heck did the POS ASSIA system lower my upload speed even though upstream SNR is better?
 
Wait, isn't upload speed on a 8 MB line also suppose to be 1 MB just like on a 10 MB line?
When I had a 10 MB line ASSIA forced my download speed down to 8 MB though my upload was kept at 1 MB.
Since my line anyway synced at 8 MB and wouldn't go higher because of ASSIA, I thought I might as well downgrade to a 8 MB line. The downgrade will also make my SNR a bit better to keep ASSIA happy, so on the new line speed my 8 MB sync should be nice and solid.

Fast forward a few days after ASSIA got hold of my 8 MB line, upstream SNR is better now sitting at 9.5 where it was around 6 before, but downstream SNR is worse, at times dipping below 6.
My line now syncs at only 7 MB down and 0.7 up, so why the heck did the POS ASSIA system lower my upload speed even though upstream SNR is better?

Upload speed is always a bit of a hit and miss I'm afraid. As with the downstream, upload is very much an "up to" value - so the 1Mbps is a best case scenario.

0.7Mbps ain't bad at all, all things considered :)
 
Upload speed is always a bit of a hit and miss I'm afraid. As with the downstream, upload is very much an "up to" value - so the 1Mbps is a best case scenario.

0.7Mbps ain't bad at all, all things considered :)


Without ASSIA messing things up my line comfortably syncs at 10 even 11 MB down and 1 MB up, sure the system probably thinks it's unstable hence the drop in sync it forces on me, but it's stable enough and works for me without ASSIA trying to be a nanny.
 
Without ASSIA messing things up my line comfortably syncs at 10 even 11 MB down and 1 MB up, sure the system probably thinks it's unstable hence the drop in sync it forces on me, but it's stable enough and works for me without ASSIA trying to be a nanny.

ASSIA should only really be pushing a line down if it deems it as unstable, so if it picks up line drops, interference or poor stats it'll step in. If the line's stable it should also push the line back up though.
 
ASSIA should only really be pushing a line down if it deems it as unstable, so if it picks up line drops, interference or poor stats it'll step in. If the line's stable it should also push the line back up though.


I never ever seen on my own line or heard/read of someone elses line speed actually being bumped up by ASSIA even after a line fix dramatically improving line quality, ASSIA always just drag lines down.
 
I never ever seen on my own line or heard/read of someone elses line speed actually being bumped up by ASSIA even after a line fix dramatically improving line quality, ASSIA always just drag lines down.

It does happen :)
 
I never ever seen on my own line or heard/read of someone elses line speed actually being bumped up by ASSIA even after a line fix dramatically improving line quality, ASSIA always just drag lines down.

For a very brief period, when I had ASSIA, it bumped my downstream speed to 5120, but it still felt like a normal 4mb line. Yes, I had maybe an extra 50kbps down rate..but the packet loss and high ping is what makes ASSIA a B1tch.. But will agree with AG, there is definitely something wrong with your line. ASSIA refreshes your line stats constantly and return it forces the DSLAM/MSAN to adjust your line to keep it stable. With fast path that real time monitoring is disabled. So you never realize there is a fault until the line actually dies, which I prefer because explaining to a Telkom tech that your line keeps disconnecting and reconnecting is just a waste of time. They never find the fault until the line loses sync completely, then they want to try and fix it. Telkom needs educate their techs properly on ASSIA or just dump the system.
 
Last edited:
Did something just break? Connection dropped now local latency sitting at 150ms and minimal throughput
 
Last edited:
All good on this side, any results you can paste here?

40Mbit VDSL

5490624011.png


Tracing route to afrihost.co.za [41.86.112.68]
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 162 ms 157 ms 157 ms cpt-up1.ip.adsl.co.za [169.1.5.105]
4 153 ms 150 ms 152 ms cpt-in1.ip.adsl.co.za [169.1.5.118]
5 164 ms 160 ms 161 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
6 156 ms 155 ms 155 ms optinet.ct1.napafrica.net [196.10.140.145]
7 174 ms 175 ms 174 ms bu-ether1.cpt-p-1.optinet.net [197.84.7.33]
8 175 ms 175 ms * te0-0-0-0.vic-p-2.optinet.net [197.84.4.35]
9 172 ms 173 ms 173 ms 102.te0-0-2-0.vic-tr-1.optinet.net [197.80.7.36]
10 181 ms 181 ms 181 ms 197-81-226-77.jhb.mweb.co.za [197.81.226.77]
11 170 ms 170 ms 170 ms 197-81-226-53.jhb.mweb.co.za [197.81.226.53]
12 103 ms 102 ms 103 ms 197-81-229-2.jhb.mweb.co.za [197.81.229.2]
13 175 ms 173 ms 178 ms 197-81-229-9.jhb.mweb.co.za [197.81.229.9]
14 166 ms 171 ms 172 ms 41-86-112-68.mweb.co.za [41.86.112.68]


I'm in the process of testing other ISP's
 
Nope something did break. Getting less than 1Mbps speed test
Huge latency too. Same for a friend sitting 8km's away also on Afrihost.

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

1 <1 ms <1 ms <1 ms 10.1.0.254
2 * * * Request timed out.
3 146 ms 148 ms 147 ms cpt-up1.ip.adsl.co.za [169.1.5.105]
4 150 ms 147 ms 146 ms cpt-in1.ip.adsl.co.za [169.1.5.118]
5 108 ms 112 ms 109 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
6 144 ms 141 ms 138 ms optinet.ct1.napafrica.net [196.10.140.145]
7 * * 149 ms bu-ether1.cpt-p-1.optinet.net [197.84.7.33]
8 147 ms 146 ms * vl11.cpt-hscore-1.optinet.net [197.84.5.238]
9 98 ms 106 ms 92 ms 196.28.178.66
10 153 ms 150 ms 150 ms cte-core-sw2.vwol.net [196.41.144.35]
11 147 ms 147 ms * www.mweb.co.za [196.2.63.110]
12 147 ms 147 ms 147 ms www.mweb.co.za [196.2.63.110]

Trace complete.



Tracing route to www.afrihost.com [104.20.30.244]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.1.0.254
2 * * * Request timed out.
3 * 148 ms 146 ms cpt-up1.ip.adsl.co.za [169.1.5.105]
4 147 ms 152 ms 146 ms cpt-up2.ip.adsl.co.za [169.1.5.106]
5 103 ms 109 ms 107 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
6 155 ms 107 ms 107 ms africainx.ct1.napafrica.net [196.10.140.7]
7 163 ms 161 ms 162 ms CORE.GP-ID-DCE-3.TO.GP-ID-MEC-2.AINX.P2P.10G.za.africainx.net [41.84.13.228]
8 162 ms 162 ms 163 ms 41-66-181-59-3b.CLO008-CDN-local-VLAN-321.africainx.net [41.66.181.59]
9 162 ms 163 ms * 104.20.30.244
10 163 ms 162 ms 163 ms 104.20.30.244

Trace complete.
 
Hey guys

About to put a notice up, seeing some issues in the South at the moment.
More updates to follow.
 
Something broke myside as well don't know if it the weather but o.O



Code:
Ping Test:

ping 197.242.144.102

64 bytes from 197.242.144.102: icmp_req=1 ttl=53 time=676 ms
64 bytes from 197.242.144.102: icmp_req=2 ttl=53 time=161 ms
64 bytes from 197.242.144.102: icmp_req=3 ttl=53 time=158 ms
64 bytes from 197.242.144.102: icmp_req=4 ttl=53 time=161 ms
64 bytes from 197.242.144.102: icmp_req=5 ttl=53 time=158 ms


ping 8.8.8.8

64 bytes from 8.8.8.8: icmp_req=1 ttl=53 time=167 ms
64 bytes from 8.8.8.8: icmp_req=2 ttl=53 time=163 ms
Request timeout for icmp_seq 3
64 bytes from 8.8.8.8: icmp_req=4 ttl=53 time=156 ms
64 bytes from 8.8.8.8: icmp_req=5 ttl=53 time=156 ms


Trace Test:

traceroute -n 197.242.144.102

  1	10.0.0.2          	1 ms      	1 ms      	1 ms      	
  2	Request timed out 	*         	*         	*         	
  3	Request timed out 	*         	*         	
   	169.1.5.1         	70 ms     	
  4	169.1.5.1         	146 ms    	135 ms    	
   	Request timed out 	*         	
  5	41.164.52.4       	134 ms    	
   	Request timed out 	*         	
   	196.44.0.7        	139 ms    	
  6	196.44.0.2        	96 ms     	
   	Request timed out 	*         	
   	196.44.31.6       	239 ms    	
  7	196.31.220.2      	158 ms    	
   	Request timed out 	*         	
   	196.31.220.1      	157 ms    	
  8	197.242.144.1     	158 ms    	
   	Request timed out 	*         	
   	196.31.63.2       	160 ms    	
  9	Request timed out 	*         	
   	196.30.42.1       	234 ms    	


traceroute -n 8.8.8.8

  1	10.0.0.2          	1 ms      	1 ms      	1 ms      	
  2	Request timed out 	*         	*         	*         	
  3	169.1.5.1         	105 ms    	72 ms     	190 ms    	
  4	169.1.5.1         	97 ms     	104 ms    	136 ms    	
  5	169.1.5.1         	135 ms    	
   	41.164.52.4       	135 ms    	
   	172.18.1.1        	152 ms    	
  6	172.18.1.1        	156 ms    	
   	72.14.194.2       	155 ms    	
   	72.14.239.5       	159 ms    	
  7	72.14.194.2       	156 ms    	


DNS Test:

nslookup www.afrihost.com

Name:	www.afrihost.com
Address: 104.20.30.244


nslookup www.google.com

Name:	www.google.com
Address: 216.58.223.4


nslookup thishouldfail.afrihost.com

** server can't find thisshouldfail.com: NXDOMAIN
 
Afriguy on a seperate note, Think telkom could do anything about my SNR, upstream goes to absolute crap when ever there is a cloud in the sky

Code:
 	                        Downstream	 Upstream
Line Coding(Trellis):	    On 	            On 
SNR Margin (dB):	            120 	            47 
Attenuation (dB):	            200 	            120 
Output Power (dBm):	     85 	             124 
Attainable Rate (Kbps):	   21164 	             728 
Rate (Kbps):	           10239 	             728 
D (interleaver depth):	      1 	              1 
Delay (msec):	             0.19 	            0.25 
 
HEC Errors:                       0 	               0 
OCD Errors:	               0 	               0 
LCD Errors:	                       0 	               0 
 
Total ES:	                       0 	                0
 
Afriguy on a seperate note, Think telkom could do anything about my SNR, upstream goes to absolute crap when ever there is a cloud in the sky

Code:
 	                        Downstream	 Upstream
Line Coding(Trellis):	    On 	            On 
SNR Margin (dB):	            120 	            47 
Attenuation (dB):	            200 	            120 
Output Power (dBm):	     85 	             124 
Attainable Rate (Kbps):	   21164 	             728 
Rate (Kbps):	           10239 	             728 
D (interleaver depth):	      1 	              1 
Delay (msec):	             0.19 	            0.25 
 
HEC Errors:                       0 	               0 
OCD Errors:	               0 	               0 
LCD Errors:	                       0 	               0 
 
Total ES:	                       0 	                0

Do your stats change/ degrade based on the weather?
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X