Afrihost New Network Feedback - Part 2

Vio · Oct 9, 2016

"Gary - Critical Care Crew" tried to help me last year - after 3 months of back and forth they couldn't help me with this exact latency issue.

Soon they will ask you to be available in the period where the issues occur so they can run "tests".

kohlhtor · Oct 9, 2016

Vio said:
"Gary - Critical Care Crew" tried to help me last year - after 3 months of back and forth they couldn't help me with this exact latency issue.

Soon they will ask you to be available in the period where the issues occur so they can run "tests".

My ticket is running for 3 month same as last year after 4 month no problem afrihost admit the network was broken

kohlhtor · Oct 9, 2016

Vio said:
"Gary - Critical Care Crew" tried to help me last year - after 3 months of back and forth they couldn't help me with this exact latency issue.

Soon they will ask you to be available in the period where the issues occur so they can run "tests".

He can not even read my trace

Rickster · Oct 9, 2016

kohlhtor said:
We have no problem

For comparison:

Code:

PS C:\WINDOWS\system32> tracert youtube.co.za

Tracing route to youtube.co.za [216.58.223.14]
over a maximum of 30 hops:

  1     1 ms    <1 ms    <1 ms  192.168.0.1
  2     *        *        *     Request timed out.
  3    10 ms     9 ms    10 ms  jhb-up7.ip.adsl.co.za [169.1.5.6]
  4    11 ms    12 ms    10 ms  jhb-net1.ip.adsl.co.za [169.1.5.52]
  5    11 ms     9 ms     9 ms  169-1-5-243.ip.afrihost.co.za [169.1.5.243]
  6    10 ms    10 ms    11 ms  72.14.237.239
  7    11 ms    11 ms    10 ms  jnb01s07-in-f14.1e100.net [216.58.223.14]

Trace complete.



Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms 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 = 9ms, Maximum = 13ms, Average = 10ms

Kaito · Oct 9, 2016

8Mb line. Cape Town
Video streaming is struggling, download speeds are below 100kb/s.
This time, my latency is high.

1 1 ms 1 ms 4 ms 10.0.0.2
2 * * * Request timed out.
3 24 ms 20 ms 36 ms cpt-up1.ip.adsl.co.za [169.1.5.105]
4 122 ms 119 ms 121 ms cpt-up2.ip.adsl.co.za [169.1.5.106]
5 124 ms 124 ms 117 ms 169-1-5-132.ip.afrihost.co.za [169.1.5.132]

Edit: Using afrihost's dns. Capped Acc.

kohlhtor · Oct 9, 2016

Rickster said:

For comparison:

Code:

PS C:\WINDOWS\system32> tracert youtube.co.za

Tracing route to youtube.co.za [216.58.223.14]
over a maximum of 30 hops:

  1     1 ms    <1 ms    <1 ms  192.168.0.1
  2     *        *        *     Request timed out.
  3    10 ms     9 ms    10 ms  jhb-up7.ip.adsl.co.za [169.1.5.6]
  4    11 ms    12 ms    10 ms  jhb-net1.ip.adsl.co.za [169.1.5.52]
  5    11 ms     9 ms     9 ms  169-1-5-243.ip.afrihost.co.za [169.1.5.243]
  6    10 ms    10 ms    11 ms  72.14.237.239
  7    11 ms    11 ms    10 ms  jnb01s07-in-f14.1e100.net [216.58.223.14]

Trace complete.



Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms 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 = 9ms, Maximum = 13ms, Average = 10ms

This is jhb the problem is Cape town

Johnatan56 · Oct 9, 2016

Cape Town, 2307ms latency in-game. Yay. Packet loss started way earlier as well.

Vio · Oct 9, 2016

kohlhtor said:
This is jhb the problem is Cape town

Got no problem on my backup WebAfrica account. So it's Afrihost CT network as per usual...

Rickster · Oct 9, 2016

Sounds like a link failure

Isengard · Oct 9, 2016

Vio said:
Got no problem on my backup WebAfrica account. So it's Afrihost CT network as per usual...

Same thing here total disaster atm, gonna have to stay on Webafrica for now...

Vio · Oct 9, 2016

Rickster said:
Sounds like a link failure

Nooooo this is working as intended...

You can't trust a word they say.

Hummercellc · Oct 9, 2016

KZN, all streaming is buffering (YouTube, Netflix) and international latency over 1000ms... Facebook loading slowly, Afrihost please fix your effing network this has been ongoing for months. Critical care are an absolute waste of time.

electrofreeze · Oct 9, 2016

definitely the worst night so far started at 6pm internet is much to slow for working but it works properly with other isp

standerr · Oct 9, 2016

Clearly something major going on

All good at 6pm

Code:

