Afrihost New Network Feedback - Part 2

Wolfling · Nov 14, 2016

electrofreeze said:
speeds are totally dead other isp works no problems shame on you AH

Same for me. Cant even load speedtest.com.

Tracing route to google.com [216.58.223.14]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 10.0.0.2
2 * * * Request timed out.
3 3500 ms * * jhb-up3.ip.adsl.co.za [169.1.5.29]
4 2477 ms 3489 ms * jhb-in2.ip.adsl.co.za [169.1.5.30]
5 1176 ms 874 ms 940 ms jhb-net1.ip.adsl.co.za [169.1.5.52]
6 1276 ms 1443 ms 2024 ms 169-1-5-243.ip.afrihost.co.za [169.1.5.243]
7 2686 ms * * 72.14.237.239
8 1789 ms 2216 ms 2455 ms www.google-analytics.com [216.58.223.14]

Pinplotter says 80% packet loss. Was fine till just after 12.

Rickster · Nov 14, 2016

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

Tracing route to mybroadband.co.za [104.20.9.169]
over a maximum of 30 hops:

1 2 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 * * * Request timed out.
4 10 ms 10 ms 10 ms jhb-net1.ip.adsl.co.za [169.1.5.52]
5 9 ms 10 ms 9 ms cloudflare.ixp.joburg [196.46.25.198]
6 10 ms 9 ms 10 ms 104.20.9.169

Trace complete.
PS C:\WINDOWS\system32> tracert bras.afrihost.com

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

1 <1 ms <1 ms <1 ms 192.168.0.1
2 61 ms 468 ms 312 ms 155.239.255.250

moedawood · Nov 14, 2016

YouTube streams perfectly at 1080 on 4Mbps but tonight, horrible experience.

Hope this feedback will be used to fix what went wrong

DeSLAM · Nov 14, 2016

Afrihost website down - only cloudflare cached snapshot working - no access to client zone.

Had to reboot router to get internet access this morning.

Domestic pings look fine - anything beyond local is about 170 per hop from ix-ae-7-0.tcore2.KLT-Cape-Town.as6453.net

AfriMan · Nov 14, 2016

DeSLAM said:
Afrihost website down - only cloudflare cached snapshot working - no access to client zone.

Had to reboot router to get internet access this morning.

Domestic pings look fine - anything beyond local is about 170 per hop from ix-ae-7-0.tcore2.KLT-Cape-Town.as6453.net

Looks OK to me, but will check what might have happened

savage · Nov 14, 2016

AfriMan said:
Looks OK to me, but will check what might have happened

Yeah, just a pity you weren't here to say that last night! Sick and tired of this crap every single night, and the next morning getting nothing but ignorance from AfriHost. It's time you guys man up, and admit as to what is going on.

Every single night, it's the same ***** service, over and over

DeSLAM · Nov 14, 2016

This is what we are seeing from Cape Town. So not fine from here.

