Afrihost Capped DSL Feedback

Mike43110 · Apr 25, 2017

Diablo is dead in the water, > 1kms is not really playable.

Code:

TRACEROUTE:
traceroute to 169.1.129.132 (169.1.129.132), 15 hops max, 60 byte packets
 1  Blizzard (Blizzard)  0.627 ms  0.696 ms  0.948 ms
 2  * * *
 3  37.244.10.102 (37.244.10.102)  0.774 ms  0.850 ms  0.889 ms
 4  37.244.10.34 (37.244.10.34)  0.741 ms  0.795 ms  0.874 ms
 5  xe-9-1-3.edge6.Amsterdam1.Level3.net (213.19.197.253)  0.559 ms  0.570 ms  0.582 ms
 6  * * *
 7  4.68.63.42 (4.68.63.42)  13.678 ms  13.689 ms  13.750 ms
 8  if-ae-11-2.tcore2.AV2-Amsterdam.as6453.net (80.231.152.25)  157.093 ms  157.157 ms  157.261 ms
 9  if-ae-14-2.tcore2.L78-London.as6453.net (80.231.131.160)  157.073 ms  157.080 ms  157.124 ms
10  if-ae-19-2.tcore1.SV8-Highbridge.as6453.net (80.231.138.21)  156.570 ms  156.532 ms  156.546 ms
11  if-ae-1-3.tcore1.PV9-Lisbon.as6453.net (80.231.158.29)  163.060 ms  163.087 ms  163.015 ms
12  if-ae-2-2.tcore2.PV9-Lisbon.as6453.net (80.231.158.6)  162.934 ms  163.032 ms  163.042 ms
13  if-ae-5-2.tcore1.KLT-Cape-Town.as6453.net (80.231.159.86)  162.949 ms  162.954 ms  162.945 ms
14  41.206.164.54 (41.206.164.54)  157.316 ms  156.343 ms  156.325 ms
15  41.164.52.41 (41.164.52.41)  180.774 ms  180.732 ms  180.724 ms


25/04/2017 20:05:05 UTC
--------------------

PING:
PING 169.1.129.132 (169.1.129.132) 56(84) bytes of data.

--- 169.1.129.132 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 4999ms



25/04/2017 20:05:05 UTC
--------------------

MTR:
HOST: Blizzard                  Loss%   Snt   Last   Avg  Best  Wrst StDev
  1. Blizzard                               0.0%    10    0.5   0.5   0.3   1.0   0.3
  2. ???                                         100.0    10    0.0   0.0   0.0   0.0   0.0
  3. 37.244.10.102                                0.0%    10    0.9   0.8   0.7   0.9   0.1
  4. 37.244.10.34                                 0.0%    10    0.8   1.3   0.8   2.8   0.7
  5. xe-9-1-3.edge6.Amsterdam1.Level3.net         0.0%    10    0.5   0.6   0.5   0.6   0.0
  6. ???                                         100.0    10    0.0   0.0   0.0   0.0   0.0
  7. 4.68.63.42                                   0.0%    10   13.6  14.6  13.4  25.3   3.7
  8. if-ae-11-2.tcore2.AV2-Amsterdam.as6453.net   0.0%    10  157.0 157.1 156.9 158.1   0.3
  9. if-ae-14-2.tcore2.L78-London.as6453.net      0.0%    10  156.8 157.1 156.8 157.8   0.4
 10. if-ae-19-2.tcore1.SV8-Highbridge.as6453.net  0.0%    10  156.6 157.4 156.5 164.5   2.5
 11. if-ae-1-3.tcore1.PV9-Lisbon.as6453.net       0.0%    10  163.0 163.2 163.0 164.2   0.3
 12. if-ae-2-2.tcore2.PV9-Lisbon.as6453.net       0.0%    10  166.7 163.8 162.9 167.1   1.6
 13. if-ae-5-2.tcore1.KLT-Cape-Town.as6453.net    0.0%    10  163.0 165.8 163.0 183.9   6.8
 14. 41.206.164.54                                0.0%    10  156.4 156.4 156.3 156.4   0.0
 15. 41.164.52.41                                 0.0%    10  163.3 165.0 163.3 179.4   5.1
 16. ???                                         100.0    10    0.0   0.0   0.0   0.0   0.0
 17. ???                                         100.0    10    0.0   0.0   0.0   0.0   0.0
 18. 169-1-129-1.ip.afrihost.co.za               10.0%    10  292.1 286.8 258.1 300.6  13.5
 19. ???                                         100.0    10    0.0   0.0   0.0   0.0   0.0