Tracing route to www.news24.com [41.86.110.200]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  10.1.0.254 
  2    <1 ms    <1 ms    <1 ms  10.100.0.1 
  3     *        *        *     Request timed out.
  4    24 ms    22 ms    23 ms  cpt-rx2.ip.adsl.co.za [169.1.5.82] 
  5    22 ms    22 ms    23 ms  169-1-5-132.ip.afrihost.co.za [169.1.5.132] 
  6    28 ms    28 ms    28 ms  optinet.ixp.capetown [196.10.140.15] 
  7    27 ms    27 ms    28 ms  bu-ether1.cpt-p-1.optinet.net [197.84.7.33] 
  8    19 ms    20 ms    19 ms  vl12.cpt-hscore-2.optinet.net [197.84.5.254] 
  9    20 ms    19 ms    21 ms  vp-02-14.bb.ctn.c27.za.net [196.28.178.70] 
 10    19 ms    19 ms    19 ms  gig5-2-cpt-opt-65-1.optinet.net [196.41.133.166] 
 11    20 ms    19 ms    20 ms  OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6] 
 12    22 ms    20 ms    22 ms  197-84-208-146.cpt.mweb.co.za [197.84.208.146] 
 13    26 ms    26 ms    26 ms  41-86-110-200.mweb.co.za [41.86.110.200] 

Trace complete.

6:30pm slightly higher

Code:

Tracing route to www.news24.com [41.86.110.200]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  10.1.0.254 
  2    <1 ms    <1 ms    <1 ms  10.100.0.1 
  3     *        *        *     Request timed out.
  4    46 ms    47 ms    48 ms  cpt-rx2.ip.adsl.co.za [169.1.5.82] 
  5    77 ms    79 ms    60 ms  169-1-5-132.ip.afrihost.co.za [169.1.5.132] 
  6    63 ms    65 ms    66 ms  optinet.ixp.capetown [196.10.140.15] 
  7    59 ms    59 ms    58 ms  bu-ether1.cpt-p-1.optinet.net [197.84.7.33] 
  8    19 ms    19 ms    19 ms  vl12.cpt-hscore-2.optinet.net [197.84.5.254] 
  9    20 ms    20 ms    20 ms  vp-02-14.bb.ctn.c27.za.net [196.28.178.70] 
 10    19 ms    20 ms    20 ms  gig5-2-cpt-opt-65-1.optinet.net [196.41.133.166] 
 11    20 ms    20 ms    20 ms  OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6] 
 12    21 ms    24 ms    20 ms  197-84-208-146.cpt.mweb.co.za [197.84.208.146] 
 13    71 ms    69 ms    68 ms  41-86-110-200.mweb.co.za [41.86.110.200] 

Trace complete.

Then from 7:30pm this

Code:

Tracing route to www.news24.com [41.86.110.200]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  10.1.0.254 
  2    <1 ms    <1 ms    <1 ms  10.100.0.1 
  3     *        *        *     Request timed out.
  4   118 ms   121 ms     *     cpt-rx2.ip.adsl.co.za [169.1.5.82] 
  5   121 ms   119 ms   142 ms  169-1-5-132.ip.afrihost.co.za [169.1.5.132] 
  6   119 ms   117 ms   117 ms  optinet.ixp.capetown [196.10.140.15] 
  7   119 ms   121 ms   123 ms  bu-ether1.cpt-p-1.optinet.net [197.84.7.33] 
  8    20 ms    20 ms    20 ms  vl12.cpt-hscore-2.optinet.net [197.84.5.254] 
  9    22 ms    20 ms    20 ms  vp-02-14.bb.ctn.c27.za.net [196.28.178.70] 
 10    88 ms    61 ms    20 ms  gig5-2-cpt-opt-65-1.optinet.net [196.41.133.166] 
 11    22 ms    20 ms    22 ms  OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6] 
 12    22 ms    22 ms    21 ms  197-84-208-146.cpt.mweb.co.za [197.84.208.146] 
 13   120 ms   120 ms   118 ms  41-86-110-200.mweb.co.za [41.86.110.200] 

Trace complete.

bras all good

Code:

Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=17ms TTL=62
Reply from 155.239.255.250: bytes=32 time=18ms TTL=62
Reply from 155.239.255.250: bytes=32 time=18ms TTL=62
Reply from 155.239.255.250: bytes=32 time=19ms TTL=62
Reply from 155.239.255.250: bytes=32 time=18ms TTL=62
Reply from 155.239.255.250: bytes=32 time=18ms TTL=62
Reply from 155.239.255.250: bytes=32 time=18ms TTL=62
Reply from 155.239.255.250: bytes=32 time=17ms TTL=62
Reply from 155.239.255.250: bytes=32 time=18ms TTL=62
Reply from 155.239.255.250: bytes=32 time=18ms TTL=62

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

standerr · Oct 9, 2016

My good friend android play store looking like this

6pm all good

Code:

Tracing route to play.l.google.com [216.58.223.46]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  10.1.0.254 
  2    <1 ms    <1 ms    <1 ms  10.100.0.1 
  3     *        *        *     Request timed out.
  4    42 ms    43 ms    42 ms  cpt-rx2.ip.adsl.co.za [169.1.5.82] 
  5    35 ms    38 ms    38 ms  169-1-5-132.ip.afrihost.co.za [169.1.5.132] 
  6    43 ms    43 ms    41 ms  41.164.52.42 
  7    52 ms    50 ms    50 ms  172.18.1.162 
  8    60 ms    61 ms    86 ms  72.14.194.206 
  9    60 ms    57 ms    55 ms  72.14.239.129 
 10    52 ms    51 ms    52 ms  jnb01s08-in-f46.1e100.net [216.58.223.46] 

