Afrihost Capped DSL Feedback

[electrofreeze]

there is no separate issue if you read my post you will see that it happens every 6 days and who does that in the middle of the day

 

[AfriGenie]

there is no separate issue if you read my post you will see that it happens every 6 days and who does that in the middle of the day

Yes, a session that has been open for 6 days, will be closed by our system to allow a new session to start.

You can get around this by restarting our modem manually at a more appropriate time every 5th day for example.

On the bright side, at least your DSL Line is stable enough that you are continuously seeing sessions that last 6 days.

 

[jordaalo]

Good day

Here to start... I've had the weirdest issue for about 3 weeks now. The issue is that my Capped 4mb line will go down every day at 10am and will stay down, or at least be unusable, till 6pm the same day. The next day it will go down at 10am and go back up at 6pm. Now remember that the same router will stay connected during this time. At 10am it goes down and at 6pm it will go back up with no restart needed. While the line goes down I will perhaps get a download speed of 0.1MB and Upload of around 0.00mb, 0.03mb, 0.1mb or even 0.4mb. When its up again I use to get 3.0mb and even 3.2mb and upload of 0.3 and 0.4mb. This was normal for me.

So I started to log calls. At 1st Afrihost responded a day later and always blaming me. Then I started to use another router and with 2 user IDs. No change. I also went as far to get a guest account from another ISP and the same happened on both routers (after 10am). After 6am both performed as I expected my line to perform with all user ids.

So I started to log new calls by phoning. This proved a waste of time and air time. So I started to log calls via your Clientzone. This is where things started to get very sh-tty. VERY. But a Open Serve dude was send to me while I was at work and I had to ask for time off to go and assist him (Not the other way around). I was hopeful since this was at around 11am on 20/06/2017. But on arrival he just said that he cannot find any errors on my line. When I say I dont believe him, he shows me on his laptop the logs where he did tests. There was 5 logs. Starting at just before 10am that was successful. Then 3 after 10am that failed. Then a time gap and then one at about 10:30am that was successful again. I pointed that out but he just kept saying that there is no issue. So I asked him to come with me into my house so I can show him all my findings. He did so. So I showed him my crappy download and uploads during the times I was talking about. Then I showed him how my line should run. This is where he talked for the 1st time. His answer was "There is no why I EVER had 4mb download". I showed him evidence that I use to have 4mb for 4 years now, and he just said no. He then did test where it kept showing that my max sync speed should be 4MB down and 1MB up. But he kept saying this is not true. From here on out my line is downgraded to a 2mb line. To be more on the dot, 2.3mb down and 0.3 up. Now this is where I started to tantrum and shout and scream... But dont worry... This was also the last day I heard anything from Afrihost and Telkom. Now I'm just being ignored. The problem I have with this is:
1- I paid in full for a service I'm not receiving
2- the next day my problem was back and my line even worse than it was.
3- I pay Afrihost to manage my line, but at this moment I'm doing all the management on my line.
4- My wife use to be able to watch youtube and even play with me online. now If more than 1 device tries to access the network the line seems to sh-t all over itself.
5- I cannot use my line when I want to. I only get time to really enjoy it over weekends and now I can only after 6pm. Monday - Sunday, and since I DARED to complain, I cant even use it during the "Prime Time" somebody has set for me for some sick reason.

So naturally I really started to spam the sh-t out of Afrihost and Hello Peter and and and, and do you know what happened? NOTHING. But here is where it gets very interesting... After my massive "sh-t myself" day, I got home and was looking forward to shooting a few random online people in the face. So I waited for my prime time to start and I went online... Just to find that I cant. Again, because I dared to complain, I was punished and my "Prime Time" was moved from 6pm to 7:30pm. 1.8 download and 0.3 upload. Another downgrade.

My sync is 0. My SNR is 0. This is all stats I'm getting off from your site.

What am I paying for? And I'm sure at the end of this month you will just keep taking my money. Steeling it is more like it. What is the issue? Is Afrihost mad at me? Why? Please... So lets go back to the good old days where I get what I paid for and then we dont bother each other.

Here is all the ref number they send me... Probably the only reason I even got this is coz its automated. Phone calls ref numbers? None. They just never give it...
PSS-211-52774 - 1 day later responce
JXD-612-26745 - 2 days later responce and downgrade of my line
NEL-289-56796 - 0 responce and downgrade of my line since I dared to complain... SIES LOUIS!

