Afrihost New Network Feedback - Part 2

Status
Not open for further replies.
AfriGuy said:
Any ETA on that PM?
I got the impression from your posts this was quite urgent.
Click to expand...
jmacc said:
I have sent you the ticket ref via PM.
Click to expand...
AfriGuy said:
As discussed via PM, your query is now with our Critical Care team who will be your point of contact and will see the issue through with you until resolved.

Cheers.
Click to expand...


After rushing back to my office today just so that I can get the ticket reference to AfriGuy, I have not received a single email or follow up call from the Afrihost Critical Care team to address this long standing Windows Update and Apple App Store shaping issues on capped accounts.
 
Last edited:
jmacc said:
After rushing back to my office today just so that I can get the ticket reference to AfriGuy, I have not received a single email or follow up call from the Afrihost Critical Care team to address this long standing Windows Update and Apple App Store shaping issues on capped accounts.
Click to expand...

Funny how you are only one with that issue.
 
jmacc said:
After rushing back to my office today just so that I can get the ticket reference to AfriGuy, I have not received a single email or follow up call from the Afrihost Critical Care team to address this long standing Windows Update and Apple App Store shaping issues on capped accounts.
Click to expand...

As per your request, you wanted us to thoroughly review the query. This is what our team are doing and will be in touch when they have feedback.
 
Rickster said:
Funny how you are only one with that issue.
Click to expand...

There is no way that others do not have this issue. Please read my posts carefully and then come back and tell me how you arrive at this conclusion.
 
jmacc said:
There is no way that others do not have this issue. Please read my posts carefully and then come back and tell me how you arrive at this conclusion.
Click to expand...

As per my numerous replies to you earlier, if this was a common issue we'd see a lot of queries around it. There simply aren't.
Please wait for feedback from our Critical Care team.
 
AfriGuy said:
As per your request, you wanted us to thoroughly review the query. This is what our team are doing and will be in touch when they have feedback.
Click to expand...

They've been reviewing this issue since July. You've even confirmed the ticket is in a Management Queue. I was under the impression that your continuous prompts for the ticket ref would result in some action today. One would assume that there would at least be some requests to do relevant tests.
 
jmacc said:
They've been reviewing this issue since July. You've even confirmed the ticket is in a Management Queue. I was under the impression that your continuous prompts for the ticket ref would result in some action today. One would assume that there would at least be some requests to do relevant tests.
Click to expand...

Our Critical Care team haven't, no.
We're following your instruction and reviewing your account, ticket history and data thoroughly before getting in touch.

Have a good evening.
 
AfriGuy said:
As per my numerous replies to you earlier, if this was a common issue we'd see a lot of queries around it. There simply aren't.
Please wait for feedback from our Critical Care team.
Click to expand...

I have already explained in detail why you do not see more of these issues. Many people including myself will try and work around these issues. That is until applying monthly updates becomes like watching paint dry. I will not be wasting my time on these forums if there was no issue.
How long should I wait for a response from critical care?
 
Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=20ms TTL=63
Reply from 155.239.255.250: bytes=32 time=19ms TTL=63
Reply from 155.239.255.250: bytes=32 time=19ms TTL=63
Reply from 155.239.255.250: bytes=32 time=22ms TTL=63

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

Pinging putlocker.is [104.23.196.8] with 32 bytes of data:
Reply from 104.23.196.8: bytes=32 time=59ms TTL=52
Reply from 104.23.196.8: bytes=32 time=50ms TTL=52
Reply from 104.23.196.8: bytes=32 time=34ms TTL=52
Reply from 104.23.196.8: bytes=32 time=39ms TTL=52

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

Pinging putlocker.is [104.23.196.8] with 32 bytes of data:
Reply from 104.23.196.8: bytes=32 time=35ms TTL=52
Reply from 104.23.196.8: bytes=32 time=29ms TTL=52
Reply from 104.23.196.8: bytes=32 time=30ms TTL=52
Reply from 104.23.196.8: bytes=32 time=40ms TTL=52

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

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