Trace complete.

7pm not so much

Code:

Tracing route to play.l.google.com [216.58.223.46]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  10.1.0.254 
  2    <1 ms    <1 ms    <1 ms  10.100.0.1 
  3     *        *        *     Request timed out.
  4     *      428 ms   449 ms  cpt-rx2.ip.adsl.co.za [169.1.5.82] 
  5   415 ms   432 ms   444 ms  169-1-5-132.ip.afrihost.co.za [169.1.5.132] 
  6   409 ms   340 ms   357 ms  41.164.52.42 
  7   498 ms   525 ms   578 ms  172.18.1.162 
  8   233 ms   214 ms   244 ms  72.14.194.206 
  9   348 ms   348 ms   389 ms  72.14.239.129 
 10   541 ms   442 ms   427 ms  jnb01s08-in-f46.1e100.net [216.58.223.46] 

Trace complete.

Johnatan56 · Oct 9, 2016

/clap

image132 · Oct 9, 2016

Afrihost

Telkom

Afrihost

Tracing route to bbc.co.uk [212.58.244.23]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1]
2 * * * Request timed out.
3 122 ms 122 ms 122 ms cpt-up2.ip.adsl.co.za [169.1.5.106]
4 120 ms 120 ms 124 ms 169-1-5-132.ip.afrihost.co.za [169.1.5.132]
5 117 ms 118 ms 120 ms 41.164.52.42
6 177 ms 177 ms 201 ms ix-ae-7-0.tcore2.KLT-Cape-Town.as6453.net [41.206.165.25]
7 336 ms 325 ms * if-ae-2-2.tcore1.KLT-Cape-Town.as6453.net [41.206.164.253]
8 312 ms 324 ms 326 ms if-ae-5-40.tcore2.PV9-Lisbon.as6453.net [80.231.159.89]
9 315 ms 300 ms 282 ms if-ae-2-2.tcore1.PV9-Lisbon.as6453.net [80.231.158.5]
10 326 ms 311 ms * if-ae-1-3.tcore1.SV8-Highbridge.as6453.net [80.231.158.30]
11 315 ms 316 ms 322 ms if-ae-2-2.tcore2.SV8-Highbridge.as6453.net [80.231.139.1]
12 314 ms 316 ms 316 ms if-ae-11-2.tcore1.L78-London.as6453.net [80.231.139.42]
13 328 ms 325 ms 325 ms if-ae-17-2.tcore1.LDN-London.as6453.net [80.231.130.130]
14 * * 329 ms 195.219.83.102
15 * * * Request timed out.
16 320 ms 327 ms 320 ms unknown.Level3.net [212.187.139.230]
17 * * * Request timed out.
18 313 ms 321 ms 318 ms ae0.er01.telhc.bbc.co.uk [132.185.254.109]
19 320 ms 312 ms * 132.185.255.148
20 318 ms 325 ms 313 ms 212.58.244.23

Telkom
C:\Users\Chris>tracert bbc.co.uk

Tracing route to bbc.co.uk [212.58.244.23]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1]
2 * * * Request timed out.
3 25 ms 23 ms 24 ms ipc-2-up.south.dsl.telkomsa.net [105.226.0.22]
4 23 ms 21 ms 22 ms ipc-aggr-2.south.dsl.telkomsa.net [105.226.0.57]
5 21 ms 22 ms 21 ms 196.25.190.209
6 166 ms 165 ms 165 ms lon-ip-hsll-1-gig-7-1-0.telkom-ipnet.co.za [196.43.9.58]
7 195 ms 185 ms 181 ms ldn-b5-link.telia.net [62.115.35.89]
8 177 ms 176 ms 178 ms atos-ic-315186-ldn-b5.c.telia.net [62.115.144.161]
9 * * * Request timed out.
10 214 ms 212 ms 215 ms ae0.er01.telhc.bbc.co.uk [132.185.254.109]
11 196 ms 187 ms 182 ms 132.185.255.148
12 172 ms 171 ms 173 ms 212.58.244.23

All is well....

Johnatan56 · Oct 9, 2016

/slow clap

This is due to packet loss, else it's about 300ms.

LBXAC20 · Oct 9, 2016

Well well well... it's starting to look like it's time to jump ship. Afrihost's network is sinking fast...

akuma · Oct 9, 2016

Lagsville here too. Hope someone's awake to resolve it soon.

Join the MyBroadband community

Get started

Afrihost New Network Feedback - Part 2

Expert Member

Expert Member

Expert Member

EVGA Fanatic

Well-Known Member

Expert Member

Honorary Master

Expert Member

EVGA Fanatic

Senior Member

Expert Member

Expert Member

Expert Member

Well-Known Member

Well-Known Member

Honorary Master

Expert Member

Honorary Master

Well-Known Member

Well-Known Member