Here is a PING to 8.8.8.8 during the "We dont want you to use our bandwidth!" time
Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=2216ms TTL=57
Reply from 8.8.8.8: bytes=32 time=2344ms TTL=57
Reply from 8.8.8.8: bytes=32 time=2377ms TTL=57
Reply from 8.8.8.8: bytes=32 time=2559ms TTL=57
Reply from 8.8.8.8: bytes=32 time=2330ms TTL=57
Reply from 8.8.8.8: bytes=32 time=1985ms TTL=57
Reply from 8.8.8.8: bytes=32 time=2204ms TTL=57
Reply from 8.8.8.8: bytes=32 time=2320ms TTL=57
Reply from 8.8.8.8: bytes=32 time=3187ms TTL=57
Reply from 8.8.8.8: bytes=32 time=2874ms TTL=57
Reply from 8.8.8.8: bytes=32 time=2058ms TTL=57
Reply from 8.8.8.8: bytes=32 time=177ms TTL=57
Reply from 8.8.8.8: bytes=32 time=424ms TTL=57
Reply from 8.8.8.8: bytes=32 time=35ms TTL=57
Reply from 8.8.8.8: bytes=32 time=41ms TTL=57
Reply from 8.8.8.8: bytes=32 time=34ms TTL=57
Reply from 8.8.8.8: bytes=32 time=320ms TTL=57
Reply from 8.8.8.8: bytes=32 time=2541ms TTL=57
Reply from 8.8.8.8: bytes=32 time=2361ms TTL=57
Reply from 8.8.8.8: bytes=32 time=1401ms TTL=57
Reply from 8.8.8.8: bytes=32 time=2768ms TTL=57
Reply from 8.8.8.8: bytes=32 time=3092ms TTL=57
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 8.8.8.8: bytes=32 time=1565ms TTL=57
Reply from 8.8.8.8: bytes=32 time=1018ms TTL=57
Reply from 8.8.8.8: bytes=32 time=2119ms TTL=57
Reply from 8.8.8.8: bytes=32 time=1562ms TTL=57
Reply from 8.8.8.8: bytes=32 time=1810ms TTL=57
Reply from 8.8.8.8: bytes=32 time=1129ms TTL=57
Reply from 8.8.8.8: bytes=32 time=1320ms TTL=57
Reply from 8.8.8.8: bytes=32 time=1186ms TTL=57
Reply from 8.8.8.8: bytes=32 time=1251ms TTL=57
Reply from 8.8.8.8: bytes=32 time=727ms TTL=57
Reply from 8.8.8.8: bytes=32 time=213ms TTL=57
Reply from 8.8.8.8: bytes=32 time=675ms TTL=57
Reply from 8.8.8.8: bytes=32 time=706ms TTL=57
Reply from 8.8.8.8: bytes=32 time=773ms TTL=57
Reply from 8.8.8.8: bytes=32 time=1524ms TTL=57
Reply from 8.8.8.8: bytes=32 time=1218ms TTL=57
Reply from 8.8.8.8: bytes=32 time=1215ms TTL=57
Reply from 8.8.8.8: bytes=32 time=2230ms TTL=57
Reply from 8.8.8.8: bytes=32 time=2970ms TTL=57
Reply from 8.8.8.8: bytes=32 time=3816ms TTL=57
Request timed out.
Request timed out.
Reply from 8.8.8.8: bytes=32 time=3944ms TTL=57
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 8.8.8.8: bytes=32 time=2154ms TTL=57
Reply from 8.8.8.8: bytes=32 time=2418ms TTL=57
Reply from 8.8.8.8: bytes=32 time=2793ms TTL=57
Reply from 8.8.8.8: bytes=32 time=2440ms TTL=57
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 8.8.8.8: bytes=32 time=3277ms TTL=57
Reply from 8.8.8.8: bytes=32 time=3286ms TTL=57
Reply from 8.8.8.8: bytes=32 time=2954ms TTL=57
Reply from 8.8.8.8: bytes=32 time=2387ms TTL=57
Reply from 8.8.8.8: bytes=32 time=2538ms TTL=57
Reply from 8.8.8.8: bytes=32 time=3232ms TTL=57
Reply from 8.8.8.8: bytes=32 time=2567ms TTL=57
Reply from 8.8.8.8: bytes=32 time=2631ms TTL=57
Reply from 8.8.8.8: bytes=32 time=2405ms TTL=57
Reply from 8.8.8.8: bytes=32 time=2718ms TTL=57
Reply from 8.8.8.8: bytes=32 time=2540ms TTL=57

