Afrihost New Network Feedback - Part 2

Status
Not open for further replies.
kohlhtor said:
Download speed Afrihost 200 Kb/s webafrica 1.1 mb/s
Click to expand...

GRES said:
We going in circles and you simply buying the time!
All things regarding to this "phenomena" were reported numerous times to AFRIHOST
All possible DNS settings on router and PC's (AH / Google /best SA / mixed) were tested - no any difference.
Everything working fine with all these settings with another ISP.
I have only one logical explanation - bad network management from AFRIHOST.
Nothing else!
Click to expand...

Must be a regional thing, as my Afrihost account seems to be working fine.

You guys might want to consider adding your location to your MyBB profile by the way. It is always useful for reps and other users to see at a glance what region you're in when you talk about internet related matters.
 
Bryn said:
Must be a regional thing, as my Afrihost account seems to be working fine.

You guys might want to consider adding your location to your MyBB profile by the way. It is always useful for reps and other users to see at a glance what region you're in when you talk about internet related matters.
Click to expand...
kohlhtor is on our beachfront... :p
 
MickeyD said:
kohlhtor is on our beachfront... :p
Click to expand...

:o

kohlhtor said:
Thanks I'm in pe
Click to expand...

I'm new to this thread on account of my current Afrihost account actually being a temporary replacement of my usual account. Forgive me if you've provided this info already, but have you tested your line with other ISP accounts? Should be easy to determine if Afrihost are the cause of your grievances. It would be pretty weird if you have issues specific to Afrihost in Summerstrand/Humewood, when I'm doing fine on AH in Walmer.

You can update your location here: http://mybroadband.co.za/vb/profile.php?do=editprofile
 
Hummercellc said:
To test I tried grabbing the Skype offline installer, it was running at 98kb/s on a 20meg line with Afrihost. Switched to my Mweb account and immediately started at 1.8mb/s. Really pathetic speeds to international services.
Click to expand...

Looks like they have to throttle to "fix" the latency problem. Clear sign of lack of capacity.
 
Bryn said:
:o



I'm new to this thread on account of my current Afrihost account actually being a temporary replacement of my usual account. Forgive me if you've provided this info already, but have you tested your line with other ISP accounts? Should be easy to determine if Afrihost are the cause of your grievances. It would be pretty weird if you have issues specific to Afrihost in Summerstrand/Humewood, when I'm doing fine on AH in Walmer.

You can update your location here: http://mybroadband.co.za/vb/profile.php?do=editprofile
Click to expand...

Other accounts working fine only Afrihost
 
wingnut771 said:
Looks like they have to throttle to "fix" the latency problem. Clear sign of lack of capacity.
Click to expand...

Definitely not the case, our Team made good progress last night, and I'm sure during the course of the day there will be further improvements in the East.
 
VindicatoR said:
Area: Cape Town
Account type: Capped Account / 100mbps
Local Traceroute:

Tracing route to www.google.co.za [216.58.223.3]
over a maximum of 30 hops:

1 4 ms 3 ms 2 ms 192.168.0.1
2 * * * Request timed out.
3 11 ms 11 ms 11 ms cpt-rx2.ip.adsl.co.za [169.1.5.82]
4 9 ms 11 ms 10 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
5 8 ms 10 ms 11 ms 41.164.52.40
6 31 ms 31 ms 30 ms 172.18.1.162
7 29 ms 31 ms 31 ms 72.14.194.206
8 31 ms 31 ms 31 ms 72.14.237.239
9 30 ms 31 ms 30 ms jnb01s07-in-f3.1e100.net [216.58.223.3]

Trace complete.

Traceroute to affected Sites: All EU Sites Really

Tracing route to www.battle.net [24.105.29.30]
over a maximum of 30 hops:

1 4 ms 3 ms 3 ms 192.168.0.1
2 * * * Request timed out.
3 10 ms 6 ms 10 ms cpt-rx2.ip.adsl.co.za [169.1.5.82]
4 13 ms 11 ms 10 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
5 7 ms 7 ms 7 ms 41.164.52.40
6 52 ms 56 ms 81 ms if-ae-7-0.tcore2.KLT-Cape-Town.as6453.net [41.206.165.25]
7 276 ms 279 ms 302 ms if-ae-2-2.tcore1.KLT-Cape-Town.as6453.net [41.206.164.253]
8 178 ms 179 ms 178 ms if-p-6.core2.PV9-Lisbon.as6453.net [41.206.164.6]
9 267 ms 266 ms 270 ms if-xe-0-0-0-2000.tcore1.PV9-Lisbon.as6453.net [80.231.158.1]
10 271 ms 272 ms 270 ms if-ae-1-3.tcore1.SV8-Highbridge.as6453.net [80.231.158.30]
11 266 ms * 267 ms if-ae-6-2.thar1.NJY-Newark.as6453.net [80.231.138.18]
12 * 261 ms * if-ae-1-3.thar2.NJY-Newark.as6453.net [216.6.57.2]
13 268 ms 274 ms * if-ae-14-15.tcore2.NTO-New-York.as6453.net [66.198.111.9]
14 283 ms 279 ms 274 ms if-ae-12-2.tcore1.N75-New-York.as6453.net [66.110.96.5]
15 270 ms 276 ms 271 ms 66.110.96.130
16 272 ms 274 ms 280 ms hu-1-3-0-3-cr02.newyork.ny.ibone.comcast.net [68.86.83.101]
17 273 ms 279 ms 278 ms be-31-pe01.60hudson.ny.ibone.comcast.net [68.86.85.226]
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 as30036.350ecermak.il.ibone.comcast.net [173.167.57.150] reports: Destination net unreachable.