25/04/2017 20:05:05 UTC
--------------------

Kosmik · Apr 26, 2017

So this supposed 100gb for the 20gb capped accounts, what happened to it? I'm getting partial messages ie every other odd page that I'm capped and we've only used 20gb so far?

AfriGenie · Apr 26, 2017

Vixation said:
I am starting to feel like a broken record here. Ticket BSL-413-35004 is still not resolved. Latency every night to any euw related server is 300-400 and I have sent more tracer routes to Afrihost than I dare count.

Is it going to be an ongoing back and forth constantly as this issue has been there for months now and I never get a clear concrete answer to yes this is an issue that is going to be fixed or can't be fixed. I know I am not the only person experiencing this.

Can we please just get a clear answer and get support tickets looked at in a timely manner. If I had to leave any support ticket unresolved for a week I would get fired.

I've asked our Network Team to follow-up on your ticket and your traceroute results. They'll definitely get to the bottom of this!

AfriGenie · Apr 26, 2017

Mike43110 said:

Diablo is dead in the water, > 1kms is not really playable.

Code:

TRACEROUTE:
traceroute to 169.1.129.132 (169.1.129.132), 15 hops max, 60 byte packets
 1  Blizzard (Blizzard)  0.627 ms  0.696 ms  0.948 ms
 2  * * *
 3  37.244.10.102 (37.244.10.102)  0.774 ms  0.850 ms  0.889 ms
 4  37.244.10.34 (37.244.10.34)  0.741 ms  0.795 ms  0.874 ms
 5  xe-9-1-3.edge6.Amsterdam1.Level3.net (213.19.197.253)  0.559 ms  0.570 ms  0.582 ms
 6  * * *
 7  4.68.63.42 (4.68.63.42)  13.678 ms  13.689 ms  13.750 ms
 8  if-ae-11-2.tcore2.AV2-Amsterdam.as6453.net (80.231.152.25)  157.093 ms  157.157 ms  157.261 ms
 9  if-ae-14-2.tcore2.L78-London.as6453.net (80.231.131.160)  157.073 ms  157.080 ms  157.124 ms
10  if-ae-19-2.tcore1.SV8-Highbridge.as6453.net (80.231.138.21)  156.570 ms  156.532 ms  156.546 ms
11  if-ae-1-3.tcore1.PV9-Lisbon.as6453.net (80.231.158.29)  163.060 ms  163.087 ms  163.015 ms
12  if-ae-2-2.tcore2.PV9-Lisbon.as6453.net (80.231.158.6)  162.934 ms  163.032 ms  163.042 ms
13  if-ae-5-2.tcore1.KLT-Cape-Town.as6453.net (80.231.159.86)  162.949 ms  162.954 ms  162.945 ms
14  41.206.164.54 (41.206.164.54)  157.316 ms  156.343 ms  156.325 ms
15  41.164.52.41 (41.164.52.41)  180.774 ms  180.732 ms  180.724 ms


25/04/2017 20:05:05 UTC
--------------------

PING:
PING 169.1.129.132 (169.1.129.132) 56(84) bytes of data.

--- 169.1.129.132 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 4999ms



25/04/2017 20:05:05 UTC
--------------------

