Afrihost Uncapped ADSL Feedback (Pt3)

Status
Not open for further replies.
Zertop said:
Hi DeathStrike,

Please would you run my second tool in my signature :)

Z
Click to expand...

Sorry for late response. i used a turbocharge and didn't want to mess with the results....

[/B] [/U]
Your average ping was 112ms
Your maximum ping was 132ms

Looking at your average ping, there is definitely something wrong with your line-( Please post the results (at the end of the program) into the forum for advice


Detailed Report

Code: 
Ping results for last hop before account switches to ISP's hardware (Hop 2 on Tracert) 

Pinging 105.236.8.65 with 32 bytes of data:
Request timed out.
Reply from 105.236.8.65: bytes=32 time=99ms TTL=254
Reply from 105.236.8.65: bytes=32 time=111ms TTL=254
Reply from 105.236.8.65: bytes=32 time=123ms TTL=254
Request timed out.
Reply from 105.236.8.65: bytes=32 time=121ms TTL=254
Reply from 105.236.8.65: bytes=32 time=109ms TTL=254
Reply from 105.236.8.65: bytes=32 time=116ms TTL=254
Reply from 105.236.8.65: bytes=32 time=90ms TTL=254
Reply from 105.236.8.65: bytes=32 time=121ms TTL=254
Reply from 105.236.8.65: bytes=32 time=120ms TTL=254
Reply from 105.236.8.65: bytes=32 time=119ms TTL=254
Reply from 105.236.8.65: bytes=32 time=110ms TTL=254
Reply from 105.236.8.65: bytes=32 time=89ms TTL=254
Reply from 105.236.8.65: bytes=32 time=111ms TTL=254
Reply from 105.236.8.65: bytes=32 time=123ms TTL=254
Reply from 105.236.8.65: bytes=32 time=119ms TTL=254
Reply from 105.236.8.65: bytes=32 time=123ms TTL=254
Reply from 105.236.8.65: bytes=32 time=122ms TTL=254
Reply from 105.236.8.65: bytes=32 time=107ms TTL=254
Reply from 105.236.8.65: bytes=32 time=132ms TTL=254
Reply from 105.236.8.65: bytes=32 time=109ms TTL=254
Reply from 105.236.8.65: bytes=32 time=111ms TTL=254
Reply from 105.236.8.65: bytes=32 time=117ms TTL=254
Reply from 105.236.8.65: bytes=32 time=85ms TTL=254
Request timed out.
Request timed out.
Request timed out.
Reply from 105.236.8.65: bytes=32 time=121ms TTL=254
Request timed out.

Ping statistics for 105.236.8.65:
    Packets: Sent = 30, Received = 24, Lost = 6 (20% loss),
Approximate round trip times in milli-seconds:
    Minimum = 85ms, Maximum = 132ms, Average = 112ms
 
2014/04/19  9:33:16.83
 
DeathStrike said:
Sorry for late response. i used a turbocharge and didn't want to mess with the results....

[/B] [/U]
Your average ping was 112ms
Your maximum ping was 132ms

Looking at your average ping, there is definitely something wrong with your line-( Please post the results (at the end of the program) into the forum for advice


Detailed Report

Code: 
Ping results for last hop before account switches to ISP's hardware (Hop 2 on Tracert) 

Pinging 105.236.8.65 with 32 bytes of data:
Request timed out.
Reply from 105.236.8.65: bytes=32 time=99ms TTL=254
Reply from 105.236.8.65: bytes=32 time=111ms TTL=254
Reply from 105.236.8.65: bytes=32 time=123ms TTL=254
Request timed out.
Reply from 105.236.8.65: bytes=32 time=121ms TTL=254
Reply from 105.236.8.65: bytes=32 time=109ms TTL=254
Reply from 105.236.8.65: bytes=32 time=116ms TTL=254
Reply from 105.236.8.65: bytes=32 time=90ms TTL=254
Reply from 105.236.8.65: bytes=32 time=121ms TTL=254
Reply from 105.236.8.65: bytes=32 time=120ms TTL=254
Reply from 105.236.8.65: bytes=32 time=119ms TTL=254
Reply from 105.236.8.65: bytes=32 time=110ms TTL=254
Reply from 105.236.8.65: bytes=32 time=89ms TTL=254
Reply from 105.236.8.65: bytes=32 time=111ms TTL=254
Reply from 105.236.8.65: bytes=32 time=123ms TTL=254
Reply from 105.236.8.65: bytes=32 time=119ms TTL=254
Reply from 105.236.8.65: bytes=32 time=123ms TTL=254
Reply from 105.236.8.65: bytes=32 time=122ms TTL=254
Reply from 105.236.8.65: bytes=32 time=107ms TTL=254
Reply from 105.236.8.65: bytes=32 time=132ms TTL=254
Reply from 105.236.8.65: bytes=32 time=109ms TTL=254
Reply from 105.236.8.65: bytes=32 time=111ms TTL=254
Reply from 105.236.8.65: bytes=32 time=117ms TTL=254
Reply from 105.236.8.65: bytes=32 time=85ms TTL=254
Request timed out.
Request timed out.
Request timed out.
Reply from 105.236.8.65: bytes=32 time=121ms TTL=254
Request timed out.

Ping statistics for 105.236.8.65:
    Packets: Sent = 30, Received = 24, Lost = 6 (20% loss),
Approximate round trip times in milli-seconds:
    Minimum = 85ms, Maximum = 132ms, Average = 112ms
 
2014/04/19  9:33:16.83
Click to expand...

Yea, that looks like a serious line issue :(

How does the account perform on another ISP's test account (WebAfrica etc)?

Z
 
no idea. don't have another test account. used to be with mweb and had afrihost test account.

should i call telkom and ask them wtf? my line is not with afrihost.

or should i purchase one gig from web africa and test with that first?
 
DeathStrike said:
no idea. don't have another test account. used to be with mweb and had afrihost test account.

should i call telkom and ask them wtf? my line is not with afrihost.

or should i purchase one gig from web africa and test with that first?
Click to expand...
Get a free GB from WA
 
DeathStrike said:
no idea. don't have another test account. used to be with mweb and had afrihost test account.

should i call telkom and ask them wtf? my line is not with afrihost.

or should i purchase one gig from web africa and test with that first?
Click to expand...

If you could test with a free GB from WA and run the tool again, that would help a lot :)

It looks to be a line issue, but this is just to make sure!

Z
 
Gunner182 said:
I was just about ask if they eased off on the shaping, but doesn't look like anything has changed. I'm on business at the moment and want to go back uncapped as ever only download during the early hours of the morning. Why doesn't Afrihost ease off on the shaping at that time? I know mweb used to do it.
Click to expand...

How early in the morning? Before the capacity problems I would only start seeing shaping at around 9-10AM so if you download before then it should be okay, scheduling late night downloads also would help, there used to be no shaping then. You probably would want to wait and see what people are saying after Tuesday when most of us are back at work.
 
Gunner182 said:
I was just about ask if they eased off on the shaping, but doesn't look like anything has changed. I'm on business at the moment and want to go back uncapped as ever only download during the early hours of the morning. Why doesn't Afrihost ease off on the shaping at that time? I know mweb used to do it.
Click to expand...
I posted a pic when I was shaped at 00:45.
My records seem to indicate that shaping soon dropped after that and I remained unshaped from then till now (10:05)
Avg dl speed was high 300's on my 4Mbps line, so I'm happy with that.

Hourly.PNG
 
Last edited:
TwilightWalker said:
How early in the morning? Before the capacity problems I would only start seeing shaping at around 9-10AM so if you download before then it should be okay, scheduling late night downloads also would help, there used to be no shaping then. You probably would want to wait and see what people are saying after Tuesday when most of us are back at work.
Click to expand...

Wee hours of the morning between 12AM and 6AM as illustrated below.

RoMark said:
I posted the pic where I was shaped at 00:45.
My reckords seem to indicate that shaping soon after that and I remained unshaped from then till now (10:05)
Avg dl speed was high 300's on my 4Mbps line, so I'm happy with that.

View attachment 113296
Click to expand...

That's impressive! What's your shaping policy on in client zone?
 
Gunner182 said:
and how many GBs have you downloaded so far this month?

Edit: In which part of the country are you?
Click to expand...

54GB.

I think I was on 38GB for the month before the upgrade, as I mostly used another ISP for my personal use, while the rest of the house used the AH account.
Since then I've exclusively used AH to see how the account handles and so far I'm happy.
My monthly usage is usually between 200 and 300GB.
My P2P downloads are scheduled for 00:00 - 06:00, except for last night when I decided to run it till 07:00 to see what would happen.

I'm in the Eastern Cape and was badly affected by the shortage in the South.
 
RoMark said:
54GB.

I think I was on 38GB for the month before the upgrade, as I mostly used another ISP for my personal use, while the rest of the house used the AH account.
Since then I've exclusively used AH to see how the account handles and so far I'm happy.
My monthly usage is usually between 200 and 300GB.
My P2P downloads are scheduled for 00:00 - 06:00, except for last night when I decided to run it till 07:00 to see what would happen.

I'm in the Eastern Cape and was badly affected by the shortage in the South.
Click to expand...

Ohk cul, sounds positive. I think I'll make the switch back to shaped uncapped during the week. I'll prob PM you again to see if anything has changed. Thanks though.:)
 
Zertop said:
If you could test with a free GB from WA and run the tool again, that would help a lot :)