Trace complete.

Tracing route to www.bbc.net.uk [212.58.244.69]
over a maximum of 30 hops:

1 1 ms 1 ms 3 ms 192.168.0.1
2 * * * Request timed out.
3 10 ms 6 ms 6 ms cpt-rx2.ip.adsl.co.za [169.1.5.82]
4 10 ms 22 ms 31 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
5 4 ms 7 ms 10 ms 41.164.52.40
6 55 ms 52 ms 56 ms if-ae-7-0.tcore1.KLT-Cape-Town.as6453.net [41.206.164.53]
7 203 ms * 212 ms if-ae-5-90.tcore2.PV9-Lisbon.as6453.net [80.231.159.109]
8 199 ms 194 ms 199 ms if-ae-2-2.tcore1.PV9-Lisbon.as6453.net [80.231.158.5]
9 206 ms 202 ms 202 ms if-ae-1-3.tcore1.SV8-Highbridge.as6453.net [80.231.158.30]
10 * 204 ms 202 ms if-ae-19-2.tcore2.L78-London.as6453.net [80.231.138.22]
11 215 ms 210 ms 207 ms if-ae-2-2.tcore1.L78-London.as6453.net [80.231.131.2]
12 203 ms 198 ms 203 ms if-ae-17-2.tcore1.LDN-London.as6453.net [80.231.130.130]
13 197 ms 198 ms 199 ms 195.219.83.102
14 193 ms 194 ms * ae-1-3104.ear2.London2.Level3.net [4.69.143.190]
15 199 ms 198 ms 202 ms unknown.Level3.net [212.187.139.230]
16 * * * Request timed out.
17 200 ms 196 ms 200 ms ae0.er01.telhc.bbc.co.uk [132.185.254.109]
18 196 ms 199 ms 198 ms 132.185.255.148
19 210 ms 210 ms 215 ms bbc-vip114.telhc.bbc.co.uk [212.58.244.69]

Trace complete.

Ping to bras.afrihost.com:

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

Affected Services: International Traffic

DNS: 169.1.1.1 169.1.1.10
Click to expand...

How are things looking this morning? Has there been any change?
 
Funny part is, they don't change their network status to reflect the issues in KZN.

"Our DSL Broadband network is not running like a bomb!"
 
Icemanbrfc said:
So they randomly selecting who to throttle? Would be strange if that was the case, as not everybody are having issues.
Click to expand...

But I see their are different pop in cap town
Other user using

3 11 ms 11 ms 11 ms cpt-rx2.ip.adsl.co.za [169.1.5.82]
4 9 ms 11 ms 10 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
5 8 ms 10 ms 11 ms 41.164.52.40

I use
3 cpt-up1.ip.adsl.co.za (169.1.5.105) 166.914 ms 533.927 ms 541.057 ms
 
Last edited:
GRES said:
We going in circles and you simply buying the time!
All things regarding to this "phenomena" were reported numerous times to AFRIHOST
All possible DNS settings on router and PC's (AH / Google /best SA / mixed) were tested - no any difference.
Everything working fine with all these settings with another ISP.
I have only one logical explanation - bad network management from AFRIHOST.
Nothing else!
Click to expand...

I see almost 6 months down the line after I investigated whether or not I should get a service from Afrihost (I decided against using AH), absolutely nothing has changed.

The same problems over and over again, continuously trying to tweak performance does not help, IF the basic network issues are not addressed and fixed which includes amongst other things:

Reviewing the complete structure of your network;
Consolidating the available capacity on critical routes into a few high capacity links;
Increasing the available capacity on links; and,
Making sure network configuration complies with International standards with regard to (amongst other glaring issues) how your DNS servers are set up, which I see is still non-compliant.

Really AH this is not rocket science. How can you possibly continue to treat your customer base like a bunch of lab rats while various people in AH play configuration tweaking games??
 
Something still not right?

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

1 * * * Request timed out.
2 16 ms 15 ms 17 ms dbn-up2.ip.adsl.co.za [169.1.5.173]
3 17 ms 19 ms 17 ms dbn-up2.ip.adsl.co.za [169.1.5.174]
4 21 ms 21 ms 20 ms dbn-in1.ip.adsl.co.za [169.1.5.204]
5 20 ms 20 ms 20 ms 41.162.84.192
6 35 ms 35 ms 44 ms 172.18.1.162
7 183 ms 183 ms 182 ms cloudflare.ixp.joburg [196.46.25.198]
8 213 ms 191 ms 182 ms 104.20.30.244

