Afrihost Uncapped DSL Feedback

happydaddy · May 9, 2017

Thats to my bb

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\happydaddy>tracert www.mybroadband.co.za

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

1 9 ms <1 ms <1 ms 192.168.20.1
2 2 ms 1 ms 1 ms 10.0.4.2
3 5 ms 3 ms 3 ms 10.0.56.1
4 4 ms 5 ms 3 ms 10.0.48.1
5 * * * Request timed out.
6 61 ms 41 ms 30 ms cpt-up1.ip.adsl.co.za [169.1.5.105]
7 109 ms 96 ms 112 ms 169-1-21-66.ip.afrihost.co.za [169.1.21.66]
8 101 ms 104 ms 112 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
9 50 ms 44 ms 49 ms 169-1-21-29.ip.afrihost.co.za [169.1.21.29]
10 119 ms 117 ms 70 ms cloudflare.ixp.joburg [196.60.8.198]
11 137 ms 112 ms 118 ms 104.20.10.169

Trace complete.

C:\Users\happydaddy>

renagade-wolf · May 9, 2017

You have problems upstream

Code:

Ping Test:

ping 197.242.144.102

64 bytes from 197.242.144.102: icmp_req=1 ttl=55 time=160 ms
64 bytes from 197.242.144.102: icmp_req=2 ttl=55 time=164 ms
64 bytes from 197.242.144.102: icmp_req=3 ttl=55 time=124 ms
64 bytes from 197.242.144.102: icmp_req=4 ttl=55 time=157 ms
64 bytes from 197.242.144.102: icmp_req=5 ttl=55 time=141 ms


ping 8.8.8.8

64 bytes from 8.8.8.8: icmp_req=1 ttl=52 time=29 ms
64 bytes from 8.8.8.8: icmp_req=2 ttl=52 time=28 ms
Request timeout for icmp_seq 3
64 bytes from 8.8.8.8: icmp_req=4 ttl=52 time=27 ms
Request timeout for icmp_seq 5


Trace Test:

traceroute -n 197.242.144.102

  1	10.0.0.2          	1 ms      	1 ms      	1 ms      	
  2	Request timed out 	*         	*         	*         	
  3	169.1.5.1         	9 ms      	9 ms      	10 ms     	
  4	169.1.5.1         	10 ms     	9 ms      	9 ms      	
  5	41.164.52.4       	87 ms     	
   	169.1.5.1         	125 ms    	101 ms    	
  6	172.18.1.1        	28 ms     	28 ms     	
   	41.164.52.4       	120 ms    	
  7	169.1.5.7         	93 ms     	98 ms     	
   	172.18.1.1        	65 ms     	
  8	169.1.5.7         	58 ms     	86 ms     	98 ms     	
  9	169.1.21.5        	28 ms     	32 ms     	
   	169.1.5.7         	90 ms     	
 10	169.1.21.5        	37 ms     	
   	197.242.144.1     	162 ms    	
 11	197.242.144.1     	162 ms    	


traceroute -n 8.8.8.8

  1	10.0.0.2          	1 ms      	
  2	Request timed out 	*         	
  3	169.1.5.1         	10 ms     	
  4	169.1.21.6        	10 ms     	
  5	169.1.5.1         	61 ms     	
  6	169.1.21.2        	47 ms     	
  7	72.14.239.3       	147 ms    	
  8	8.8.8.8           	27 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: 169.1.2.89


nslookup thishouldfail.afrihost.com

** server can't find thisshouldfail.com: NXDOMAIN

Turbocharging has done nothing to improve anything.

happydaddy · May 9, 2017

This is same router different isp tracert to www.mybroadband.co.za Hope it helps

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\happydaddy>tracert www.mybroadband.co.za

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

1 9 ms <1 ms <1 ms 192.168.20.1
2 3 ms 1 ms 2 ms 10.0.4.2
3 2 ms 3 ms 4 ms 10.0.56.1
4 7 ms 2 ms 3 ms 10.0.48.1
5 * * * Request timed out.
6 40 ms 31 ms 33 ms cdsl2-ctn-vl2473-ipc.ip.isnet.net [196.38.72.194
]
7 83 ms 36 ms 25 ms vlan2473.cdsl2-ctn.isdsl.net [196.38.72.193]
8 49 ms 29 ms 41 ms 196.35.115.136
9 52 ms 32 ms 33 ms mi-za-cpt-p8-te0-7-0-0.ip.isnet.net [168.209.2.1
3]
10 43 ms 35 ms 27 ms 168.209.6.130
11 45 ms 33 ms 37 ms 196-10-140-198.ixp.capetown [196.10.140.198]
12 27 ms 51 ms 43 ms 104.20.9.169

Trace complete.

C:\Users\happydaddy>

AfriGenie · May 9, 2017

happydaddy said:
Below 2 sites i tracert to

