Afrihost New Network Feedback - Part 3

Status
Not open for further replies.
I understand that you are frustrated, but I'm going to ask that you please remain respectful towards our Support Agents, they are trying to assist you in getting your issue resolved, and calling them names is definitely not on.

You please need to train them better technically to not do the standard copy paste questions, then this kind of thing won't happen.

Further, my ticket CZN-480-86086 with regards to unacceptable Amazon Prime streaming experience on my 8mb line has not been responded to since my last reply Fri, 23 Dec 2016 10:17:57, is this normal?
 
You please need to train them better technically to not do the standard copy paste questions, then this kind of thing won't happen.

Further, my ticket CZN-480-86086 with regards to unacceptable Amazon Prime streaming experience on my 8mb line has not been responded to since my last reply Fri, 23 Dec 2016 10:17:57, is this normal?

Asking us to look into a reply that you are not happy with is entirely different from being disrespectful towards our Team. We are here to assist our Clients, but we need to remain respectful and polite towards each other. I can understand being frustrated or not happy with a reply but at no point should be disrepect each other.

It's not cool having to wait that long for a reply, I've asked our Team to look into this now and you should have a reply soon.

There shouldn't be any issues with Amazon Prime Video from what I know, but I'm not sure if there are local CDNs yet.

Which DNS servers are you using?
 
Asking us to look into a reply that you are not happy with is entirely different from being disrespectful towards our Team. We are here to assist our Clients, but we need to remain respectful and polite towards each other. I can understand being frustrated or not happy with a reply but at no point should be disrepect each other.

Understood and agreed. I guess some people here are more technical than some of the 1st line support staff, which creates a potential for frustration.

It's not cool having to wait that long for a reply, I've asked our Team to look into this now and you should have a reply soon.

There shouldn't be any issues with Amazon Prime Video from what I know, but I'm not sure if there are local CDNs yet.

Which DNS servers are you using?

I'm using OpenDNS, and have no issues if I switch to Netflix or Youtube streaming, so it's something to do with Amazon. I've also logged a support ticket with Amazon, they are saying from their side my bandwidth is 1-2MB, so something is not right. I would understand if they don't have a local CDN, but surely a 8MB line and capped account should not be that disappointing? Also, if I run a speedtest while streaming Amazon it still gets about 5-6mb, so there is lots of capacity on the line left, it cannot be an exchange issue, the fact that Youtube and Netflix works backs that up. Does Netflix have a SA CDN?
 
Understood and agreed. I guess some people here are more technical than some of the 1st line support staff, which creates a potential for frustration.



I'm using OpenDNS, and have no issues if I switch to Netflix or Youtube streaming, so it's something to do with Amazon. I've also logged a support ticket with Amazon, they are saying from their side my bandwidth is 1-2MB, so something is not right. I would understand if they don't have a local CDN, but surely a 8MB line and capped account should not be that disappointing? Also, if I run a speedtest while streaming Amazon it still gets about 5-6mb, so there is lots of capacity on the line left, it cannot be an exchange issue, the fact that Youtube and Netflix works backs that up. Does Netflix have a SA CDN?

I'm pretty sure Netflix content is being served locally, I'll get an Amazon Trial account and do a bit of testing on my side as well.
 
I'm pretty sure Netflix content is being served locally, I'll get an Amazon Trial account and do a bit of testing on my side as well.

Thats a very good reason to watch The Grand Tour at work lol :D
 
What!? Where?! I would never do that... :whistle:

PS: The Namibia Special is awesome!

Yep. Namibia Special felt like the old topgear specials. I wasn't very impressed by the American or Celebrity Brain Crash or w/e that crap is called.

I actually thought Grand Tour would be more like the Namibia Episode because of the name. Would have been much better, in my opinion. But I can also understand that it might not be financially feasible, as the specials on top gear were the most expensive to produce.

Oh well, they got me hooked. That's all that counts.
 
Yep. Namibia Special felt like the old topgear specials. I wasn't very impressed by the American or Celebrity Brain Crash or w/e that crap is called.

I actually thought Grand Tour would be more like the Namibia Episode because of the name. Would have been much better, in my opinion. But I can also understand that it might not be financially feasible, as the specials on top gear were the most expensive to produce.

Oh well, they got me hooked. That's all that counts.

Couldn't have said it better. :)
 
P address or host name:
www.afrihost.co.za
Go