It looks to be a line issue, but this is just to make sure!

Z
Click to expand...

Ok got WA account. the loading speed seems bit better. but the report says line is still faulty. I have also called telkom and had them reset my ports as well before running this test.


Zertop's "Is it my Line" Results
Basic Report:

Your average ping was 294ms
Your maximum ping was 619ms

Looking at your average ping, there is definitely something wrong with your line-( Please post the results (at the end of the program) into the forum for advice


Detailed Report

Code: 
Ping results for last hop before account switches to ISP's hardware (Hop 2 on Tracert) 

Pinging 196.210.170.129 with 32 bytes of data:
Request timed out.
Request timed out.
Reply from 196.210.170.129: bytes=32 time=104ms TTL=254
Reply from 196.210.170.129: bytes=32 time=121ms TTL=254
Reply from 196.210.170.129: bytes=32 time=118ms TTL=254
Reply from 196.210.170.129: bytes=32 time=114ms TTL=254
Reply from 196.210.170.129: bytes=32 time=105ms TTL=254
Reply from 196.210.170.129: bytes=32 time=91ms TTL=254
Reply from 196.210.170.129: bytes=32 time=490ms TTL=254
Reply from 196.210.170.129: bytes=32 time=474ms TTL=254
Reply from 196.210.170.129: bytes=32 time=443ms TTL=254
Reply from 196.210.170.129: bytes=32 time=619ms TTL=254
Reply from 196.210.170.129: bytes=32 time=272ms TTL=254
Reply from 196.210.170.129: bytes=32 time=381ms TTL=254
Reply from 196.210.170.129: bytes=32 time=119ms TTL=254
Reply from 196.210.170.129: bytes=32 time=568ms TTL=254
Reply from 196.210.170.129: bytes=32 time=517ms TTL=254
Reply from 196.210.170.129: bytes=32 time=112ms TTL=254
Reply from 196.210.170.129: bytes=32 time=350ms TTL=254
Request timed out.
Reply from 196.210.170.129: bytes=32 time=105ms TTL=254
Reply from 196.210.170.129: bytes=32 time=145ms TTL=254
Request timed out.
Reply from 196.210.170.129: bytes=32 time=102ms TTL=254
Reply from 196.210.170.129: bytes=32 time=542ms TTL=254
Reply from 196.210.170.129: bytes=32 time=312ms TTL=254
Request timed out.
Reply from 196.210.170.129: bytes=32 time=317ms TTL=254
Reply from 196.210.170.129: bytes=32 time=488ms TTL=254
Reply from 196.210.170.129: bytes=32 time=342ms TTL=254

Ping statistics for 196.210.170.129:
    Packets: Sent = 30, Received = 25, Lost = 5 (16% loss),
Approximate round trip times in milli-seconds:
    Minimum = 91ms, Maximum = 619ms, Average = 294ms
 
2014/04/19 10:44:44.18
 
DeathStrike said:
Ok got WA account. the loading speed seems bit better. but the report says line is still faulty. I have also called telkom and had them reset my ports as well before running this test.


Zertop's "Is it my Line" Results
Basic Report:

Your average ping was 294ms
Your maximum ping was 619ms

Looking at your average ping, there is definitely something wrong with your line-( Please post the results (at the end of the program) into the forum for advice


Detailed Report

Code: 
Ping results for last hop before account switches to ISP's hardware (Hop 2 on Tracert) 

Pinging 196.210.170.129 with 32 bytes of data:
Request timed out.
Request timed out.
Reply from 196.210.170.129: bytes=32 time=104ms TTL=254
Reply from 196.210.170.129: bytes=32 time=121ms TTL=254
Reply from 196.210.170.129: bytes=32 time=118ms TTL=254
Reply from 196.210.170.129: bytes=32 time=114ms TTL=254
Reply from 196.210.170.129: bytes=32 time=105ms TTL=254
Reply from 196.210.170.129: bytes=32 time=91ms TTL=254
Reply from 196.210.170.129: bytes=32 time=490ms TTL=254
Reply from 196.210.170.129: bytes=32 time=474ms TTL=254
Reply from 196.210.170.129: bytes=32 time=443ms TTL=254
Reply from 196.210.170.129: bytes=32 time=619ms TTL=254
Reply from 196.210.170.129: bytes=32 time=272ms TTL=254
Reply from 196.210.170.129: bytes=32 time=381ms TTL=254
Reply from 196.210.170.129: bytes=32 time=119ms TTL=254
Reply from 196.210.170.129: bytes=32 time=568ms TTL=254
Reply from 196.210.170.129: bytes=32 time=517ms TTL=254
Reply from 196.210.170.129: bytes=32 time=112ms TTL=254
Reply from 196.210.170.129: bytes=32 time=350ms TTL=254
Request timed out.
Reply from 196.210.170.129: bytes=32 time=105ms TTL=254
Reply from 196.210.170.129: bytes=32 time=145ms TTL=254
Request timed out.
Reply from 196.210.170.129: bytes=32 time=102ms TTL=254
Reply from 196.210.170.129: bytes=32 time=542ms TTL=254
Reply from 196.210.170.129: bytes=32 time=312ms TTL=254
Request timed out.
Reply from 196.210.170.129: bytes=32 time=317ms TTL=254
Reply from 196.210.170.129: bytes=32 time=488ms TTL=254
Reply from 196.210.170.129: bytes=32 time=342ms TTL=254

Ping statistics for 196.210.170.129:
    Packets: Sent = 30, Received = 25, Lost = 5 (16% loss),
Approximate round trip times in milli-seconds:
    Minimum = 91ms, Maximum = 619ms, Average = 294ms
 
2014/04/19 10:44:44.18
Click to expand...
There were some exchanges reported yesterday in the Cape Town area with problems.
Not sure if it was resolved.

Source:
http://mybroadband.co.za/vb/showthr...back-(Pt3)?p=12505884&viewfull=1#post12505884
 
Last edited:
Gunner182 said:
Ohk cul, sounds positive. I think I'll make the switch back to shaped uncapped during the week. I'll prob PM you again to see if anything has changed. Thanks though.:)
Click to expand...

I'm still on the old 1Mbps package, not too worried about speed just getting what I need. Before the IPC problem I used to do around 150 -180 GB a month without even really trying to push it and do most of my downloading 10PM-8AM, if I wanted I could do more. Right now I'm on 58GB for the month with 12GB downloaded the past 2 days. That should give you at least an idea of home uncapped when all is working.
 
Hi there
I'm new here to Afrihost.
I have a 4meg line, uncapped. Here is my speedtest and just need to know if the speed looks okay?

Last Result:
Download Speed: 2842 kbps (355.3 KB/sec transfer rate)
Upload Speed: 265 kbps (33.1 KB/sec transfer rate)
Latency: 60 ms
19/4/2014 11:38:15

Second test, also Johannesburg server:
Last Result:
Download Speed: 3266 kbps (408.3 KB/sec transfer rate)
Upload Speed: 211 kbps (26.4 KB/sec transfer rate)
Latency: 60 ms
19/4/2014 11:40:47
Thanx

CS
 
Lionking_ said:
Hi there
I'm new here to Afrihost.
I have a 4meg line, uncapped. Here is my speedtest and just need to know if the speed looks okay?

Last Result:
Download Speed: 2842 kbps (355.3 KB/sec transfer rate)
Upload Speed: 265 kbps (33.1 KB/sec transfer rate)
Latency: 60 ms
19/4/2014 11:38:15

Second test, also Johannesburg server:
Last Result:
Download Speed: 3266 kbps (408.3 KB/sec transfer rate)
Upload Speed: 211 kbps (26.4 KB/sec transfer rate)
Latency: 60 ms
19/4/2014 11:40:47
Thanx

CS
Click to expand...
I assume that is local.
The 60ms seems a tad high.
A 4mbps line should yield about 3200Mps - 3600Mbps and 350 - 400kbps.
That is very generalized though. Some guys get better stats, some worse.

Ensure that no other downloads are running when you the tests.
It might also be that your exchange is a bit busy atm.

If you are really worried, you can search for the username Zertop in this thread.
There are 2 tests that you can run. Just look in his sig for the links.

I'm about 800km from Cape Town.

3448802954.png
[/URL][/IMG]
 
RoMark said:
There were some exchanges reported yesterday in the Cape Town area with problems.
Not sure if it was resolved.

Source:
http://mybroadband.co.za/vb/showthr...back-(Pt3)?p=12505884&viewfull=1#post12505884
Click to expand...
thanks. i might fall under that. don't want to call out telkom as they said it would be R300 if i call them out and it is not their fault. :/ can anyone tell me what their experience is with having the adsl line with afrihost? is it a good idea or not? i am considering it so that i don't have to deal with telkom for this issues.
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X