Afrihost New Network Feedback

Status
Not open for further replies.
How much longer does Afrihost expect us to actually keep calm over these continual issues. Now I cannot send emails, wtf. This is not teething problems, this is out right incompetence.

Cant email, cant send small attachments via Skype, browsing does not work.

I think it's a little early to accuse anyone of incompetence, we still don't know what caused this, and ultimately the people you're talking about are the ones who we rely on to fix this for all of us. Let's give them a chance to do their work.
 
View attachment 310691

Last connection at the office lasted a whole 5 days without disconnecting:).

Edit:
11:30pm PDT = 8:30am SAST

That looks pretty alright. We haven't quite sorted out our session disconnects like we have on the old network, but I'm pretty sure we'll be going back to the same system we had in place before :)
 
I think it's a little early to accuse anyone of incompetence, we still don't know what caused this, and ultimately the people you're talking about are the ones who we rely on to fix this for all of us. Let's give them a chance to do their work.

It's +- 12 hours later?? Just how much time do you need to competently identify a network problem? Or is this perhaps a matter of your competent engineers going to bed last night, instead of working on the problems last night like they where supposed to?

EDIT: Or perhaps you're waiting for the competent Canadians to wake up?
 
Not sure how that happened. Did your product actually change in ClientZone or are you saying that it behaves more like an Uncapped product now?

Changed in the ClientZone.
I might have done something wrong. But leaves a sour taste as I paid for a business connection and getting an normal uncapped connection...
 
I think it's a little early to accuse anyone of incompetence, we still don't know what caused this, and ultimately the people you're talking about are the ones who we rely on to fix this for all of us. Let's give them a chance to do their work.

Nope, its not, I pay you are expected to deliver, there is always an excuse, ipc issues, were one a few months back, IOS updates broke your network, and there have been many others. Now we have promises of this fancy staqt of the art network, an what less than a few days and we back to the normal Afrihost experience. I dont think I am alone in my feelings on this.

A lesson Afrihost never seem to learn, don't hype up a product to such an extent that you cannot deliver, its bound to bite you in the ass, and you lose far more than you will ever gain. I would hate to a company that seems to be continually in the press or mentioned in forums due to poor service.
 
I can't access FNB?

1 * * *
2 dbn-up2.ip.adsl.co.za (169.1.5.173) 14.970 ms 13.843 ms 14.043 ms
3 dbn-up2.ip.adsl.co.za (169.1.5.174) 15.030 ms 14.174 ms 14.052 ms
4 dbn-in1.ip.adsl.co.za (169.1.5.204) 14.290 ms 14.121 ms 13.785 ms
5 41.162.84.192 (41.162.84.192) 9.104 ms 8.998 ms 9.101 ms
6 172.18.16.53 (172.18.16.53) 17.504 ms 17.132 ms 16.749 ms
7 * * *
8 * * *
 
I can't access FNB?

1 * * *
2 dbn-up2.ip.adsl.co.za (169.1.5.173) 14.970 ms 13.843 ms 14.043 ms
3 dbn-up2.ip.adsl.co.za (169.1.5.174) 15.030 ms 14.174 ms 14.052 ms
4 dbn-in1.ip.adsl.co.za (169.1.5.204) 14.290 ms 14.121 ms 13.785 ms
5 41.162.84.192 (41.162.84.192) 9.104 ms 8.998 ms 9.101 ms
6 172.18.16.53 (172.18.16.53) 17.504 ms 17.132 ms 16.749 ms
7 * * *
8 * * *

Yes - Afrihost is broken, yet again...
 
I can't access FNB?

1 * * *
2 dbn-up2.ip.adsl.co.za (169.1.5.173) 14.970 ms 13.843 ms 14.043 ms
3 dbn-up2.ip.adsl.co.za (169.1.5.174) 15.030 ms 14.174 ms 14.052 ms
4 dbn-in1.ip.adsl.co.za (169.1.5.204) 14.290 ms 14.121 ms 13.785 ms
5 41.162.84.192 (41.162.84.192) 9.104 ms 8.998 ms 9.101 ms
6 172.18.16.53 (172.18.16.53) 17.504 ms 17.132 ms 16.749 ms
7 * * *
8 * * *