MTR:
HOST: Blizzard                  Loss%   Snt   Last   Avg  Best  Wrst StDev
  1. Blizzard                               0.0%    10    0.5   0.5   0.3   1.0   0.3
  2. ???                                         100.0    10    0.0   0.0   0.0   0.0   0.0
  3. 37.244.10.102                                0.0%    10    0.9   0.8   0.7   0.9   0.1
  4. 37.244.10.34                                 0.0%    10    0.8   1.3   0.8   2.8   0.7
  5. xe-9-1-3.edge6.Amsterdam1.Level3.net         0.0%    10    0.5   0.6   0.5   0.6   0.0
  6. ???                                         100.0    10    0.0   0.0   0.0   0.0   0.0
  7. 4.68.63.42                                   0.0%    10   13.6  14.6  13.4  25.3   3.7
  8. if-ae-11-2.tcore2.AV2-Amsterdam.as6453.net   0.0%    10  157.0 157.1 156.9 158.1   0.3
  9. if-ae-14-2.tcore2.L78-London.as6453.net      0.0%    10  156.8 157.1 156.8 157.8   0.4
 10. if-ae-19-2.tcore1.SV8-Highbridge.as6453.net  0.0%    10  156.6 157.4 156.5 164.5   2.5
 11. if-ae-1-3.tcore1.PV9-Lisbon.as6453.net       0.0%    10  163.0 163.2 163.0 164.2   0.3
 12. if-ae-2-2.tcore2.PV9-Lisbon.as6453.net       0.0%    10  166.7 163.8 162.9 167.1   1.6
 13. if-ae-5-2.tcore1.KLT-Cape-Town.as6453.net    0.0%    10  163.0 165.8 163.0 183.9   6.8
 14. 41.206.164.54                                0.0%    10  156.4 156.4 156.3 156.4   0.0
 15. 41.164.52.41                                 0.0%    10  163.3 165.0 163.3 179.4   5.1
 16. ???                                         100.0    10    0.0   0.0   0.0   0.0   0.0
 17. ???                                         100.0    10    0.0   0.0   0.0   0.0   0.0
 18. 169-1-129-1.ip.afrihost.co.za               10.0%    10  292.1 286.8 258.1 300.6  13.5
 19. ???                                         100.0    10    0.0   0.0   0.0   0.0   0.0


25/04/2017 20:05:05 UTC
--------------------

Those results look okay from what I can see. Could you maybe run a traceroute from your connection to Blizzard?

AfriGenie · Apr 26, 2017

Kosmik said:
So this supposed 100gb for the 20gb capped accounts, what happened to it? I'm getting partial messages ie every other odd page that I'm capped and we've only used 20gb so far?

You should most definitely have had the data allocated. Can you please PM me your username and I'll check what's going on.

AfriGenie · Apr 26, 2017

Johnatan56 said:

Ah sorry!

Code:

ping 212.58.244.23 -t

Pinging 212.58.244.23 with 32 bytes of data:
Reply from 212.58.244.23: bytes=32 time=149ms TTL=52
Reply from 212.58.244.23: bytes=32 time=148ms TTL=52
Reply from 212.58.244.23: bytes=32 time=148ms TTL=52
Reply from 212.58.244.23: bytes=32 time=148ms TTL=52
Reply from 212.58.244.23: bytes=32 time=150ms TTL=52
Reply from 212.58.244.23: bytes=32 time=148ms TTL=52
Reply from 212.58.244.23: bytes=32 time=148ms TTL=52
Reply from 212.58.244.23: bytes=32 time=148ms TTL=52
Reply from 212.58.244.23: bytes=32 time=148ms TTL=52
Reply from 212.58.244.23: bytes=32 time=148ms TTL=52
Reply from 212.58.244.23: bytes=32 time=148ms TTL=52
Reply from 212.58.244.23: bytes=32 time=148ms TTL=52
Reply from 212.58.244.23: bytes=32 time=149ms TTL=52
Reply from 212.58.244.23: bytes=32 time=148ms TTL=52
Reply from 212.58.244.23: bytes=32 time=148ms TTL=52
Reply from 212.58.244.23: bytes=32 time=148ms TTL=52
Reply from 212.58.244.23: bytes=32 time=148ms TTL=52
Reply from 212.58.244.23: bytes=32 time=148ms TTL=52
Reply from 212.58.244.23: bytes=32 time=148ms TTL=52

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

EDIT: For anyone reading, the above is for comparison to an Afrihost account, it's an alternative ISP.

Thanks for the results.

Kosmik · Apr 26, 2017

Pm sent

AfriGenie · Apr 26, 2017

Kosmik said:
Pm sent

Got it! And you have a reply.

GreatD7007 · Apr 26, 2017

AfriGenie said:
Got it! And you have a reply.

Hi AfriGenie. Please see my inbox, please mate. Many thanks

AfriGenie · Apr 26, 2017

GreatD7007 said:
Hi AfriGenie. Please see my inbox, please mate. Many thanks

Got your PM, thanks!

I'm checking on the sessions logs now.

GreatD7007 · Apr 26, 2017

AfriGenie said:
Got your PM, thanks!

I'm checking on the sessions logs now.

I replied. Please see message.

AfriGenie · Apr 26, 2017

GreatD7007 said:
I replied. Please see message.

Will do!