1 1 ms 1 ms 1 ms myrouter.Home [192.168.1.1]
2 * * * Request timed out.
3 23 ms 24 ms 21 ms dbn-up2.ip.adsl.co.za [169.1.5.174]
4 25 ms 22 ms 21 ms dbn-in1.ip.adsl.co.za [169.1.5.204]
5 22 ms 20 ms 22 ms 41.162.84.192
6 28 ms 27 ms 28 ms 172.18.1.162
7 34 ms 34 ms 30 ms cloudflare.ixp.joburg [196.46.25.198]
8 46 ms 31 ms 32 ms 104.20.30.244

Trace complete.

streaming is not looking good at all. Really really struggling.
Streaming from Putlocker. Please check if there's any issue at the moment
 
I am more and more frequently getting time out errors to Netflix

Ping:
Code: 
C:\WINDOWS\system32>ping netflix.com

Pinging netflix.com [54.171.21.76] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 54.171.21.76:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\WINDOWS\system32>ping movies.netflix.com

Pinging movies.eu-west-1.prodaa.netflix.com [52.17.3.133] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 52.17.3.133:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\WINDOWS\system32>ping youtube.com

Pinging youtube.com [169.1.2.86] with 32 bytes of data:
Reply from 169.1.2.86: bytes=32 time=24ms TTL=58
Reply from 169.1.2.86: bytes=32 time=21ms TTL=58
Reply from 169.1.2.86: bytes=32 time=22ms TTL=58
Reply from 169.1.2.86: bytes=32 time=21ms TTL=58

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

C:\WINDOWS\system32>ping afrihost.com

Pinging afrihost.com [104.20.30.244] with 32 bytes of data:
Reply from 104.20.30.244: bytes=32 time=44ms TTL=52
Reply from 104.20.30.244: bytes=32 time=44ms TTL=52
Reply from 104.20.30.244: bytes=32 time=44ms TTL=52
Reply from 104.20.30.244: bytes=32 time=44ms TTL=52

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

C:\WINDOWS\system32>ping google.com

Pinging google.com [169.1.2.85] with 32 bytes of data:
Reply from 169.1.2.85: bytes=32 time=24ms TTL=58
Reply from 169.1.2.85: bytes=32 time=22ms TTL=58
Reply from 169.1.2.85: bytes=32 time=22ms TTL=58
Reply from 169.1.2.85: bytes=32 time=24ms TTL=58

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

C:\WINDOWS\system32>

Trace route:

Code: 
C:\WINDOWS\system32>tracert netflix.com

Tracing route to netflix.com [52.210.113.179]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.0.2
  2     *        *        *     Request timed out.
  3    55 ms    54 ms    50 ms  cpt-up1.ip.adsl.co.za [169.1.5.105]
  4    24 ms    23 ms    22 ms  cpt-in1.ip.adsl.co.za [169.1.5.118]
  5    56 ms   136 ms    48 ms  cpt-net1.ip.adsl.co.za [169.1.5.128]
  6    24 ms    23 ms    22 ms  41.164.52.40
  7    55 ms    57 ms    77 ms  ix-ae-7-0.tcore2.KLT-Cape-Town.as6453.net [41.206.165.25]
  8   179 ms   177 ms   176 ms  if-ae-2-2.tcore1.KLT-Cape-Town.as6453.net [41.206.164.253]
  9   215 ms   204 ms   199 ms  if-ae-5-20.tcore2.PV9-Lisbon.as6453.net [80.231.159.61]
 10   192 ms   193 ms   196 ms  if-ae-2-2.tcore1.PV9-Lisbon.as6453.net [80.231.158.5]
 11   171 ms   170 ms   174 ms  if-ae-1-3.tcore1.SV8-Highbridge.as6453.net [80.231.158.30]
 12   167 ms   169 ms   166 ms  if-ae-2-2.tcore2.SV8-Highbridge.as6453.net [80.231.139.1]
 13   170 ms   171 ms   171 ms  if-ae-11-2.tcore1.L78-London.as6453.net [80.231.139.42]
 14   164 ms   165 ms   165 ms  if-ae-17-2.tcore1.LDN-London.as6453.net [80.231.130.130]
 15   171 ms   171 ms   171 ms  195.219.83.186
 16   166 ms   165 ms   166 ms  ae-3.r02.londen05.uk.bb.gin.ntt.net [129.250.2.119]
 17   230 ms   222 ms   227 ms  82.112.115.162
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20   178 ms   175 ms   177 ms  176.32.106.146
 21   176 ms   175 ms   175 ms  176.32.106.29
 22   175 ms   175 ms   175 ms  178.236.0.189
 23   181 ms   179 ms   179 ms  178.236.0.196
 24   177 ms   175 ms   176 ms  176.32.107.11
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.