Ping statistics for 8.8.8.8:
Packets: Sent = 79, Received = 58, Lost = 21 (26% loss),
Approximate round trip times in milli-seconds:
Minimum = 34ms, Maximum = 3944ms, Average = 1947ms

Please. PLEASE. I just want help. I just want what I paid for. PLEASE help

 

[jordaalo]

So? Can I expect another down grade on my line with a free and complimentary "No Response"?

 

[Pulserider]

So? Can I expect another down grade on my line with a free and complimentary "No Response"?

I was almost in the same situation. I could not use my internet and it got worst. ISP's blame Telkom, Telkom blames ISP's. Exchange congestion, line problems, port resets and nothing gets solved.

I went with a good WISP - problems solved. There is no more issues and I get what I am paying for. WISP's is on the raise because of these type of problems...

 

[electrofreeze]

Yes, a session that has been open for 6 days, will be closed by our system to allow a new session to start.

You can get around this by restarting our modem manually at a more appropriate time every 5th day for example.

On the bright side, at least your DSL Line is stable enough that you are continuously seeing sessions that last 6 days.

i dont want to reset the modem as we use the internet 24/7 so just sort out your side so that it wont happen again as it never use to work like this before
we are paying for internet use not for modem and line resets

 

[AfriFella]

Good day

Here to start... I've had the weirdest issue for about 3 weeks now. The issue is that my Capped 4mb line will go down every day at 10am and will stay down, or at least be unusable, till 6pm the same day. The next day it will go down at 10am and go back up at 6pm. Now remember that the same router will stay connected during this time. At 10am it goes down and at 6pm it will go back up with no restart needed. While the line goes down I will perhaps get a download speed of 0.1MB and Upload of around 0.00mb, 0.03mb, 0.1mb or even 0.4mb. When its up again I use to get 3.0mb and even 3.2mb and upload of 0.3 and 0.4mb. This was normal for me.

So I started to log calls. At 1st Afrihost responded a day later and always blaming me. Then I started to use another router and with 2 user IDs. No change. I also went as far to get a guest account from another ISP and the same happened on both routers (after 10am). After 6am both performed as I expected my line to perform with all user ids.

So I started to log new calls by phoning. This proved a waste of time and air time. So I started to log calls via your Clientzone. This is where things started to get very sh-tty. VERY. But a Open Serve dude was send to me while I was at work and I had to ask for time off to go and assist him (Not the other way around). I was hopeful since this was at around 11am on 20/06/2017. But on arrival he just said that he cannot find any errors on my line. When I say I dont believe him, he shows me on his laptop the logs where he did tests. There was 5 logs. Starting at just before 10am that was successful. Then 3 after 10am that failed. Then a time gap and then one at about 10:30am that was successful again. I pointed that out but he just kept saying that there is no issue. So I asked him to come with me into my house so I can show him all my findings. He did so. So I showed him my crappy download and uploads during the times I was talking about. Then I showed him how my line should run. This is where he talked for the 1st time. His answer was "There is no why I EVER had 4mb download". I showed him evidence that I use to have 4mb for 4 years now, and he just said no. He then did test where it kept showing that my max sync speed should be 4MB down and 1MB up. But he kept saying this is not true. From here on out my line is downgraded to a 2mb line. To be more on the dot, 2.3mb down and 0.3 up. Now this is where I started to tantrum and shout and scream... But dont worry... This was also the last day I heard anything from Afrihost and Telkom. Now I'm just being ignored. The problem I have with this is:
1- I paid in full for a service I'm not receiving
2- the next day my problem was back and my line even worse than it was.
3- I pay Afrihost to manage my line, but at this moment I'm doing all the management on my line.
4- My wife use to be able to watch youtube and even play with me online. now If more than 1 device tries to access the network the line seems to sh-t all over itself.
5- I cannot use my line when I want to. I only get time to really enjoy it over weekends and now I can only after 6pm. Monday - Sunday, and since I DARED to complain, I cant even use it during the "Prime Time" somebody has set for me for some sick sexual reason.