This page (http://www.afrihost.com/) is currently offline. However, because the site uses Cloudflare's Always Online™ technology you can continue to surf a snapshot of the site. We will keep checking in the background and, as soon as the site comes back, you will automatically be served the live version. Always Online™ is powered by Cloudflare

kohlhtor · Nov 14, 2016

Speedtest from MyBroadband to jhb is not working from yesterday it was working on Telkom

DeSLAM · Nov 14, 2016

AH website working now.

DeSLAM · Nov 14, 2016

AH website down again, ERROR 520 message when trying to access from Cape Town, then redirects to Cloudflare snapshot again.

AfriMan · Nov 14, 2016

DeSLAM said:
AH website down again, ERROR 520 message when trying to access from Cape Town, then redirects to Cloudflare snapshot again.

Seems to be an issue there, the team are investigating

AfriMan · Nov 14, 2016

Rickster said:
PS C:\WINDOWS\system32> tracert mybroadband.co.za

Tracing route to mybroadband.co.za [104.20.9.169]
over a maximum of 30 hops:

1 2 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 * * * Request timed out.
4 10 ms 10 ms 10 ms jhb-net1.ip.adsl.co.za [169.1.5.52]
5 9 ms 10 ms 9 ms cloudflare.ixp.joburg [196.46.25.198]
6 10 ms 9 ms 10 ms 104.20.9.169

Trace complete.
PS C:\WINDOWS\system32> tracert bras.afrihost.com

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

1 <1 ms <1 ms <1 ms 192.168.0.1
2 61 ms 468 ms 312 ms 155.239.255.250

Wolfling said:
Same for me. Cant even load speedtest.com.

Tracing route to google.com [216.58.223.14]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 10.0.0.2
2 * * * Request timed out.
3 3500 ms * * jhb-up3.ip.adsl.co.za [169.1.5.29]
4 2477 ms 3489 ms * jhb-in2.ip.adsl.co.za [169.1.5.30]
5 1176 ms 874 ms 940 ms jhb-net1.ip.adsl.co.za [169.1.5.52]
6 1276 ms 1443 ms 2024 ms 169-1-5-243.ip.afrihost.co.za [169.1.5.243]
7 2686 ms * * 72.14.237.239
8 1789 ms 2216 ms 2455 ms www.google-analytics.com [216.58.223.14]

Pinplotter says 80% packet loss. Was fine till just after 12.

moedawood said:
Capped account, streaming sucks really bad!

Switched to Web Africa, everything is normal. Afrihost has too much of buffering.

Please pass this feedback to the network team to investigate and possibly implement fixes.

As far as the network team were aware, everything should have been normal, but they are checking for anomalies

Hummercellc · Nov 14, 2016

Tracing route to mweb.co.za [196.2.63.110]
over a maximum of 30 hops:

1 * * * Request timed out.
2 15 ms 16 ms 16 ms dbn-up2.ip.adsl.co.za [169.1.5.173]
3 16 ms 15 ms 16 ms dbn-up2.ip.adsl.co.za [169.1.5.174]
4 20 ms 21 ms 20 ms dbn-in1.ip.adsl.co.za [169.1.5.204]
5 73 ms 73 ms 75 ms optinet.ixp.durban [196.10.141.75]
6 104 ms 102 ms 118 ms 197-82-7-1.dbn.mweb.co.za [197.82.7.1]
7 106 ms 103 ms 106 ms te0-7-0-1.vic-p-2.optinet.net [197.84.4.44]
8 109 ms 107 ms 115 ms 197-84-4-100.cpt.mweb.co.za [197.84.4.100]
9 109 ms 105 ms 98 ms te0-0-0-0.cpt-p-2.optinet.net [197.84.4.46]
10 96 ms 93 ms 98 ms te0-7-0-0.cpt-p-1.optinet.net [197.84.4.33]
11 94 ms 106 ms 98 ms vl12.cpt-hscore-2.optinet.net [197.84.5.254]
12 105 ms 106 ms 104 ms vp-02-14.bb.ctn.c27.za.net [196.28.178.70]
13 90 ms 103 ms 102 ms gig5-2-cpt-opt-65-1.optinet.net [196.41.133.166]
14 * * * Request timed out.
15 * * * Request timed out.

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

1 * * * Request timed out.
2 15 ms 16 ms 15 ms dbn-up2.ip.adsl.co.za [169.1.5.173]
3 21 ms 21 ms 21 ms dbn-up2.ip.adsl.co.za [169.1.5.174]
4 21 ms 24 ms 21 ms dbn-in1.ip.adsl.co.za [169.1.5.204]
5 137 ms 18 ms 16 ms 41.162.84.192
6 348 ms 321 ms 272 ms 172.18.1.162
7 81 ms 45 ms 32 ms cloudflare.ixp.joburg [196.46.25.198]
8 188 ms 262 ms 244 ms 104.20.30.244

Trace complete.

AfriMan · Nov 14, 2016

Hummercellc said:

There is an issue on our website, guys are checking this out now.

First trace route looks like weird stuff happening on mweb's routing internally

WickedP3NGU1N · Nov 14, 2016

At least you guys have something that works

My line is so stuffed that it CONNECTS at a faster speed than it says it supports right now. It rode the lightning and came in second place

It jumps between ADSL_G.bmt and ADSL_2plus, connecting anywhere between 0.1MB and 2MB while the line says it can only connect at 1.37MB :wtf: Oh and the SNR is between -3.2 & 5. The Attenuation is between 10 and 70! The packet loss is so bad it makes the Libertarian party look good. It was a line capable of 15MB and now its 2 cups with a string

If Telkom don't fix it soon I might have to just kick it and get a WISP service instead...

3 Different guys from Afrihost are trying to help but responses are slow while I wait for Telkom to come and fix the line...

So the Afrihost net issues you are all seeing look quite normal to me right now

Alien0 · Nov 14, 2016

WickedMONK3Y said:
At least you guys have something that works

My line is so stuffed that it CONNECTS at a faster speed than it says it supports right now. It rode the lightning and came in second place It jumps between ADSL_G.bmt and ADSL_2plus, connecting anywhere between 0.1MB and 2MB while the line says it can only connect at 1.37MB :wtf: Oh and the SNR is between -3.2 & 5. The Attenuation is between 10 and 70! The packet loss is so bad it makes the Libertarian party look good. It was a line capable of 15MB and now its 2 cups with a string If Telkom don't fix it soon I might have to just kick it and get a WISP service instead...

3 Different guys from Afrihost are trying to help but responses are slow while I wait for Telkom to come and fix the line...

So the Afrihost net issues you are all seeing look quite normal to me right now

Disconnect your voice line and only connect your modem/router
worked for me after the storm... still waiting for Telkom to repair the land line though

Kenny · Nov 14, 2016

Good day everyone,
here are my 2c...
Lately it became almost a norm that around this time nothing works like it should, high pings to game servers, torrets are almost dead, packet losses etc.
Just to make sure it is not the congestion on my exchange, I ran "is it my line" tool

Zertop's LineTool Results
Date/Time: Mon Nov 14 16:51:51 CAT 2016

Basic Report:

Your packet loss was 0%.
Your average ping was 26ms.
Your maximum ping was 69ms.

Looking at your average ping, your line seems to be running perfectly.
Looking at your maximum ping, however, it seems as though there could be a slight intermittent issue on the line. If required, please post the results to a forum post.

Detailed Report:

Code:

Pinging 155.239.255.250 with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=62ms TTL=63
Reply from 155.239.255.250: bytes=32 time=23ms TTL=63
Reply from 155.239.255.250: bytes=32 time=69ms TTL=63
Reply from 155.239.255.250: bytes=32 time=25ms TTL=63
Reply from 155.239.255.250: bytes=32 time=24ms TTL=63
Reply from 155.239.255.250: bytes=32 time=24ms TTL=63
Reply from 155.239.255.250: bytes=32 time=25ms TTL=63
Reply from 155.239.255.250: bytes=32 time=24ms TTL=63
Reply from 155.239.255.250: bytes=32 time=24ms TTL=63
Reply from 155.239.255.250: bytes=32 time=25ms TTL=63
Reply from 155.239.255.250: bytes=32 time=25ms TTL=63
Reply from 155.239.255.250: bytes=32 time=24ms TTL=63
Reply from 155.239.255.250: bytes=32 time=24ms TTL=63
Reply from 155.239.255.250: bytes=32 time=23ms TTL=63
Reply from 155.239.255.250: bytes=32 time=24ms TTL=63
Reply from 155.239.255.250: bytes=32 time=23ms TTL=63
Reply from 155.239.255.250: bytes=32 time=25ms TTL=63
Reply from 155.239.255.250: bytes=32 time=27ms TTL=63
Reply from 155.239.255.250: bytes=32 time=23ms TTL=63
Reply from 155.239.255.250: bytes=32 time=23ms TTL=63
Reply from 155.239.255.250: bytes=32 time=24ms TTL=63
Reply from 155.239.255.250: bytes=32 time=23ms TTL=63
Reply from 155.239.255.250: bytes=32 time=23ms TTL=63
Reply from 155.239.255.250: bytes=32 time=23ms TTL=63
Reply from 155.239.255.250: bytes=32 time=23ms TTL=63
Reply from 155.239.255.250: bytes=32 time=24ms TTL=63
Reply from 155.239.255.250: bytes=32 time=24ms TTL=63
Reply from 155.239.255.250: bytes=32 time=24ms TTL=63
Reply from 155.239.255.250: bytes=32 time=23ms TTL=63
Reply from 155.239.255.250: bytes=32 time=24ms TTL=63

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

AfriGenie · Nov 14, 2016

Kenny said:

Good day everyone,
here are my 2c...
Lately it became almost a norm that around this time nothing works like it should, high pings to game servers, torrets are almost dead, packet losses etc.
Just to make sure it is not the congestion on my exchange, I ran "is it my line" tool

Zertop's LineTool Results
Date/Time: Mon Nov 14 16:51:51 CAT 2016

Basic Report:

Your packet loss was 0%.
Your average ping was 26ms.
Your maximum ping was 69ms.

Looking at your average ping, your line seems to be running perfectly.
Looking at your maximum ping, however, it seems as though there could be a slight intermittent issue on the line. If required, please post the results to a forum post.

Detailed Report:

Code:

Pinging 155.239.255.250 with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=62ms TTL=63
Reply from 155.239.255.250: bytes=32 time=23ms TTL=63
Reply from 155.239.255.250: bytes=32 time=69ms TTL=63
Reply from 155.239.255.250: bytes=32 time=25ms TTL=63
Reply from 155.239.255.250: bytes=32 time=24ms TTL=63
Reply from 155.239.255.250: bytes=32 time=24ms TTL=63
Reply from 155.239.255.250: bytes=32 time=25ms TTL=63
Reply from 155.239.255.250: bytes=32 time=24ms TTL=63
Reply from 155.239.255.250: bytes=32 time=24ms TTL=63
Reply from 155.239.255.250: bytes=32 time=25ms TTL=63
Reply from 155.239.255.250: bytes=32 time=25ms TTL=63
Reply from 155.239.255.250: bytes=32 time=24ms TTL=63
Reply from 155.239.255.250: bytes=32 time=24ms TTL=63
Reply from 155.239.255.250: bytes=32 time=23ms TTL=63
Reply from 155.239.255.250: bytes=32 time=24ms TTL=63
Reply from 155.239.255.250: bytes=32 time=23ms TTL=63
Reply from 155.239.255.250: bytes=32 time=25ms TTL=63
Reply from 155.239.255.250: bytes=32 time=27ms TTL=63
Reply from 155.239.255.250: bytes=32 time=23ms TTL=63
Reply from 155.239.255.250: bytes=32 time=23ms TTL=63
Reply from 155.239.255.250: bytes=32 time=24ms TTL=63
Reply from 155.239.255.250: bytes=32 time=23ms TTL=63
Reply from 155.239.255.250: bytes=32 time=23ms TTL=63
Reply from 155.239.255.250: bytes=32 time=23ms TTL=63
Reply from 155.239.255.250: bytes=32 time=23ms TTL=63
Reply from 155.239.255.250: bytes=32 time=24ms TTL=63
Reply from 155.239.255.250: bytes=32 time=24ms TTL=63
Reply from 155.239.255.250: bytes=32 time=24ms TTL=63
Reply from 155.239.255.250: bytes=32 time=23ms TTL=63
Reply from 155.239.255.250: bytes=32 time=24ms TTL=63

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

You definitely shouldn't be seeing latency that high on your DSL line. The latency on your DSL line shouldn't really go above 25ms to 36ms.

Is it only this time of day that you see the latency start increasing?

savage · Nov 14, 2016

AfriGenie said:
You definitely shouldn't be seeing latency that high on your DSL line. The latency on your DSL line shouldn't really go above 25ms to 36ms.

Is it only this time of day that you see the latency start increasing?

Uhm - isn't that what we've been saying, for WEEKS now? Yes, you are absolutely correct, we shouldn't - but we DO. And ONLY on Afrihost. And yes, EVERY single day from 5PM or 8PM on wards (used to be 8, lately it's been 5). My "premium" uncapped DSL was USELESS yesterday night, completely. Not a SINGLE WORD from Afrihost.

Again, as I posted this morning - it's time that we start to get some answers from AH about this.

AfriGenie · Nov 14, 2016

savage said:
Uhm - isn't that what we've been saying, for WEEKS now? Yes, you are absolutely correct, we shouldn't - but we DO. And ONLY on Afrihost. And yes, EVERY single day from 5PM or 8PM on wards (used to be 8, lately it's been 5). My "premium" uncapped DSL was USELESS yesterday night, completely. Not a SINGLE WORD from Afrihost.

Again, as I posted this morning - it's time that we start to get some answers from AH about this.

Kenny's issue appears to be a line issue, or congestion on his Exchange.

Which services are you experiencing problems with?

Join the MyBroadband community

Get started

Afrihost New Network Feedback - Part 2

Well-Known Member

EVGA Fanatic

Senior Member

Senior Member

Afrihost Representative

Expert Member

Senior Member

Expert Member

Senior Member

Senior Member

Afrihost Representative

Afrihost Representative

Expert Member

Afrihost Representative

Well-Known Member

Well-Known Member

Senior Member

Afrihost

Expert Member

Afrihost