Afrihost New Network Feedback - Part 2

Status
Not open for further replies.
This is not true or you're not informed. This is the response I got from your critical care team on Monday.
Code:
I see you also were testing mweb sites. 
We have been getting a few complaints about the mweb sites being slow. 
Extensive testing was carried out, during peak times. 

The feedback I got was routeing issues was sorted.

It's not fully resolved though from my testing.
I can confirm it has not been resolved.
 
As I mentioned before, you're welcome to.

Surely that is not a helpful attitude from your side? Let my try and phrase my question so that you understand what I'm asking. I'm typing it slowly too.

We try our best to supply tests and show where issues are. I even made a video for critical care to show my issue.
At some point we need to assume no solution is forthcoming.
So my question to you as a helpful Afrihost representative is when in your opinion should we as customers log a dispute. After one day is obviously stupid, two days too, but when would you suggest is the right time. The last thing I want is to waste my time and your accounts departments time with stupid requests.
 
Surely that is not a helpful attitude from your side? Let my try and phrase my question so that you understand what I'm asking. I'm typing it slowly too.

We try our best to supply tests and show where issues are. I even made a video for critical care to show my issue.
At some point we need to assume no solution is forthcoming.
So my question to you as a helpful Afrihost representative is when in your opinion should we as customers log a dispute. After one day is obviously stupid, two days too, but when would you suggest is the right time. The last thing I want is to waste my time and your accounts departments time with stupid requests.

It's not my place to recommend you take things forward from Critical Care - that's a decision you need to make.

I've confirmed this before and stand by it, our Critical Care are extremely good at what they do and will see the issue through. I'm sorry that we can't confirm a time it'll be fixed - but your query is actively being looked at.
 
Last edited:
As an ex Afrihost client, I can confirm that critical care are essentially useless, and out of all the issues I had, and after many tests, my issues were never resolved, and in the end I was told the only option was to go to another ISP, not only by them but also by reps on this forum. I got one credit, and was made to feel like a criminal after, because I complained.
Exactly how I feel, I do not like the way the Afrihost Reps deal with situations. They make you feel like you are the problem.
 
Any Afripeeps around?

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

1 <1 ms <1 ms <1 ms 192.168.0.1
2 358 ms 376 ms 407 ms 169-0-5-1.ip.afrihost.co.za [169.0.5.1]
3 * * * Request timed out.
4 264 ms 247 ms 266 ms jhb-in1.ip.adsl.co.za [169.1.5.42]
5 390 ms 407 ms 392 ms jhb-net1.ip.adsl.co.za [169.1.5.52]
6 388 ms 445 ms 383 ms 169-1-5-243.ip.afrihost.co.za [169.1.5.243]
7 344 ms 368 ms 398 ms 72.14.237.239
8 367 ms 402 ms 386 ms jnb01s07-in-f4.1e100.net [216.58.223.4]

Trace complete.
 
As an ex Afrihost client, I can confirm that critical care are essentially useless, and out of all the issues I had, and after many tests, my issues were never resolved, and in the end I was told the only option was to go to another ISP, not only by them but also by reps on this forum. I got one credit, and was made to feel like a criminal after, because I complained.
I cannot agree with this pal re the reps. They are very active in trying to assist as best they possibly can. In fact, they come across as very professional and polite despite alot of abuse. The reps are human after all, and they can only handle so much abuse

I can understand users frustrations when things dont work, but it must difficult to pin point issues when not everybody are having issues. I remember there was once an issue in Cape Town, but not all users were affected.

But in your defense purp, at some point you get tired of it all, and it's time to move on. One cannot blame you for that, and if you experience better internet with another isp, then its a decision you have to make.
 
Any Afripeeps around?

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

1 <1 ms <1 ms <1 ms 192.168.0.1
2 358 ms 376 ms 407 ms 169-0-5-1.ip.afrihost.co.za [169.0.5.1]
3 * * * Request timed out.
4 264 ms 247 ms 266 ms jhb-in1.ip.adsl.co.za [169.1.5.42]
5 390 ms 407 ms 392 ms jhb-net1.ip.adsl.co.za [169.1.5.52]
6 388 ms 445 ms 383 ms 169-1-5-243.ip.afrihost.co.za [169.1.5.243]
7 344 ms 368 ms 398 ms 72.14.237.239
8 367 ms 402 ms 386 ms jnb01s07-in-f4.1e100.net [216.58.223.4]

Trace complete.