So naturally I really started to spam the sh-t out of Afrihost and Hello Peter and and and, and do you know what happened? NOTHING. But here is where it gets very interesting... After my massive "sh-t myself" day, I got home and was looking forward to shooting a few random online people in the face. So I waited for my prime time to start and I went online... Just to find that I cant. Again, because I dared to complain, I was punished and my "Prime Time" was moved from 6pm to 7:30pm. 1.8 download and 0.3 upload. Another downgrade.

My sync is 0. My SNR is 0. This is all stats I'm getting off from your site.

What am I paying for? And I'm sure at the end of this month you will just keep taking my money. Steeling it is more like it. What is the issue? Is daddy Afrihost mad at me? Why? Is it because I like to spank naked GI JOES? Well... He likes to abandon his clients after a very nasty molestation session. I think that we are quits... So lets go back to the good old days where I get what I paid for and then we dont bother each other anymore?

Here is all the ref number they send me... Probably the only reason I even got this is coz its automated. Phone calls ref numbers? None. They just never give it...
PSS-211-52774 - 1 day later responce
JXD-612-26745 - 2 days later responce and downgrade of my line
NEL-289-56796 - 0 responce and downgrade of my line since I dared to complain... SIES LOUIS!

Here is a PING to 8.8.8.8 during the "We dont want you to use our bandwidth!" time
Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=2216ms TTL=57
Reply from 8.8.8.8: bytes=32 time=2344ms TTL=57
Reply from 8.8.8.8: bytes=32 time=2377ms TTL=57
Reply from 8.8.8.8: bytes=32 time=2559ms TTL=57
Reply from 8.8.8.8: bytes=32 time=2330ms TTL=57
Reply from 8.8.8.8: bytes=32 time=1985ms TTL=57
Reply from 8.8.8.8: bytes=32 time=2204ms TTL=57
Reply from 8.8.8.8: bytes=32 time=2320ms TTL=57
Reply from 8.8.8.8: bytes=32 time=3187ms TTL=57
Reply from 8.8.8.8: bytes=32 time=2874ms TTL=57
Reply from 8.8.8.8: bytes=32 time=2058ms TTL=57
Reply from 8.8.8.8: bytes=32 time=177ms TTL=57
Reply from 8.8.8.8: bytes=32 time=424ms TTL=57
Reply from 8.8.8.8: bytes=32 time=35ms TTL=57
Reply from 8.8.8.8: bytes=32 time=41ms TTL=57
Reply from 8.8.8.8: bytes=32 time=34ms TTL=57
Reply from 8.8.8.8: bytes=32 time=320ms TTL=57
Reply from 8.8.8.8: bytes=32 time=2541ms TTL=57
Reply from 8.8.8.8: bytes=32 time=2361ms TTL=57
Reply from 8.8.8.8: bytes=32 time=1401ms TTL=57
Reply from 8.8.8.8: bytes=32 time=2768ms TTL=57
Reply from 8.8.8.8: bytes=32 time=3092ms TTL=57
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 8.8.8.8: bytes=32 time=1565ms TTL=57
Reply from 8.8.8.8: bytes=32 time=1018ms TTL=57
Reply from 8.8.8.8: bytes=32 time=2119ms TTL=57
Reply from 8.8.8.8: bytes=32 time=1562ms TTL=57
Reply from 8.8.8.8: bytes=32 time=1810ms TTL=57
Reply from 8.8.8.8: bytes=32 time=1129ms TTL=57
Reply from 8.8.8.8: bytes=32 time=1320ms TTL=57
Reply from 8.8.8.8: bytes=32 time=1186ms TTL=57
Reply from 8.8.8.8: bytes=32 time=1251ms TTL=57
Reply from 8.8.8.8: bytes=32 time=727ms TTL=57
Reply from 8.8.8.8: bytes=32 time=213ms TTL=57
Reply from 8.8.8.8: bytes=32 time=675ms TTL=57
Reply from 8.8.8.8: bytes=32 time=706ms TTL=57
Reply from 8.8.8.8: bytes=32 time=773ms TTL=57
Reply from 8.8.8.8: bytes=32 time=1524ms TTL=57
Reply from 8.8.8.8: bytes=32 time=1218ms TTL=57
Reply from 8.8.8.8: bytes=32 time=1215ms TTL=57
Reply from 8.8.8.8: bytes=32 time=2230ms TTL=57
Reply from 8.8.8.8: bytes=32 time=2970ms TTL=57
Reply from 8.8.8.8: bytes=32 time=3816ms TTL=57
Request timed out.
Request timed out.
Reply from 8.8.8.8: bytes=32 time=3944ms TTL=57
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 8.8.8.8: bytes=32 time=2154ms TTL=57
Reply from 8.8.8.8: bytes=32 time=2418ms TTL=57
Reply from 8.8.8.8: bytes=32 time=2793ms TTL=57
Reply from 8.8.8.8: bytes=32 time=2440ms TTL=57
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 8.8.8.8: bytes=32 time=3277ms TTL=57
Reply from 8.8.8.8: bytes=32 time=3286ms TTL=57
Reply from 8.8.8.8: bytes=32 time=2954ms TTL=57
Reply from 8.8.8.8: bytes=32 time=2387ms TTL=57
Reply from 8.8.8.8: bytes=32 time=2538ms TTL=57
Reply from 8.8.8.8: bytes=32 time=3232ms TTL=57
Reply from 8.8.8.8: bytes=32 time=2567ms TTL=57
Reply from 8.8.8.8: bytes=32 time=2631ms TTL=57
Reply from 8.8.8.8: bytes=32 time=2405ms TTL=57
Reply from 8.8.8.8: bytes=32 time=2718ms TTL=57
Reply from 8.8.8.8: bytes=32 time=2540ms TTL=57

