Afrihost New Network Feedback - Part 2

Status
Not open for further replies.
Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=188ms TTL=50
Reply from 8.8.8.8: bytes=32 time=188ms TTL=50
Reply from 8.8.8.8: bytes=32 time=187ms TTL=50
Reply from 8.8.8.8: bytes=32 time=186ms TTL=50

Ping statistics for 8.8.8.8:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 186ms, Maximum = 188ms, Average = 187ms

Is this because of the new cache server?
 
I have a suggestion AfriGuy. If it is possible to strike a deal with hotspot wifi providers like AlwaysOn or Vast networks, please do! In fact if you can offer the data wallet through hotspot providers since mobile data is quite expensive that would be great. In Durban there's a lot of wifi hotspots but only 50MB use available :(

Please check if this option is viable. Thanks again! :)
 
Just confirmed that we rolled out a new Google cache server yesterday. Some services like Android updates, Youtube and other Google related stuff might see higher latency until the server has finished caching.

Hopefully this'll happen soon. Can't even load a 480p video on my 8MB line.

Why were customers pushed onto the new cache server if it wasn't ready to be used?

And also informed, via a simple e-mail or notification on the website, that this process was taking place, so that everyone could at least avoid messaging here or submitting tech support tickets, thinking their account was having problems.
 
Afrihost is useless lately. Can't stream worth a damn. Switched back to my CW account and entire videos buffer in seconds. Submitting cancellation for my AH account. I took out this account because my CW account was hacked dry, but I was going to see which ISP was worth sticking with. This is exactly why I left Afrihost the last time. I don't want excuses and I don't want it to mostly work fine - I want it to always work and to work well.
 
This is fcking confusing


Why can't you just all of it together?
 

Attachments

  • 1473515073014.jpg
    1473515073014.jpg
    37.5 KB · Views: 172
Streaming seriously bad again this weekend. Don't know if it's the new google cache server or changes made to the system for this new free time data but something has definitely changed for the worse starting last weekend.
 
Chiming in...

Streaming seems dead in the water, so to speak. Ping results:

HTML:
ping 197.242.144.102

64 bytes from 197.242.144.102: icmp_req=1 ttl=53 time=39 ms
64 bytes from 197.242.144.102: icmp_req=2 ttl=53 time=39 ms
64 bytes from 197.242.144.102: icmp_req=3 ttl=53 time=40 ms
64 bytes from 197.242.144.102: icmp_req=4 ttl=53 time=39 ms
64 bytes from 197.242.144.102: icmp_req=5 ttl=53 time=46 ms


ping 8.8.8.8

64 bytes from 8.8.8.8: icmp_req=1 ttl=49 time=178 ms
64 bytes from 8.8.8.8: icmp_req=2 ttl=49 time=182 ms
64 bytes from 8.8.8.8: icmp_req=3 ttl=49 time=176 ms
64 bytes from 8.8.8.8: icmp_req=4 ttl=49 time=180 ms
64 bytes from 8.8.8.8: icmp_req=5 ttl=49 time=177 ms


traceroute -n 197.242.144.102

  1	192.168.1.1       	1 ms      	1 ms      	1 ms      	
  2	Request timed out 	*         	*         	*         	
  3	169.1.5.1         	19 ms     	17 ms     	17 ms     	
  4	169.1.5.1         	14 ms     	14 ms     	17 ms     	
  5	41.164.52.4       	16 ms     	15 ms     	15 ms     	
  6	196.223.22.3      	16 ms     	16 ms     	16 ms     	
  7	196.44.0.7        	17 ms     	19 ms     	18 ms     	
  8	196.44.31.6       	59 ms     	38 ms     	39 ms     	
  9	196.44.31.1       	38 ms     	
   	196.44.31.9       	38 ms     	39 ms     	
 10	196.31.220.1      	38 ms     	40 ms     	
   	196.31.220.2      	39 ms     	
 11	196.31.63.2       	40 ms     	38 ms     	39 ms     	
 12	196.30.42.1       	38 ms     	39 ms     	39 ms     	
 13	197.242.144.1     	40 ms     	39 ms     	39 ms     	


traceroute -n 8.8.8.8

  1	192.168.1.1       	1 ms      	1 ms      	
  2	Request timed out 	*         	*         	
  3	169.1.5.1         	18 ms     	31 ms     	
  4	169.1.5.1         	20 ms     	18 ms     	
  5	41.164.52.4       	24 ms     	16 ms     	
  6	172.18.1.1        	41 ms     	44 ms     	
  7	72.14.239.1       	224 ms
 
No issues with YT this end:

ah11.png

Although, google ping is still high:

Tracing route to google.co.za [216.58.223.35]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms ARCHER_D7 [192.168.1.1]
2 * * * Request timed out.
3 16 ms 14 ms 13 ms dbn-up2.ip.adsl.co.za [169.1.5.162]
4 14 ms 14 ms 14 ms dbn-in1.ip.adsl.co.za [169.1.5.204]
5 14 ms 14 ms 15 ms 41.162.84.192
6 21 ms 22 ms 23 ms 172.18.1.162
7 182 ms 181 ms 181 ms 72.14.194.206
8 182 ms 181 ms 182 ms 72.14.239.129
9 181 ms 181 ms 182 ms jnb01s08-in-f3.1e100.net [216.58.223.35]