Hummercellc · Apr 26, 2017

YouTube in sy moêr tonight....
Buffering one way to nowhere.

BrendanMc · Apr 26, 2017

Shocking...

https://mybroadband.co.za/vb/showth...L-Feedback?p=19583736&viewfull=1#post19583736

That no-one even bothered to respond...

Pada · Apr 26, 2017

Is the shaping on the Afrihost shaped capped accounts really this bad that is unusable for playing online games at times?

For instance on my shaped capped account my lowest ping to the Quake Live server in CPT from Stellenbosch is 22ms compared to my WebAfrica account that has a ping of 49ms, BUT the Afrihost ping is all over the place and ICMP ping doesn't show how bad it actually is in game.

For instance when pinging the server, there is a lot of jitter:

Code:

Pinging 197.255.148.13 with 32 bytes of data:
Reply from 197.255.148.13: bytes=32 time=25ms TTL=58
Reply from 197.255.148.13: bytes=32 time=40ms TTL=58
Reply from 197.255.148.13: bytes=32 time=23ms TTL=58
Reply from 197.255.148.13: bytes=32 time=22ms TTL=58
Reply from 197.255.148.13: bytes=32 time=22ms TTL=58
Reply from 197.255.148.13: bytes=32 time=32ms TTL=58
Reply from 197.255.148.13: bytes=32 time=23ms TTL=58
Reply from 197.255.148.13: bytes=32 time=49ms TTL=58
Reply from 197.255.148.13: bytes=32 time=49ms TTL=58
Reply from 197.255.148.13: bytes=32 time=64ms TTL=58
Reply from 197.255.148.13: bytes=32 time=75ms TTL=58
Reply from 197.255.148.13: bytes=32 time=22ms TTL=58

Code:

Tracing route to 197.255.148.13 over a maximum of 30 hops

  1     *        *        *     Request timed out.
  2    89 ms   101 ms   108 ms  cpt-up1.ip.adsl.co.za [169.1.5.105]
  3    69 ms    43 ms    32 ms  169-1-21-66.ip.afrihost.co.za [169.1.21.66]
  4    23 ms    22 ms    23 ms  cpt-net1.ip.adsl.co.za [169.1.5.128]
  5    53 ms    47 ms    41 ms  adept.ixp.capetown [196.10.140.72]
  6    24 ms    24 ms    24 ms  v99.bb1.ter.cpt.adept.za.net [196.44.42.154]
  7    26 ms    23 ms    23 ms  197.255.148.13

Trace complete.

Where as using WebAfrica capped account, I have no jitter:

Code:

Pinging 197.255.148.13 with 32 bytes of data:
Reply from 197.255.148.13: bytes=32 time=50ms TTL=52
Reply from 197.255.148.13: bytes=32 time=50ms TTL=52
Reply from 197.255.148.13: bytes=32 time=49ms TTL=52
Reply from 197.255.148.13: bytes=32 time=49ms TTL=52
Reply from 197.255.148.13: bytes=32 time=49ms TTL=52
Reply from 197.255.148.13: bytes=32 time=49ms TTL=52

Code:

Tracing route to 197.255.148.13 over a maximum of 30 hops

  1     *        *        *     Request timed out.
  2    26 ms    86 ms    45 ms  cdsl1-ctn-vl2376-ipc.ip.isnet.net [196.38.72.206]
  3    27 ms    35 ms    41 ms  cdsl1-ctn-vl2376.ip.isnet.net [196.38.72.205]
  4    23 ms    24 ms    23 ms  196.35.115.128
  5    23 ms    25 ms    24 ms  mi-za-cpt-p7-te0-7-0-0.ip.isnet.net [168.209.2.12]
  6    48 ms    48 ms    48 ms  mi-za-umh-p8-ten-0-0-1-3-147.ip.isnet.net [168.209.0.24]
  7    48 ms    48 ms    49 ms  ar3-umh-be102.ip.isnet.net [168.209.93.248]
  8    48 ms    49 ms    50 ms  mi-za-umh-br3-te0-0-1-3-301.ip.isnet.net [168.209.39.66]
  9    50 ms    50 ms    50 ms  mi-za-umh-pe6-gi0-3-425.ip.isnet.net [196.14.217.129]
 10    49 ms    49 ms    48 ms  196.14.217.130
 11    51 ms    49 ms    49 ms  41.193.72.5
 12    49 ms    49 ms    49 ms  41.193.119.114
 13    48 ms    49 ms    48 ms  41.193.119.86
 14    48 ms    49 ms    48 ms  196.22.232.234
 15    50 ms    49 ms    50 ms  cpt-br-r1-vlan1026.frogfoot.net [41.85.1.89]
 16    49 ms    49 ms    53 ms  cpt-ter-cor-sw1-vlan2.frogfoot.net [196.1.56.100]
 17    49 ms    49 ms    49 ms  frogfoot.pe0.ter.cpt.adept.za.net [41.85.15.198]
 18    51 ms    51 ms    51 ms  v99.bb1.ter.cpt.adept.za.net [196.44.42.154]
 19    50 ms    49 ms    48 ms  197.255.148.13