happydaddy said:
Thats to my bb

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\happydaddy>tracert www.mybroadband.co.za

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

1 9 ms <1 ms <1 ms 192.168.20.1
2 2 ms 1 ms 1 ms 10.0.4.2
3 5 ms 3 ms 3 ms 10.0.56.1
4 4 ms 5 ms 3 ms 10.0.48.1
5 * * * Request timed out.
6 61 ms 41 ms 30 ms cpt-up1.ip.adsl.co.za [169.1.5.105]
7 109 ms 96 ms 112 ms 169-1-21-66.ip.afrihost.co.za [169.1.21.66]
8 101 ms 104 ms 112 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
9 50 ms 44 ms 49 ms 169-1-21-29.ip.afrihost.co.za [169.1.21.29]
10 119 ms 117 ms 70 ms cloudflare.ixp.joburg [196.60.8.198]
11 137 ms 112 ms 118 ms 104.20.10.169

Trace complete.

C:\Users\happydaddy>

Thanks for the traceroute results. I've asked our Team to check what's going on.

MoonOwl · May 9, 2017

Is access to content on cloud storage services such as Mega and Dropbox deprioritised on your premium uncapped packages because Dropbox will not even open and Mega is taking forever... Such is the story with GitHub git services too

renagade-wolf · May 9, 2017

renagade-wolf said:
You have problems upstream

<SNIP>

Turbocharging has done nothing to improve anything.

Http downloads:

Youtube Streaming:

MoonOwl · May 9, 2017

MoonOwl said:
Is access to content on cloud storage services such as Mega and Dropbox deprioritised on your premium uncapped packages because Dropbox will not even open and Mega is taking forever... Such is the story with GitHub git services too

Streaming is fine and I understand that downloads are shaped during peak periods BUT I didn't expect just a few kibibytes of a document to be inaccessible

renagade-wolf · May 9, 2017

Either my turbocharge just kicked in, or something was fixed cause things have improved. Well downloads at least, tools still show weird vibes in the network

Code:

Ping Test:

ping 197.242.144.102

64 bytes from 197.242.144.102: icmp_req=1 ttl=55 time=158 ms
64 bytes from 197.242.144.102: icmp_req=2 ttl=55 time=167 ms
Request timeout for icmp_seq 3
Request timeout for icmp_seq 4
64 bytes from 197.242.144.102: icmp_req=5 ttl=55 time=157 ms


ping 8.8.8.8

Request timeout for icmp_seq 1
64 bytes from 8.8.8.8: icmp_req=2 ttl=52 time=28 ms
Request timeout for icmp_seq 3
Request timeout for icmp_seq 4
64 bytes from 8.8.8.8: icmp_req=5 ttl=52 time=28 ms


Trace Test:

traceroute -n 197.242.144.102

  1	10.0.0.2          	1 ms      	1 ms      	
  2	Request timed out 	*         	*         	
  3	169.1.5.1         	8 ms      	8 ms      	
  4	169.1.5.1         	9 ms      	10 ms     	
  5	169.1.5.1         	91 ms     	64 ms     	
  6	172.18.1.1        	72 ms     	
   	41.169.57.2       	154 ms    	
  7	169.1.5.7         	111 ms    	56 ms     	
  8	169.1.21.5        	32 ms     	
   	169.1.5.7         	120 ms    	
  9	169.1.21.5        	33 ms     	


traceroute -n 8.8.8.8

  1	10.0.0.2          	1 ms      	
  2	Request timed out 	*         	
  3	169.1.5.1         	10 ms     	
  4	169.1.21.6        	11 ms     	
  5	169.1.5.1         	118 ms    	
  6	169.1.21.2        	25 ms     	
  7	72.14.239.3       	99 ms     	
  8	8.8.8.8           	27 ms     	


DNS Test:

nslookup www.afrihost.com

Name:	www.afrihost.com
Address: 104.20.31.244


nslookup www.google.com

Name:	www.google.com
Address: 169.1.2.91


nslookup thishouldfail.afrihost.com

** server can't find thisshouldfail.com: NXDOMAIN

Zertop's LineTool Results
Date/Time: Tue May 09 20:25:44 CAT 2017

Basic Report:

Your packet loss was 0%.
Your average ping was 7ms.
Your maximum ping was 16ms.

Looking at your average ping, your line seems to be running perfectly.
It seems that your maximum ping is also good. If there are any issues, they most probably lie with your ISP

Detailed Report:

Code:

Pinging 155.239.255.250 with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=16ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63

Ping statistics for 155.239.255.250:
    Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 7ms, Maximum = 16ms, Average = 7ms

Reaper1242 · May 9, 2017

renagade-wolf said:
Either my turbocharge just kicked in, or something was fixed cause things have improved.

I think something improved because streaming my side is also better and I didn't turbocharge.
Streaming is fine. Everything else is for sh*t

I doubt it's a permanent fix. Probably just a band aid.