--- PING www.afrihost.co.za (41.86.112.68) 56(84) bytes of data. ---
64 bytes from 41.86.112.68: icmp_seq=1 ttl=49 time=199 ms
64 bytes from 41.86.112.68: icmp_seq=2 ttl=49 time=198 ms
64 bytes from 41.86.112.68: icmp_seq=3 ttl=49 time=198 ms
64 bytes from 41.86.112.68: icmp_seq=4 ttl=49 time=198 ms


--- www.afrihost.co.za ping statistics ---


packets transmitted 4
received 4
packet loss 0 %
time 3004 ms



--- Round Trip Time (rtt) ---


min 198.782 ms
avg 198.891 ms
max 199.164 ms
mdev 0.353 ms




1 * * *


2 core21.hetzner.de 213.239.229.129 0.227 ms 0.241 ms
core22.hetzner.de 213.239.229.133 0.252 ms


3 core11.hetzner.de 213.239.245.221 4.220 ms 4.236 ms 4.236 ms


4 juniper4.ffm.hetzner.de 213.239.245.10 4.856 ms 4.872 ms
juniper5.rz2.hetzner.de 213.239.229.166 2.780 ms


5 ae5-710.nbg40.core-backbone.com 81.95.15.5 de 15.784 ms 15.790 ms 15.790 ms


6 ae6-2077.lon10.core-backbone.com 5.56.18.2 de 15.155 ms 15.989 ms 15.201 ms


7 * * *


8 be-4-778-thd-p-2.optinet.net 176.67.177.146 203.303 ms 205.310 ms
be-9-777-thd-p-2.optinet.net 176.67.177.130 196.948 ms


9 be-69-thd-p-2.optinet.net 176.67.177.162 203.746 ms 203.756 ms
be-69-thd-p-1.optinet.net 176.67.177.161 199.156 ms


10 s2-po0-3-2-0.vic-p-1.optinet.net 197.80.5.6 205.184 ms
s1-po0-3-0-0.vic-p-2.optinet.net 197.80.5.8 198.650 ms
s2-po0-3-2-0.vic-p-1.optinet.net 197.80.5.6 205.184 ms


11 197-84-4-100.cpt.mweb.co.za 197.84.4.100 201.139 ms
197-84-4-101.cpt.mweb.co.za 197.84.4.101 202.295 ms
197-84-4-100.cpt.mweb.co.za 197.84.4.100 201.139 ms


12 101.te0-0-2-0.vic-tr-1.optinet.net 197.80.7.4 202.885 ms 202.861 ms 202.354 ms


13 197-81-226-77.jhb.mweb.co.za 197.81.226.77 199.601 ms 199.718 ms 199.084 ms


14 197-81-226-53.jhb.mweb.co.za 197.81.226.53 202.351 ms 204.074 ms 199.951 ms


15 197-81-229-2.jhb.mweb.co.za 197.81.229.2 198.734 ms 199.205 ms 199.287 ms


16 197-81-229-9.jhb.mweb.co.za 197.81.229.9 201.795 ms 199.301 ms 199.389 ms


17 41-86-112-68.mweb.co.za 41.86.112.68 za 200.357 ms
 
Why is the ping so kuk now?


C:\Users\> ping afrihost.co.za

Pinging afrihost.co.za [41.86.112.68] with 32 bytes of data:
Reply from 41.86.112.68: bytes=32 time=31ms TTL=42
Reply from 41.86.112.68: bytes=32 time=31ms TTL=42
Reply from 41.86.112.68: bytes=32 time=30ms TTL=42
Reply from 41.86.112.68: bytes=32 time=31ms TTL=42

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




C:\Users\ ping www.google.com

Pinging www.google.com [169.1.2.92] with 32 bytes of data:
Reply from 169.1.2.92: bytes=32 time=26ms TTL=58
Reply from 169.1.2.92: bytes=32 time=9ms TTL=58
Reply from 169.1.2.92: bytes=32 time=9ms TTL=58
Reply from 169.1.2.92: bytes=32 time=9ms TTL=58

Ping statistics for 169.1.2.92:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 9ms, Maximum = 26ms, Average = 13ms

C:\Users\> ping www.apple.com

Pinging e6858.dsce9.akamaiedge.net [104.108.183.93] with 32 bytes of data:
Reply from 104.108.183.93: bytes=32 time=184ms TTL=44
Reply from 104.108.183.93: bytes=32 time=182ms TTL=44
Reply from 104.108.183.93: bytes=32 time=182ms TTL=44
Reply from 104.108.183.93: bytes=32 time=181ms TTL=44

Ping statistics for 104.108.183.93:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 181ms, Maximum = 184ms, Average = 182ms
 
Last edited:
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X