Afrihost Business Uncapped Feedback

Status
Not open for further replies.
Hasn't been a good year for internet ><

Tried your app, but doesn't seem to like me.

Ping results for last hop before account switches to ISP's hardware (Hop 2 on Tracert)
Bad parameter *.

2014-04-14 21:44:59,14


EDIT: "80 was unexpected at this time." appears on the screen after "Press any key to continue..."

o_O

Haha, okay. Ill have a look at why that is! Are you by any chance running a firewall?

Z
 
o_O

Haha, okay. Ill have a look at why that is! Are you by any chance running a firewall?

Z

Just the usual windows firewall.. tried disabling it but no luck.

.exe doesn't create any text files, but the zipped version does.. although just had what I pasted in my previous message in it.

Maybe my net is on another level of screwed..
 
Line has been dodgy for the last 3 days. And no, this is not over Wifi, it is via the cable (which was replaced last month as a fault finding measure, and it is not anything else but a crap line, yet again....)



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

Your average ping was 71ms
Your maximum ping was 182ms

Looking at your average ping, your line seems to be a bit dodgy :/ This may account for any slow speeds you may be experiencing. However, it could just be related to a high-latency home network (ie... Wi-Fi). If you feel the need, 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.11.193 with 32 bytes of data:
Reply from 105.236.11.193: bytes=32 time=13ms TTL=254
Reply from 105.236.11.193: bytes=32 time=12ms TTL=254
Reply from 105.236.11.193: bytes=32 time=13ms TTL=254
Reply from 105.236.11.193: bytes=32 time=12ms TTL=254
Reply from 105.236.11.193: bytes=32 time=13ms TTL=254
Reply from 105.236.11.193: bytes=32 time=13ms TTL=254
Reply from 105.236.11.193: bytes=32 time=14ms TTL=254
Reply from 105.236.11.193: bytes=32 time=12ms TTL=254
Reply from 105.236.11.193: bytes=32 time=12ms TTL=254
Reply from 105.236.11.193: bytes=32 time=13ms TTL=254
Reply from 105.236.11.193: bytes=32 time=89ms TTL=254
Reply from 105.236.11.193: bytes=32 time=49ms TTL=254
Reply from 105.236.11.193: bytes=32 time=47ms TTL=254
Reply from 105.236.11.193: bytes=32 time=39ms TTL=254
Reply from 105.236.11.193: bytes=32 time=92ms TTL=254
Reply from 105.236.11.193: bytes=32 time=114ms TTL=254
Reply from 105.236.11.193: bytes=32 time=112ms TTL=254
Reply from 105.236.11.193: bytes=32 time=117ms TTL=254
Reply from 105.236.11.193: bytes=32 time=111ms TTL=254
Reply from 105.236.11.193: bytes=32 time=57ms TTL=254
Reply from 105.236.11.193: bytes=32 time=119ms TTL=254
Reply from 105.236.11.193: bytes=32 time=114ms TTL=254
Reply from 105.236.11.193: bytes=32 time=147ms TTL=254
Reply from 105.236.11.193: bytes=32 time=182ms TTL=254
Reply from 105.236.11.193: bytes=32 time=173ms TTL=254
Reply from 105.236.11.193: bytes=32 time=98ms TTL=254
Reply from 105.236.11.193: bytes=32 time=66ms TTL=254
Reply from 105.236.11.193: bytes=32 time=79ms TTL=254
Reply from 105.236.11.193: bytes=32 time=139ms TTL=254
Reply from 105.236.11.193: bytes=32 time=85ms TTL=254

Ping statistics for 105.236.11.193:
    Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 12ms, Maximum = 182ms, Average = 71ms
 
2014/04/14 22:42:54.37
 
Line has been dodgy for the last 3 days. And no, this is not over Wifi, it is via the cable (which was replaced last month as a fault finding measure, and it is not anything else but a crap line, yet again....)



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

Your average ping was 71ms
Your maximum ping was 182ms