Ping statistics for 8.8.8.8:
Packets: Sent = 79, Received = 58, Lost = 21 (26% loss),
Approximate round trip times in milli-seconds:
Minimum = 34ms, Maximum = 3944ms, Average = 1947ms

Please. PLEASE. I just want help. I just want what I paid for. PLEASE help

So? Can I expect another down grade on my line with a free and complimentary "No Response"?

Hi there jordaalo. Thanks for reaching out and for your detailed post. I'm sure we'll be able to find the cause of this together. To start off, I'm really sorry to hear that you've been having such a poor experience and that you have had to resort to such extreme measure in order to get heard. This really isn't something I like to hear people go through. I'm sorry to hear that you had to.

Your "like-clockwork" connectivity issues, tied in with the high latency on your attached pingtest result, immediately indicates to me that you're suffering from exchange congestion. I know this is something that might have been suggested to you previously, but we'll be happy to troubleshoot this with you in order to confirm. There are other factors that might also be causing your issues, all of which will have to be looked at through troubleshooting - and I'll be happy to help you out over PM. I think it's very important to note that you are not being "punished" or deliberately downgraded, as you have suggested in your post. All connection problems have a cause and I'm happy to help you find yours.

Also, I'm not sure about your molestation remark? I must say that this can be considered a little "off" and might offend others in this forum, or whoever might come across it. I would really appreciate it if you could edit that part of your post as it won't remove any of the context in your complaint.

In the end, I just want to help you resolve your issue. We want everyone to have the best experience. Looking forward to chatting to you over in PM.

 

[AfriFella]

I was almost in the same situation. I could not use my internet and it got worst. ISP's blame Telkom, Telkom blames ISP's. Exchange congestion, line problems, port resets and nothing gets solved.

I went with a good WISP - problems solved. There is no more issues and I get what I am paying for. WISP's is on the raise because of these type of problems...

I'm glad to hear that you found a personal solution that works for you, andreh.

If you have any Afrihost related queries, please feel free to post them here.

 

[AfriFella]

i dont want to reset the modem as we use the internet 24/7 so just sort out your side so that it wont happen again as it never use to work like this before
we are paying for internet use not for modem and line resets

This is not something that has to be sorted out on our side. I have to stress that this has always been the way our radius manages sessions. In fact, on the old MTN network, sessions were reset every 3 days. I think Genie offered great advice when he suggested that you manage the time you reboot your router. A routine reboot every few days is always good practice.

 

[mister]

I tell you what, you reboot your core every few days, and I'll reboot my DSL router every few days. How does that sound?
Sorry, but these things do NOT require to be rebooted every few days. You, are out right talking bull****.

I wish I thought of telling them myself to reboot their core... +reps

 

[AfriFella]

I wish I thought of telling them myself to reboot their core... +reps

Luckily that's not the case.

 

[electrofreeze]