Trace complete.

C:\WINDOWS\system32>

Whats happening here, can you help Mr Afriman?
 
high trace international from pe caped account
ping bras

Ping has started…

PING bras.afrihost.com (155.239.255.250): 56 data bytes
64 bytes from 155.239.255.250: icmp_seq=0 ttl=63 time=23.413 ms
64 bytes from 155.239.255.250: icmp_seq=1 ttl=63 time=22.842 ms
64 bytes from 155.239.255.250: icmp_seq=2 ttl=63 time=22.764 ms
64 bytes from 155.239.255.250: icmp_seq=3 ttl=63 time=22.436 ms
64 bytes from 155.239.255.250: icmp_seq=4 ttl=63 time=22.178 ms
64 bytes from 155.239.255.250: icmp_seq=5 ttl=63 time=22.726 ms
64 bytes from 155.239.255.250: icmp_seq=6 ttl=63 time=22.109 ms
64 bytes from 155.239.255.250: icmp_seq=7 ttl=63 time=22.741 ms
64 bytes from 155.239.255.250: icmp_seq=8 ttl=63 time=22.401 ms
64 bytes from 155.239.255.250: icmp_seq=9 ttl=63 time=22.545 ms

--- bras.afrihost.com ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 22.109/22.616/23.413/0.356 ms


sipgate

trace sipgate afrihost 1509.jpg

youtube

youtubee afrihost 1509.jpg
 
jmacc said:
I have already explained in detail why you do not see more of these issues. Many people including myself will try and work around these issues. That is until applying monthly updates becomes like watching paint dry. I will not be wasting my time on these forums if there was no issue.
How long should I wait for a response from critical care?
Click to expand...

Tomorrow.
 
AfriGuy said:
Our Critical Care team haven't, no.
We're following your instruction and reviewing your account, ticket history and data thoroughly before getting in touch.

Have a good evening.
Click to expand...

I did not instruct you to review my account, ticket history and data.
The primary request is to resolve the update shaping issue. In doing this my request was to stop doing tests which have no technical merit. I also requested that a capable person be assigned to work this case with me. The window of opportunity is running out. If we miss this window, come next month we will have another repeat. This I will not do. Then I will cancel this service. And before you think this is not a problem, we have more business than this service with Afrihost. We have also generated a substantial amount of business for Afrihost in terms of client referrals. We will gladly move this business else where. Contrary to what you and others think about my posts on this forum, I want Afrihost to succeed because we also have skin in this game. However my patience is almost depleted.
 
jmacc said:
I did not instruct you to review my account, ticket history and data.
The primary request is to resolve the update shaping issue. In doing this my request was to stop doing tests which have no technical merit. I also requested that a capable person be assigned to work this case with me. The window of opportunity is running out. If we miss this window, come next month we will have another repeat. This I will not do. Then I will cancel this service. And before you think this is not a problem, we have more business than this service with Afrihost. We have also generated a substantial amount of business for Afrihost in terms of client referrals. We will gladly move this business else where. Contrary to what you and others think about my posts on this forum, I want Afrihost to succeed because we also have skin in this game. However my patience is almost depleted.
Click to expand...

I have already replied to all of your queries. Critical Care will be in touch further.
 
So not sure what just happened. Afrihost account will no longer connect in router, nor does any other ISP. Getting "no response". The line is synced at its speed and I'm getting SNR and attenuation values.

I assume Telkom is playing games...?
 
Vorastra said:
So not sure what just happened. Afrihost account will no longer connect in router, nor does any other ISP. Getting "no response". The line is synced at its speed and I'm getting SNR and attenuation values.

I assume Telkom is playing games...?
Click to expand...

Sounds like a line issue :(
Drop me a PM with your DSL username and I'll check what's happening here.
 
My line has been completely dead since 8pm as well. Can't connect at all.. Second day in a row this has happened
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X