Afrihost Support

Z

zsasz

New Member
Joined
Mar 15, 2005
Messages
8
Reaction score
0
Location
Johannesburg North
Does afrihost support no longer work over the weekend?

My fibre has been down since Friday morning , I've logged support tickets Friday evening. Also tried using that call me back feature twice and nothing.

What makes this really annoying, my issue appears to a configuration issue on their or vumatel's end.
 
No, so don't feel too hard done by...YET.

I've been waiting 2 weeks for a a single shred of sense or meaningful assistance/phonecall/support in response to this sort of performance I get 24x7 - just the usual automated resply emails "we're working on it and apologise for any possible???!!! inconvenience this may have caused"

@AfriNatic ^^^ WTH? Really?

21/01/19 20:52
Ping: 45ms
Download: 1.59Mbps
Upload: 0.01Mbps

21/01/19 23:30
Ping 39ms
Download 3.62Mbps
Upload 0.03Mbps

2/02/19 15:15
Ping: 284ms
Download: 0.55Mbps
Upload: 0.01Mbps

2/02/19 15:24
Ping: 73ms
Download: 1.34Mbps
Upload: 0.01Mbps


My dial-up was more reliable and faster back in 2002....
 
Last edited:
Ping statistics for 169.1.1.221:
Packets: Sent = 31, Received = 23, Lost = 8 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 70ms, Maximum = 1242ms, Average = 451ms


C:\WINDOWS\system32>ping -t afrihost.co.za

Pinging afrihost.co.za [169.1.1.221] with 32 bytes of data:
Request timed out.
Request timed out.
Reply from 169.1.1.221: bytes=32 time=688ms TTL=55
Reply from 169.1.1.221: bytes=32 time=752ms TTL=55
Reply from 169.1.1.221: bytes=32 time=244ms TTL=55
Request timed out.
Reply from 169.1.1.221: bytes=32 time=555ms TTL=55
Reply from 169.1.1.221: bytes=32 time=822ms TTL=55
Request timed out.
Reply from 169.1.1.221: bytes=32 time=637ms TTL=55
Reply from 169.1.1.221: bytes=32 time=646ms TTL=55
Reply from 169.1.1.221: bytes=32 time=537ms TTL=55
Reply from 169.1.1.221: bytes=32 time=171ms TTL=55
Request timed out.
Request timed out.
Request timed out.
Reply from 169.1.1.221: bytes=32 time=552ms TTL=55
Request timed out.
Reply from 169.1.1.221: bytes=32 time=85ms TTL=55
Reply from 169.1.1.221: bytes=32 time=487ms TTL=55
Reply from 169.1.1.221: bytes=32 time=216ms TTL=55
Reply from 169.1.1.221: bytes=32 time=432ms TTL=55
Reply from 169.1.1.221: bytes=32 time=75ms TTL=55
Reply from 169.1.1.221: bytes=32 time=1242ms TTL=55
Reply from 169.1.1.221: bytes=32 time=70ms TTL=55
Reply from 169.1.1.221: bytes=32 time=135ms TTL=55
Reply from 169.1.1.221: bytes=32 time=208ms TTL=55
Reply from 169.1.1.221: bytes=32 time=1080ms TTL=55
Reply from 169.1.1.221: bytes=32 time=555ms TTL=55
Reply from 169.1.1.221: bytes=32 time=125ms TTL=55
Reply from 169.1.1.221: bytes=32 time=78ms TTL=55
 
Last edited:
zsasz said:
Does afrihost support no longer work over the weekend?

My fibre has been down since Friday morning , I've logged support tickets Friday evening. Also tried using that call me back feature twice and nothing.

What makes this really annoying, my issue appears to a configuration issue on their or vumatel's end.
Click to expand...

Gee, that is horrible to hear. I am so terribly sorry that I am only getting to your thread now. I am more than willing to help you out.

Please send me the ticket ID in question and I will look into this for you.
 
MirageF1 said:
Ping statistics for 169.1.1.221:
Packets: Sent = 31, Received = 23, Lost = 8 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 70ms, Maximum = 1242ms, Average = 451ms


C:\WINDOWS\system32>ping -t afrihost.co.za

Pinging afrihost.co.za [169.1.1.221] with 32 bytes of data:
Request timed out.
Request timed out.
Reply from 169.1.1.221: bytes=32 time=688ms TTL=55
Reply from 169.1.1.221: bytes=32 time=752ms TTL=55
Reply from 169.1.1.221: bytes=32 time=244ms TTL=55
Request timed out.
Reply from 169.1.1.221: bytes=32 time=555ms TTL=55
Reply from 169.1.1.221: bytes=32 time=822ms TTL=55
Request timed out.
Reply from 169.1.1.221: bytes=32 time=637ms TTL=55
Reply from 169.1.1.221: bytes=32 time=646ms TTL=55
Reply from 169.1.1.221: bytes=32 time=537ms TTL=55
Reply from 169.1.1.221: bytes=32 time=171ms TTL=55
Request timed out.
Request timed out.
Request timed out.
Reply from 169.1.1.221: bytes=32 time=552ms TTL=55
Request timed out.
Reply from 169.1.1.221: bytes=32 time=85ms TTL=55
Reply from 169.1.1.221: bytes=32 time=487ms TTL=55
Reply from 169.1.1.221: bytes=32 time=216ms TTL=55
Reply from 169.1.1.221: bytes=32 time=432ms TTL=55
Reply from 169.1.1.221: bytes=32 time=75ms TTL=55
Reply from 169.1.1.221: bytes=32 time=1242ms TTL=55
Reply from 169.1.1.221: bytes=32 time=70ms TTL=55
Reply from 169.1.1.221: bytes=32 time=135ms TTL=55
Reply from 169.1.1.221: bytes=32 time=208ms TTL=55
Reply from 169.1.1.221: bytes=32 time=1080ms TTL=55
Reply from 169.1.1.221: bytes=32 time=555ms TTL=55
Reply from 169.1.1.221: bytes=32 time=125ms TTL=55
Reply from 169.1.1.221: bytes=32 time=78ms TTL=55
Click to expand...

This test looks horrible, I will try and get one of the fibre managers to give you a call to help you sort this out. Please send me your account information via PM and we will get this sorted out. I am very sorry for getting back to you so late.
 
AfriNatic said:
Gee, that is horrible to hear. I am so terribly sorry that I am only getting to your thread now. I am more than willing to help you out.

Please send me the ticket ID in question and I will look into this for you.
Click to expand...
This was resolved 4 days after logging it. It literally took 10 minutes to resolve, but, I had request 3 call backs and update to support ticket twice before resolution
 
AfriNatic said:
This test looks horrible, I will try and get one of the fibre managers to give you a call to help you sort this out. Please send me your account information via PM and we will get this sorted out. I am very sorry for getting back to you so late.
Click to expand...

PM sent.
 
zsasz said:
This was resolved 4 days after logging it. It literally took 10 minutes to resolve, but, I had request 3 call backs and update to support ticket twice before resolution
Click to expand...

That is really terrible, no client of ours should struggle like that to get help. If you need help again, please let me know.
 
So, OP was Sunday, so let's not count that, then:
Monday, Tuesday, Wednesday, Thursday, Friday.

That's quite a long response time in your own sub-forum.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X