Sorry about that :( Definitely some weirdness happening from our end, we're working on a fix :)
 
Hehe, how your line manages to perform like this all the time is proper cool!
Are you hoarding your areas DSLAM in your garden? :p

my ping last night was also close to that of Lara at 39ms, but had no issues. In fact switching between your data and Telkom, and both seemed stable.
 
Sorry about that :( Definitely some weirdness happening from our end, we're working on a fix :)

but there have been issue since about 20:30 last night and we still have issues,. and it actually seem to be getting worse, some of us actually need to get work done and month end it the busiest time of the month.
 
my ping last night was also close to that of Lara at 39ms, but had no issues. In fact switching between your data and Telkom, and both seemed stable.

Great news!
There are still some intermittent-nes (if that's a word) around this morning though.
 
but there have been issue since about 20:30 last night and we still have issues,. and it actually seem to be getting worse, some of us actually need to get work done and month end it the busiest time of the month.

Our network team hasn't stopped working on this, if there was a quick fix available it would have been done already.
While there have been improvements, it's not up to 100%.
 
Ping Test:

ping 197.242.144.102

64 bytes from 197.242.144.102: icmp_req=1 ttl=54 time=33 ms
64 bytes from 197.242.144.102: icmp_req=2 ttl=54 time=32 ms
64 bytes from 197.242.144.102: icmp_req=3 ttl=54 time=32 ms
64 bytes from 197.242.144.102: icmp_req=4 ttl=54 time=34 ms
64 bytes from 197.242.144.102: icmp_req=5 ttl=54 time=35 ms


ping 8.8.8.8

64 bytes from 8.8.8.8: icmp_req=1 ttl=53 time=31 ms
64 bytes from 8.8.8.8: icmp_req=2 ttl=53 time=31 ms
64 bytes from 8.8.8.8: icmp_req=3 ttl=53 time=30 ms
Request timeout for icmp_seq 4
64 bytes from 8.8.8.8: icmp_req=5 ttl=53 time=31 ms


Trace Test:

traceroute -n 197.242.144.102

1 192.168.1.1 1 ms 1 ms 1 ms
2 Request timed out * * *
3 169.1.5.1 9 ms 56 ms 9 ms
4 169.1.5.1 15 ms 11 ms 12 ms
5 41.164.52.4 31 ms 11 ms 36 ms
6 172.18.32.3 13 ms 22 ms 15 ms
7 196.223.22.3 15 ms 13 ms 11 ms
8 196.44.0.7 11 ms 12 ms 18 ms
9 196.44.31.6 57 ms 37 ms 44 ms
10 196.44.0.2 33 ms 51 ms
196.30.1.5 52 ms
11 196.31.220.2 33 ms 36 ms
196.30.1.5 58 ms
12 196.31.63.2 33 ms 33 ms
196.31.220.2 43 ms
13 196.30.42.1 37 ms 36 ms
196.31.63.2 48 ms
14 197.242.144.1 33 ms 76 ms
196.30.42.1 199 ms
15 197.242.144.1 45 ms


traceroute -n 8.8.8.8

1 192.168.1.1 1 ms 1 ms 1 ms
2 Request timed out * * *
3 169.1.5.1 33 ms 13 ms 11 ms
4 169.1.5.1 9 ms 21 ms 30 ms
5 41.164.52.4 14 ms 10 ms 32 ms
6 172.18.1.1 31 ms 31 ms 32 ms
7 72.14.194.2 31 ms 31 ms 42 ms
8 72.14.239.5 39 ms 31 ms 34 ms
9 8.8.8.8 45 ms 31 ms 31 ms


DNS Test:

nslookup www.afrihost.com

Name: www.afrihost.com
Address: 41.181.185.18


nslookup www.google.com

Name: www.google.com
Address: 197.84.135.59


nslookup thishouldfail.afrihost.com

** server can't find thisshouldfail.com: NXDOMAIN

 
Great news!
There are still some intermittent-nes (if that's a word) around this morning though.

again, whether thats due to your data, or just the line syncing fine at the moment, im not sure.

Afriguy, i have sent Afriman a request, so im hoping to see if he can accomodate that request. But if you can check with him, then let me know. I signed up now with your 10GB + 10GB package at R49 for the kid to use, but if the request is good, then ill look to increase that to a bigger package. :)
 
Our network team hasn't stopped working on this, if there was a quick fix available it would have been done already.
While there have been improvements, it's not up to 100%.

Hi AfriGuy, Maybe check first before making this statement as it is now really broken in Durban, else people will shout at you :-(
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X