Looking at your average ping, your line seems to be a bit dodgy :/ This may account for any slow speeds you may be experiencing. However, it could just be related to a high-latency home network (ie... Wi-Fi). If you feel the need, 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.11.193 with 32 bytes of data:
Reply from 105.236.11.193: bytes=32 time=13ms TTL=254
Reply from 105.236.11.193: bytes=32 time=12ms TTL=254
Reply from 105.236.11.193: bytes=32 time=13ms TTL=254
Reply from 105.236.11.193: bytes=32 time=12ms TTL=254
Reply from 105.236.11.193: bytes=32 time=13ms TTL=254
Reply from 105.236.11.193: bytes=32 time=13ms TTL=254
Reply from 105.236.11.193: bytes=32 time=14ms TTL=254
Reply from 105.236.11.193: bytes=32 time=12ms TTL=254
Reply from 105.236.11.193: bytes=32 time=12ms TTL=254
Reply from 105.236.11.193: bytes=32 time=13ms TTL=254
Reply from 105.236.11.193: bytes=32 time=89ms TTL=254
Reply from 105.236.11.193: bytes=32 time=49ms TTL=254
Reply from 105.236.11.193: bytes=32 time=47ms TTL=254
Reply from 105.236.11.193: bytes=32 time=39ms TTL=254
Reply from 105.236.11.193: bytes=32 time=92ms TTL=254
Reply from 105.236.11.193: bytes=32 time=114ms TTL=254
Reply from 105.236.11.193: bytes=32 time=112ms TTL=254
Reply from 105.236.11.193: bytes=32 time=117ms TTL=254
Reply from 105.236.11.193: bytes=32 time=111ms TTL=254
Reply from 105.236.11.193: bytes=32 time=57ms TTL=254
Reply from 105.236.11.193: bytes=32 time=119ms TTL=254
Reply from 105.236.11.193: bytes=32 time=114ms TTL=254
Reply from 105.236.11.193: bytes=32 time=147ms TTL=254
Reply from 105.236.11.193: bytes=32 time=182ms TTL=254
Reply from 105.236.11.193: bytes=32 time=173ms TTL=254
Reply from 105.236.11.193: bytes=32 time=98ms TTL=254
Reply from 105.236.11.193: bytes=32 time=66ms TTL=254
Reply from 105.236.11.193: bytes=32 time=79ms TTL=254
Reply from 105.236.11.193: bytes=32 time=139ms TTL=254
Reply from 105.236.11.193: bytes=32 time=85ms TTL=254

Ping statistics for 105.236.11.193:
    Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 12ms, Maximum = 182ms, Average = 71ms
 
2014/04/14 22:42:54.37

Yea, looking bad /:

Have you reported a fault?

Z
 
Tested this morning at 8am. Guess this isn't just restricted to peak times.

traceroute to afrihost.co.za (197.242.144.102), 64 hops max, 52 byte packets
1 192.168.0.1 (192.168.0.1) 1.085 ms 0.901 ms 0.715 ms
2 105-236-0-129-esr-lo.mtnbusiness.co.za (105.236.0.129) 9.754 ms 91.834 ms 145.894 ms
3 41.181.222.42 (41.181.222.42) 20.091 ms 236.725 ms 409.472 ms
4 ng-mse-1--ng-cr-1-a.za.mtnns.net (196.44.27.68) 302.598 ms 203.344 ms 280.234 ms
5 jh-cr-1.za--ng-cr-1.za.mtnns.net (196.44.31.176) 126.284 ms 216.796 ms 74.035 ms
6 rb-cr-2.za--jh-cr-1.za.mtnns.net (196.44.0.43) 118.548 ms 200.265 ms 261.710 ms
7 qux--rb-dca-2.za-b.za.mtnbusiness.net (41.181.165.119) 405.884 ms 266.888 ms 32.795 ms
8 196.31.220.10 (196.31.220.10) 22.321 ms
196.30.1.53 (196.30.1.53) 54.908 ms
196.31.220.10 (196.31.220.10) 121.176 ms
9 196.31.220.21 (196.31.220.21) 93.430 ms 133.659 ms 133.368 ms
10 196.31.63.206 (196.31.63.206) 36.063 ms 179.091 ms 145.067 ms
11 196.30.42.133 (196.30.42.133) 135.532 ms 308.675 ms 406.896 ms
12 cms-gm.afrihost.com (197.242.144.102) 317.540 ms !Z 19.745 ms !Z 34.539 ms !Z

Speedtests won't even complete, they just hang or fail, but I'm only getting 2mb instead of 4mb. Great start to the day.
 
Certain changes are immediate others are at the beginning of the month.
Upgrades are usually instantly, but downgrades I think only effective at the start of the new month.

I'm running into this issue ATM. afrihost edit package - edited.jpg

Clientzone says changes effective immediately. Moved from "business DSL" uncapped to "uncapped" early April. Funny thing is that I can tell my product has been moved (torrents are shaped - corresponding to 'shaping policy' online) but Afrihost support insist the move hasn't happened and refuse to credit me for the pro-rated difference.

Anyone else hitting their head against this? :confused:
 
Spoke too soon, speed crap again. 8mb Business Uncapped .

Last Result:
Download Speed: 2014 kbps (251.8 KB/sec transfer rate)
Upload Speed: 859 kbps (107.4 KB/sec transfer rate)
Latency: 17 ms
Monday, 14 April 2014 19:44

We're seeing usage pick up again, it was reasonably calm yesterday so we saw better throughput than we have recently. I'm still hoping that this week leading up to the upgrade will be quieter than usual due to the the upcoming holiday.
 