Trace complete.

... and now like 15 minutes later after I reconnected to Afrihost, my ping (both ICMP & in game) is perfect:

Code:

Pinging 197.255.148.13 with 32 bytes of data:
Reply from 197.255.148.13: bytes=32 time=23ms TTL=58
Reply from 197.255.148.13: bytes=32 time=23ms TTL=58
Reply from 197.255.148.13: bytes=32 time=22ms TTL=58
Reply from 197.255.148.13: bytes=32 time=23ms TTL=58
Reply from 197.255.148.13: bytes=32 time=23ms TTL=58
Reply from 197.255.148.13: bytes=32 time=23ms TTL=58
Reply from 197.255.148.13: bytes=32 time=24ms TTL=58

BrendanMc · Apr 26, 2017

WTF is actually going on???? I cannot browse anything on my capped account. its just after 10pm and all im getting is dns errors unable to browse etc etc. Yet switching to my 1gb free account and no hassles.

Im completely sick of this absolute bs service

Hummercellc · Apr 26, 2017

BrendanMc said:
WTF is actually going on???? I cannot browse anything on my capped account. its just after 10pm and all im getting is dns errors unable to browse etc etc. Yet switching to my 1gb free account and no hassles.

Im completely sick of this absolute bs service

+1 very Intermittent here, same sh*t different day. The Afrihost Way™

BrendanMc · Apr 26, 2017

Hummercellc said:
+1 very Intermittent here, same sh*t different day. The Afrihost Way™

Agreed, i'm annoyed as hell.

Hummercellc · Apr 26, 2017

BrendanMc said:
Agreed, i'm annoyed as hell.

When there are no problems Afrihost is great, but lately it has been getting progressively worse more and more often, for longer periods.
I wish Gain would have the balls to own up to their network not having enough capacity and fix the problem.

moedawood · Apr 27, 2017

Have been using my AH account. Things look stable.

Code:

traceroute to afrihost.com (104.20.31.244), 30 hops max, 40 byte packets
 1  * * *
 2  dbn-up2.ip.adsl.co.za (169.1.5.174)  16.516 ms  14.84 ms  15.934 ms
 3  dbn-in1.ip.adsl.co.za (169.1.5.204)  15.865 ms  14.928 ms  14.129 ms
 4  169-1-21-32.ip.afrihost.co.za (169.1.21.32)  27.174 ms  27.231 ms  26.466 ms
 5  cloudflare.ixp.joburg (196.60.8.198)  26.725 ms  28.2 ms  37.333 ms
 6  104.20.31.244 (104.20.31.244)  26.697 ms  31.615 ms  27.964 ms

Code:

PING BBC.co.uk (212.58.246.78): 56 data bytes
64 bytes from 212.58.246.78: icmp_seq=0 ttl=38 time=199.1 ms
64 bytes from 212.58.246.78: icmp_seq=1 ttl=39 time=196.8 ms
64 bytes from 212.58.246.78: icmp_seq=2 ttl=39 time=197.4 ms
64 bytes from 212.58.246.78: icmp_seq=3 ttl=38 time=198.0 ms
64 bytes from 212.58.246.78: icmp_seq=4 ttl=39 time=197.3 ms

--- BBC.co.uk ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 196.8/197.7/199.1 ms

Afrihost Capped DSL Feedback

Senior Member

Honorary Master

Afrihost

Afrihost

Afrihost

Afrihost

Honorary Master

Afrihost

Senior Member

Afrihost

Senior Member

Afrihost

Expert Member

Expert Member

Executive Member

Expert Member

Expert Member

Expert Member

Expert Member

Senior Member