Trace complete.
 
No issues with YT this end:

View attachment 388170

Although, google ping is still high:

Tracing route to google.co.za [216.58.223.35]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms ARCHER_D7 [192.168.1.1]
2 * * * Request timed out.
3 16 ms 14 ms 13 ms dbn-up2.ip.adsl.co.za [169.1.5.162]
4 14 ms 14 ms 14 ms dbn-in1.ip.adsl.co.za [169.1.5.204]
5 14 ms 14 ms 15 ms 41.162.84.192
6 21 ms 22 ms 23 ms 172.18.1.162
7 182 ms 181 ms 181 ms 72.14.194.206
8 182 ms 181 ms 182 ms 72.14.239.129
9 181 ms 181 ms 182 ms jnb01s08-in-f3.1e100.net [216.58.223.35]

Trace complete.
Google and YouTube with both show international ip addresses for the main url. Video is usually pulled from a local CDN in your case that video was pulled from r1--sn-hfxc-wocl.googlevideo.com wocl being the mweb cache cluster.
 
Streaming seems dead in the water, so to speak. Ping results:

HTML:
ping 197.242.144.102

64 bytes from 197.242.144.102: icmp_req=1 ttl=53 time=39 ms
64 bytes from 197.242.144.102: icmp_req=2 ttl=53 time=39 ms
64 bytes from 197.242.144.102: icmp_req=3 ttl=53 time=40 ms
64 bytes from 197.242.144.102: icmp_req=4 ttl=53 time=39 ms
64 bytes from 197.242.144.102: icmp_req=5 ttl=53 time=46 ms


ping 8.8.8.8

64 bytes from 8.8.8.8: icmp_req=1 ttl=49 time=178 ms
64 bytes from 8.8.8.8: icmp_req=2 ttl=49 time=182 ms
64 bytes from 8.8.8.8: icmp_req=3 ttl=49 time=176 ms
64 bytes from 8.8.8.8: icmp_req=4 ttl=49 time=180 ms
64 bytes from 8.8.8.8: icmp_req=5 ttl=49 time=177 ms


traceroute -n 197.242.144.102

  1	192.168.1.1       	1 ms      	1 ms      	1 ms      	
  2	Request timed out 	*         	*         	*         	
  3	169.1.5.1         	19 ms     	17 ms     	17 ms     	
  4	169.1.5.1         	14 ms     	14 ms     	17 ms     	
  5	41.164.52.4       	16 ms     	15 ms     	15 ms     	
  6	196.223.22.3      	16 ms     	16 ms     	16 ms     	
  7	196.44.0.7        	17 ms     	19 ms     	18 ms     	
  8	196.44.31.6       	59 ms     	38 ms     	39 ms     	
  9	196.44.31.1       	38 ms     	
   	196.44.31.9       	38 ms     	39 ms     	
 10	196.31.220.1      	38 ms     	40 ms     	
   	196.31.220.2      	39 ms     	
 11	196.31.63.2       	40 ms     	38 ms     	39 ms     	
 12	196.30.42.1       	38 ms     	39 ms     	39 ms     	
 13	197.242.144.1     	40 ms     	39 ms     	39 ms     	


traceroute -n 8.8.8.8

  1	192.168.1.1       	1 ms      	1 ms      	
  2	Request timed out 	*         	*         	
  3	169.1.5.1         	18 ms     	31 ms     	
  4	169.1.5.1         	20 ms     	18 ms     	
  5	41.164.52.4       	24 ms     	16 ms     	
  6	172.18.1.1        	41 ms     	44 ms     	
  7	72.14.239.1       	224 ms

Your Google DNS tracert looks strange.
The 6th IP is an intranet reserved IP, the last one is supposedly in the US :confused:.
I have the same though.

Code:
Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  ARCHER_D5 [192.168.0.1] < My Access Point
  2     1 ms     1 ms    <1 ms  home.gateway.pace.net [192.168.1.1] < My router
  3     *        *        *     Request timed out. < My exchange
  4    24 ms    23 ms    23 ms  cpt-up1.ip.adsl.co.za [169.1.5.105]
  5    24 ms    24 ms    24 ms  cpt-in1.ip.adsl.co.za [169.1.5.118]
  6    23 ms    23 ms    23 ms  cpt-net1.ip.adsl.co.za [169.1.5.128]
  7    24 ms    24 ms    23 ms  41.164.52.40
  8    45 ms    45 ms    45 ms  172.18.1.162
  9   197 ms   202 ms   208 ms  72.14.194.206
 10   215 ms   215 ms   219 ms  72.14.239.53
 11   218 ms   203 ms   199 ms  google-public-dns-a.google.com [8.8.8.8]

Trace complete.
 
I'll add my voice to the others - Streaming has been a complete mess this weekend. :(
Seems like there are major issues with international bandwidth.
Intl. speedtests are 4mbps on my 20mbps line. Local is fine at 19mbps.
 
Pretty much everything is 384 speed for me...

Anything using cloudfare bugs out all the time, including mybb
 
All is well in the friendly city. :)
10Mbps Capped account.

531496549.png

Capture_1080.JPG
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X