So basically I am screwed until Telkom decides to do something...My problem is that it was running fine two months ago and now all of a sudden my noise margin has become really bad :/

The noise margin could be determined by several factors - POTS filters are the first place to look, but there could be induced noise on the line from Electromagnetic interference from electric fences or appliances on the same power circuit as the router, etc. Sometimes it can be pretty hard to pin down.

Are you logging faults with Telkom (either directly or through us)?
 
Line has been dodgy for the last 3 days. And no, this is not over Wifi, it is via the cable (which was replaced last month as a fault finding measure, and it is not anything else but a crap line, yet again....)



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

Your average ping was 71ms
Your maximum ping was 182ms

Looking at your average ping, your line seems to be a bit dodgy :/ This may account for any slow speeds you may be experiencing. However, it could just be related to a high-latency home network (ie... Wi-Fi). If you feel the need, 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.11.193 with 32 bytes of data:
Reply from 105.236.11.193: bytes=32 time=13ms TTL=254
Reply from 105.236.11.193: bytes=32 time=12ms TTL=254
Reply from 105.236.11.193: bytes=32 time=13ms TTL=254
Reply from 105.236.11.193: bytes=32 time=12ms TTL=254
Reply from 105.236.11.193: bytes=32 time=13ms TTL=254
Reply from 105.236.11.193: bytes=32 time=13ms TTL=254
Reply from 105.236.11.193: bytes=32 time=14ms TTL=254
Reply from 105.236.11.193: bytes=32 time=12ms TTL=254
Reply from 105.236.11.193: bytes=32 time=12ms TTL=254
Reply from 105.236.11.193: bytes=32 time=13ms TTL=254
Reply from 105.236.11.193: bytes=32 time=89ms TTL=254
Reply from 105.236.11.193: bytes=32 time=49ms TTL=254
Reply from 105.236.11.193: bytes=32 time=47ms TTL=254
Reply from 105.236.11.193: bytes=32 time=39ms TTL=254
Reply from 105.236.11.193: bytes=32 time=92ms TTL=254
Reply from 105.236.11.193: bytes=32 time=114ms TTL=254
Reply from 105.236.11.193: bytes=32 time=112ms TTL=254
Reply from 105.236.11.193: bytes=32 time=117ms TTL=254
Reply from 105.236.11.193: bytes=32 time=111ms TTL=254
Reply from 105.236.11.193: bytes=32 time=57ms TTL=254
Reply from 105.236.11.193: bytes=32 time=119ms TTL=254
Reply from 105.236.11.193: bytes=32 time=114ms TTL=254
Reply from 105.236.11.193: bytes=32 time=147ms TTL=254
Reply from 105.236.11.193: bytes=32 time=182ms TTL=254
Reply from 105.236.11.193: bytes=32 time=173ms TTL=254
Reply from 105.236.11.193: bytes=32 time=98ms TTL=254
Reply from 105.236.11.193: bytes=32 time=66ms TTL=254
Reply from 105.236.11.193: bytes=32 time=79ms TTL=254
Reply from 105.236.11.193: bytes=32 time=139ms TTL=254
Reply from 105.236.11.193: bytes=32 time=85ms TTL=254

Ping statistics for 105.236.11.193:
    Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 12ms, Maximum = 182ms, Average = 71ms
 
2014/04/14 22:42:54.37

Seems like pings seems to get worse as you go along - sorry to see this. So you think your line issues are back again?
 
Guys not to be a DOOM sayer but the 18th is a holiday??? wont this affect the install??? some feedback??

I don't think it's an impossibility - Telkom have made people available on Public Holdays before during outages and maintenance. I think it could be a valid date. At the level we're talking about management-wise, I don't think those dates are given out lightly (I hope so).
 
I don't think it's an impossibility - Telkom have made people available on Public Holdays before during outages and maintenance. I think it could be a valid date. At the level we're talking about management-wise, I don't think those dates are given out lightly (I hope so).

This does not sound so confident anymore? I have a feeling the ipc issues will remain.
 
Last edited:
This does not sound so confident anymore? I have a feeling the ipc issues will remain.

Given the number of delays, I guess I have to leave some room for doubt. But from all indications, the 18th should go ahead as scheduled. I really doubt that there could possibly be any further delays at this stage.
 
The noise margin could be determined by several factors - POTS filters are the first place to look, but there could be induced noise on the line from Electromagnetic interference from electric fences or appliances on the same power circuit as the router, etc. Sometimes it can be pretty hard to pin down.

Are you logging faults with Telkom (either directly or through us)?

I have logged a fault through afrihost and Telkom about two weeks ago...I replaced all the POTS filters and the router is connected independently. I don't what I can do further...
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X