Not looking very good there :(
Any services running in the background?

Is the latency to your exchange replicated when testing with another ISP at all?
 
Let me log on with Web Africa.

Give me a sec

EDIT: SAIX Speedtest (Afrihost):
Down: 0.34Mbps
Up: 0.41Mbps
Jitter: 89ms
Ping: 303ms

SAIX Speedtest (WebAfrica):



Last Result:
Download Speed: 1271 kbps (158.9 KB/sec transfer rate)
Upload Speed: 402 kbps (50.3 KB/sec transfer rate)
Latency: 142 ms
Jitter: 66 ms

Web Africa Tracert:

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

1 2 ms <1 ms <1 ms 192.168.0.1
2 296 ms 290 ms 294 ms 196-210-132-129.dynamic.isadsl.co.za [196.210.132.129]
3 251 ms 266 ms 268 ms cdsl1-rba-vl2360.ip.isnet.net [196.38.73.133]
4 313 ms 255 ms 253 ms cdsl1-rba-vl150.ip.isnet.net [196.38.73.17]
5 221 ms 315 ms 389 ms core2b-pkl-te0-0-0-0.ip.isnet.net [196.26.0.63]
6 261 ms * 306 ms pr2-pkl-xe-2-2-0.ip.isnet.net [168.209.1.179]
7 298 ms 329 ms 340 ms 72.14.205.16
8 389 ms 396 ms 415 ms 72.14.237.239
9 321 ms 310 ms 317 ms jnb01s07-in-f4.1e100.net [216.58.223.4]

Trace complete.
 
Last edited:
Let me log on with Web Africa.

Give me a sec

EDIT: SAIX Speedtest (Afrihost):
Down: 0.34Mbps
Up: 0.41Mbps
Jitter: 89ms
Ping: 303ms

SAIX Speedtest (WebAfrica):



Last Result:
Download Speed: 1271 kbps (158.9 KB/sec transfer rate)
Upload Speed: 402 kbps (50.3 KB/sec transfer rate)
Latency: 142 ms
Jitter: 66 ms

Web Africa Tracert:

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

1 2 ms <1 ms <1 ms 192.168.0.1
2 296 ms 290 ms 294 ms 196-210-132-129.dynamic.isadsl.co.za [196.210.132.129]
3 251 ms 266 ms 268 ms cdsl1-rba-vl2360.ip.isnet.net [196.38.73.133]
4 313 ms 255 ms 253 ms cdsl1-rba-vl150.ip.isnet.net [196.38.73.17]
5 221 ms 315 ms 389 ms core2b-pkl-te0-0-0-0.ip.isnet.net [196.26.0.63]
6 261 ms * 306 ms pr2-pkl-xe-2-2-0.ip.isnet.net [168.209.1.179]
7 298 ms 329 ms 340 ms 72.14.205.16
8 389 ms 396 ms 415 ms 72.14.237.239
9 321 ms 310 ms 317 ms jnb01s07-in-f4.1e100.net [216.58.223.4]

Trace complete.
Slaught3r, congestion... Log a fault with Telkom, and ask them to have them sort the exchange out in terms of capacity. Looks like it might be running on full your exchange
 
Looks like your exchange isn't in a very happy place :(

Please help... I am at the end of my tether with this crap. Got the following ref from Telkomza: 28BRK231015 but no idea what the progress on it is.
 
Please help... I am at the end of my tether with this crap. Got the following ref from Telkomza: 28BRK231015 but no idea what the progress on it is.

Was the fault logged with us? Can't seem to search it :(
Congestion is always a tough one to crack. Telkom need to upgrade hardware in the area which is done based on a pretty stringent schedule.

Usually the best way to get stuff like this sorted out is to have your friends, family, neighbours and pets in the area to log faults.
 
Please help... I am at the end of my tether with this crap. Got the following ref from Telkomza: 28BRK231015 but no idea what the progress on it is.
Slaughter i know completely irrelevant, but whats your mobile signal like in your area?
 
Slaughter i know completely irrelevant, but whats your mobile signal like in your area?

I am actually going to pickup a LTE sim tomorrow to see if that is an option. If signal is good, then I will switch - the cost is just prohibiting me at the moment.

Was the fault logged with us? Can't seem to search it :(
Congestion is always a tough one to crack. Telkom need to upgrade hardware in the area which is done based on a pretty stringent schedule.

Usually the best way to get stuff like this sorted out is to have your friends, family, neighbours and pets in the area to log faults.

The fault is logged with Telkom - I sent the details to one of you Afriguys to keep tabs on it (not sure which one - you all look the same to me... :D) So Telkom is aware of it and there are plans to connect it to Metro Ethernet, but this was almost a year ago - no feedback since... :(

EDIT: Quote from Afriman on PM: "AfriGenie has logged a fault for you - so he's checking on the progress for you."
 
Last edited:
I am actually going to pickup a LTE sim tomorrow to see if that is an option. If signal is good, then I will switch - the cost is just prohibiting me at the moment.



The fault is logged with Telkom - I sent the details to one of you Afriguys to keep tabs on it (not sure which one - you all look the same to me... :D) So Telkom is aware of it and there are plans to connect it to Metro Ethernet, but this was almost a year ago - no feedback since... :(

Check our coverage map before making any purchases, to be safe :)

I know congestion is super frustrating :( Do you know if your area is marked for fibre rollouts at all?
 
Well yes they are, but nothing has been resolved.
You're not answering my question. When should I say enough is enough and argue my case in front of big brother. How many weeks is enough for a ticket to be open without solution?
All my issues disappeared when I moved to capped account. It is that sh***y new shaping policy on the business uncapped.
 
Check our coverage map before making any purchases, to be safe :)

I know congestion is super frustrating :( Do you know if your area is marked for fibre rollouts at all?

Problem being that the colours that indicate the different connection types just doesn't load... :(
 
I am actually going to pickup a LTE sim tomorrow to see if that is an option. If signal is good, then I will switch - the cost is just prohibiting me at the moment.



The fault is logged with Telkom - I sent the details to one of you Afriguys to keep tabs on it (not sure which one - you all look the same to me... :D) So Telkom is aware of it and there are plans to connect it to Metro Ethernet, but this was almost a year ago - no feedback since... :(

EDIT: Quote from Afriman on PM: "AfriGenie has logged a fault for you - so he's checking on the progress for you."
The only reason i say this re mobile signal Slaught3r is to move your line back to TI, and get the integrated data sim. So keep your Afrihost DSL data, but in times like this, that integrated data sim does come in handy. Until Openserve can fix your exchange, you can use the sim as a back up.

It would be awesome if Afrihost could introduce an integrated sim to use with our DSL data, but i know its not feasible as explained before. :)
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X