Trace complete.
Click to expand...


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

1 * * * Request timed out.
2 16 ms 16 ms 16 ms dbn-up2.ip.adsl.co.za [169.1.5.173]
3 16 ms 16 ms 17 ms dbn-up2.ip.adsl.co.za [169.1.5.174]
4 33 ms 26 ms 41 ms dbn-in1.ip.adsl.co.za [169.1.5.204]
5 21 ms 22 ms 23 ms 41.162.84.192
6 31 ms 30 ms 29 ms 172.18.1.162
7 190 ms 190 ms 194 ms cloudflare.ixp.joburg [196.46.25.198]
8 203 ms 196 ms 196 ms 104.20.71.110

Trace complete.
Click to expand...
 
kohlhtor said:
But I see their are different pop in cap town
Other user using

3 11 ms 11 ms 11 ms cpt-rx2.ip.adsl.co.za [169.1.5.82]
4 9 ms 11 ms 10 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
5 8 ms 10 ms 11 ms 41.164.52.40

I use
3 cpt-up1.ip.adsl.co.za (169.1.5.105) 166.914 ms 533.927 ms 541.057 ms
Click to expand...

Are you seeing this latency to 169.1.5.105 now?
My ping to that destination is around 19ms, what do your pings look like?
 
GRES said:
We going in circles and you simply buying the time!
All things regarding to this "phenomena" were reported numerous times to AFRIHOST
All possible DNS settings on router and PC's (AH / Google /best SA / mixed) were tested - no any difference.
Everything working fine with all these settings with another ISP.
I have only one logical explanation - bad network management from AFRIHOST.
Nothing else!
Click to expand...

Sorry to hear you feel that way. We aren't trying to buy time, we're simply not seeing an issue in your area so will need to look at some data to advise further.
 
AfriGuy said:
Results look fairly standard for CloudFlare.
Click to expand...

Mweb Account :confused:

1 197-81-99-XXX.jhb.mweb.co.za (197.81.99.XXX) 0.993 ms 1.314 ms 0.817 ms
2 197-81-146-1.jhb.mweb.co.za (197.81.146.1) 16.714 ms 15.192 ms 15.093 ms
3 vl85.vic-hscore-2.optinet.net (197.81.146.4) 16.039 ms 16.410 ms 16.398 ms
4 12.te0-7-0-2.vic-p-1.optinet.net (197.80.5.241) 18.903 ms 18.924 ms 18.763 ms
5 201.bu-ether5.vic-pe-2.optinet.net (197.80.7.71) 22.073 ms 22.390 ms 23.765 ms
6 bu-ether1.tis-pe-2.optinet.net (197.80.4.9) 29.809 ms 29.385 ms 31.773 ms
7 bu-ether2.tis-pe-1.optinet.net (197.80.4.252) 31.043 ms 30.933 ms 31.031 ms
8 197-80-4-195.jhb.mweb.co.za (197.80.4.195) 32.137 ms 34.894 ms 32.484 ms
9 cloudflare.ixp.joburg (196.46.25.198) 29.074 ms 29.977 ms 31.408 ms
10 104.20.30.244 (104.20.30.244) 29.307 ms 30.233 ms 29.978 ms
 
Hummercellc said:
Mweb Account :confused:

1 197-81-99-XXX.jhb.mweb.co.za (197.81.99.XXX) 0.993 ms 1.314 ms 0.817 ms
2 197-81-146-1.jhb.mweb.co.za (197.81.146.1) 16.714 ms 15.192 ms 15.093 ms
3 vl85.vic-hscore-2.optinet.net (197.81.146.4) 16.039 ms 16.410 ms 16.398 ms
4 12.te0-7-0-2.vic-p-1.optinet.net (197.80.5.241) 18.903 ms 18.924 ms 18.763 ms
5 201.bu-ether5.vic-pe-2.optinet.net (197.80.7.71) 22.073 ms 22.390 ms 23.765 ms
6 bu-ether1.tis-pe-2.optinet.net (197.80.4.9) 29.809 ms 29.385 ms 31.773 ms
7 bu-ether2.tis-pe-1.optinet.net (197.80.4.252) 31.043 ms 30.933 ms 31.031 ms
8 197-80-4-195.jhb.mweb.co.za (197.80.4.195) 32.137 ms 34.894 ms 32.484 ms
9 cloudflare.ixp.joburg (196.46.25.198) 29.074 ms 29.977 ms 31.408 ms
10 104.20.30.244 (104.20.30.244) 29.307 ms 30.233 ms 29.978 ms
Click to expand...

I'll query this with our network team, although I'm not aware of any peering issues.
Could just be how the routers communicate with each other.
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X