I don't know what you mean by rebooting the "core", or where you got that information from? We do not reboot the "core". Specific DSL internet sessions get closed by the radius server every 6 days, which assists our network team with reporting. This is a feature that has always been in place and has, in fact, evolved from every 1.5 days to 3 days (MTN) to 6 days (currently). Other ISPs have similar features in place, some of which resets a DSL connection every 24 hours. Furthermore, the 6 day radius reset does not apply to non Openserve fibre connections.



I'm sorry you feel that way. I think it's a good idea to understand that we do not reboot our "core network" before conspiracies start flying around.

do you even understand what people are saying when you read their posts because it sure as hell doesnt look like it

 

[Praeses]

Will people please stop being a-holes to the reps on this forum. Rudeness has chased away many reps in the past (maybe not AH, but others). Much respect to AfriFella for even bothering to respond to such posts.

 

[Icemanbrfc]

Will people please stop being a-holes to the reps on this forum. Rudeness has chased away many reps in the past (maybe not AH, but others). Much respect to AfriFella for even bothering to respond to such posts.

What Praeses said ^^

 

[jordaalo]

Hi there jordaalo. Thanks for reaching out and for your detailed post. I'm sure we'll be able to find the cause of this together. To start off, I'm really sorry to hear that you've been having such a poor experience and that you have had to resort to such extreme measure in order to get heard. This really isn't something I like to hear people go through. I'm sorry to hear that you had to.

Your "like-clockwork" connectivity issues, tied in with the high latency on your attached pingtest result, immediately indicates to me that you're suffering from exchange congestion. I know this is something that might have been suggested to you previously, but we'll be happy to troubleshoot this with you in order to confirm. There are other factors that might also be causing your issues, all of which will have to be looked at through troubleshooting - and I'll be happy to help you out over PM. I think it's very important to note that you are not being "punished" or deliberately downgraded, as you have suggested in your post. All connection problems have a cause and I'm happy to help you find yours.

Also, I'm not sure about your molestation remark? I must say that this can be considered a little "off" and might offend others in this forum, or whoever might come across it. I would really appreciate it if you could edit that part of your post as it won't remove any of the context in your complaint.

In the end, I just want to help you resolve your issue. We want everyone to have the best experience. Looking forward to chatting to you over in PM.

I appreciate any help I can get. And sorry about the remark. I will try to find out how to edit it out. And please understand that I'm not rude towards those who helps. I've been through hell so far and I know I my sense of humor isnt for all. Clearly this is the place to find help and I will be more than happy to sing your praises if we can at the very least get my line to a point again where I can use it over the weekends all the time.

Now this is probably gonna get me "Banned for stupidity" for this question, but how do I do the PM?

Thanks for he response and future help - you do not know how better this makes me feel. please lets get this out of the way. let me know what to do

 

[moedawood]

I appreciate any help I can get. And sorry about the remark. I will try to find out how to edit it out. And please understand that I'm not rude towards those who helps. I've been through hell so far and I know I my sense of humor isnt for all. Clearly this is the place to find help and I will be more than happy to sing your praises if we can at the very least get my line to a point again where I can use it over the weekends all the time.

Now this is probably gonna get me "Banned for stupidity" for this question, but how do I do the PM?

Thanks for he response and future help - you do not know how better this makes me feel. please lets get this out of the way. let me know what to do

Ping bras.afrihost.com

It measures latency to the exchange.

 

[jordaalo]

Ping bras.afrihost.com