AfriGenie · May 9, 2017

renagade-wolf said:

Either my turbocharge just kicked in, or something was fixed cause things have improved. Well downloads at least, tools still show weird vibes in the network

Code:

Ping Test:

ping 197.242.144.102

64 bytes from 197.242.144.102: icmp_req=1 ttl=55 time=158 ms
64 bytes from 197.242.144.102: icmp_req=2 ttl=55 time=167 ms
Request timeout for icmp_seq 3
Request timeout for icmp_seq 4
64 bytes from 197.242.144.102: icmp_req=5 ttl=55 time=157 ms


ping 8.8.8.8

Request timeout for icmp_seq 1
64 bytes from 8.8.8.8: icmp_req=2 ttl=52 time=28 ms
Request timeout for icmp_seq 3
Request timeout for icmp_seq 4
64 bytes from 8.8.8.8: icmp_req=5 ttl=52 time=28 ms


Trace Test:

traceroute -n 197.242.144.102

  1	10.0.0.2          	1 ms      	1 ms      	
  2	Request timed out 	*         	*         	
  3	169.1.5.1         	8 ms      	8 ms      	
  4	169.1.5.1         	9 ms      	10 ms     	
  5	169.1.5.1         	91 ms     	64 ms     	
  6	172.18.1.1        	72 ms     	
   	41.169.57.2       	154 ms    	
  7	169.1.5.7         	111 ms    	56 ms     	
  8	169.1.21.5        	32 ms     	
   	169.1.5.7         	120 ms    	
  9	169.1.21.5        	33 ms     	


traceroute -n 8.8.8.8

  1	10.0.0.2          	1 ms      	
  2	Request timed out 	*         	
  3	169.1.5.1         	10 ms     	
  4	169.1.21.6        	11 ms     	
  5	169.1.5.1         	118 ms    	
  6	169.1.21.2        	25 ms     	
  7	72.14.239.3       	99 ms     	
  8	8.8.8.8           	27 ms     	


DNS Test:

nslookup www.afrihost.com

Name:	www.afrihost.com
Address: 104.20.31.244


nslookup www.google.com

Name:	www.google.com
Address: 169.1.2.91


nslookup thishouldfail.afrihost.com

** server can't find thisshouldfail.com: NXDOMAIN

Thanks for the update.

Please let me know if there is any change.

SickTricky · May 9, 2017

bad again. but now really bad. xbox cant even download updates

AfriGenie · May 9, 2017

Reaper1242 said:
I think something improved because streaming my side is also better and I didn't turbocharge.

I doubt it's a permanent fix. Probably just a band aid.

Thank you for the update.

If you notice any change, please let me know.

AfriGenie · May 9, 2017

SickTricky said:
bad again. but now really bad. xbox cant even download updates

What sort of Uncapped account do you have?

Jings · May 9, 2017

Definitely a major issue happening here. Haven't accessed DSTV Catch Up in the last two weeks but right now the buffering is terrible. YouTube is streaming seamlessly.

AfriGenie · May 9, 2017

MoonOwl said:
Streaming is fine and I understand that downloads are shaped during peak periods BUT I didn't expect just a few kibibytes of a document to be inaccessible

It really does depend on the type of HTTP download. Depending on the type of Uncapped account you have, you will be able to use Turbocharge to make sure that you're able to use Dropbox and Mega when you need to.

SickTricky · May 9, 2017

both 20mbps and 40mbps business. youtube is fine. facebook is ok. but the rest not so good. so the throughput is there! but the other internets...nope

SickTricky · May 9, 2017

SickTricky said:
both 20mbps and 40mbps business. youtube is fine. facebook is ok. but the rest not so good. so the throughput is there! but the other internets...nope

My CPU runs out of steam before the buffer can be an issue

Gekco · May 9, 2017

renagade-wolf said:
Either my turbocharge just kicked in, or something was fixed cause things have improved. Well downloads at least, tools still show weird vibes in the network

Downloads have improved a lot for me as well. We'll see if it lasts.
Not using turbocharge.

Reaper1242 · May 9, 2017

Gekco said:
Downloads have improved a lot for me as well. We'll see if it lasts.
Not using turbocharge.

Download from GitHub running at 0

AfriGenie · May 9, 2017

SickTricky said:
both 20mbps and 40mbps business. youtube is fine. facebook is ok. but the rest not so good. so the throughput is there! but the other internets...nope

Your performance should be pretty decent at the moment. Which services aren't running that great for you?

Join the MyBroadband community

Get started

Afrihost Uncapped DSL Feedback

New Member

Well-Known Member

New Member

Afrihost

Active Member

Well-Known Member

Active Member

Well-Known Member

Well-Known Member

Afrihost

Active Member

Afrihost

Afrihost

Treasure Maker

Afrihost

Active Member

Active Member

Expert Member

Well-Known Member

Afrihost