It measures latency to the exchange.

Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=57ms TTL=63
Reply from 155.239.255.250: bytes=32 time=49ms TTL=63
Reply from 155.239.255.250: bytes=32 time=53ms TTL=63
Reply from 155.239.255.250: bytes=32 time=69ms TTL=63
Reply from 155.239.255.250: bytes=32 time=48ms TTL=63
Reply from 155.239.255.250: bytes=32 time=64ms TTL=63
Reply from 155.239.255.250: bytes=32 time=69ms TTL=63
Reply from 155.239.255.250: bytes=32 time=59ms TTL=63
Reply from 155.239.255.250: bytes=32 time=66ms TTL=63
Reply from 155.239.255.250: bytes=32 time=62ms TTL=63
Reply from 155.239.255.250: bytes=32 time=66ms TTL=63
Reply from 155.239.255.250: bytes=32 time=56ms TTL=63
Reply from 155.239.255.250: bytes=32 time=49ms TTL=63
Reply from 155.239.255.250: bytes=32 time=64ms TTL=63
Reply from 155.239.255.250: bytes=32 time=44ms TTL=63
Reply from 155.239.255.250: bytes=32 time=60ms TTL=63
Reply from 155.239.255.250: bytes=32 time=53ms TTL=63
Reply from 155.239.255.250: bytes=32 time=67ms TTL=63
Reply from 155.239.255.250: bytes=32 time=46ms TTL=63
Reply from 155.239.255.250: bytes=32 time=60ms TTL=63
Reply from 155.239.255.250: bytes=32 time=64ms TTL=63
Reply from 155.239.255.250: bytes=32 time=54ms TTL=63
Reply from 155.239.255.250: bytes=32 time=59ms TTL=63
Reply from 155.239.255.250: bytes=32 time=47ms TTL=63
Reply from 155.239.255.250: bytes=32 time=51ms TTL=63
Reply from 155.239.255.250: bytes=32 time=69ms TTL=63
Reply from 155.239.255.250: bytes=32 time=47ms TTL=63
Reply from 155.239.255.250: bytes=32 time=63ms TTL=63
Reply from 155.239.255.250: bytes=32 time=45ms TTL=63
Reply from 155.239.255.250: bytes=32 time=48ms TTL=63
Reply from 155.239.255.250: bytes=32 time=60ms TTL=63
Reply from 155.239.255.250: bytes=32 time=60ms TTL=63
Reply from 155.239.255.250: bytes=32 time=61ms TTL=63
Reply from 155.239.255.250: bytes=32 time=51ms TTL=63
Reply from 155.239.255.250: bytes=32 time=58ms TTL=63
Reply from 155.239.255.250: bytes=32 time=62ms TTL=63
Reply from 155.239.255.250: bytes=32 time=47ms TTL=63
Reply from 155.239.255.250: bytes=32 time=47ms TTL=63
Reply from 155.239.255.250: bytes=32 time=64ms TTL=63
Reply from 155.239.255.250: bytes=32 time=56ms TTL=63
Reply from 155.239.255.250: bytes=32 time=63ms TTL=63
Reply from 155.239.255.250: bytes=32 time=44ms TTL=63
Reply from 155.239.255.250: bytes=32 time=60ms TTL=63
Reply from 155.239.255.250: bytes=32 time=63ms TTL=63
Reply from 155.239.255.250: bytes=32 time=54ms TTL=63
Reply from 155.239.255.250: bytes=32 time=66ms TTL=63
Reply from 155.239.255.250: bytes=32 time=70ms TTL=63
Reply from 155.239.255.250: bytes=32 time=51ms TTL=63
Reply from 155.239.255.250: bytes=32 time=52ms TTL=63
Reply from 155.239.255.250: bytes=32 time=51ms TTL=63
Reply from 155.239.255.250: bytes=32 time=67ms TTL=63
Reply from 155.239.255.250: bytes=32 time=52ms TTL=63

Ping statistics for 155.239.255.250:
Packets: Sent = 52, Received = 52, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 44ms, Maximum = 70ms, Average = 57ms

To be honest, I not sure if this is good or bad. Also, this was at 7:12am. Like I said... at precisely 10:00am (not 9:59am or 10:01am) my line will go down and I can most of the time do nothing for testing. But to add, my knowledge of Internet stuff is "Noob" at best.

On that note, I'm not sure how AfriFella can help after 10:00am. But he probibly has a kick butt trick or 6. Hopefully. Will be so great to put all of this behind me.

 

[jordaalo]

My line went down again at 9:40am today. Not sure why the change in times... Perhaps coz i complained again... And... Again my weekend of fun is runed. Ag man. I have no connection what so ever to test. Must say was so hopeful... Please help me out. Not sure what i did to deserve this. Please help me

 

[jordaalo]

Okay. According to Telkomza (jd} i contacted via twitter my ports was reseted and adjusted. He requested that it reset and try again. This was 9:10am. I did as he asked and at abou 9:40am i lost connection. I infromed them again. But they take long to respond. Probibly very busy.

 

[jordaalo]

Thanks to the help of JD a technician is called to assist. Anybody following this... Hope you niticed that all progress made so far is because of what i did. Now remeber that i do pay afrihost every month to manage my line. Just sayan